From 3a65dc0dc954273cd6a212e880449fade3e58eaf Mon Sep 17 00:00:00 2001
From: Erik Arvstedt <erik.arvstedt@gmail.com>
Date: Mon, 22 Aug 2022 14:57:40 +0200
Subject: [PATCH] docs/configuration: improve section `Remote bitcoind`

---
 docs/configuration.md | 17 +++++++----------
 1 file changed, 7 insertions(+), 10 deletions(-)

diff --git a/docs/configuration.md b/docs/configuration.md
index b0f151c..878bf45 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -214,18 +214,15 @@ services.bitcoind = {
 };
 ```
 
-If a `secure-node.nix` or `tor-enable.nix` preset is imported in your
-configuration or a `tor.enforce` option is explicitly enabled, you also need to
-allow remote connections for **every** service which needs to connect to the
-remote bitcoind:
-
-```
-systemd.services.<service>.serviceConfig = {
-  IPAddressAllow = [ ${services.bitcoind.rpc.address} ];
-};
+For each service that connects to bitcoind and has option
+`services.<service>.tor.enforce` enabled (either explicitly or by importing
+`secure-node.nix` or `enable-tor.nix`), you need to
+allow the remote bitcoind connection:
+```nix
+systemd.services.<service>.serviceConfig.IPAddressAllow = [ ${services.bitcoind.rpc.address} ];
 ```
 
-> Please note that configuration above applies only if the remote bitcoind **is
+> The above configuration is only required if the remote bitcoind **is
 > not** accessed via Tor.