diff --git a/doc/tor.md b/doc/tor.md
index 733baab43d..fd28d24c20 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -120,7 +120,7 @@ API, to create and destroy 'ephemeral' hidden services programmatically.
 Dash Core has been updated to make use of this.
 
 This means that if Tor is running (and proper authentication has been configured),
-Dash Core automatically creates a hidden service to listen on. This will positively 
+Dash Core automatically creates a hidden service to listen on. This will positively
 affect the number of available .onion nodes.
 
 This new feature is enabled by default if Dash Core is listening (`-listen`), and
@@ -129,8 +129,9 @@ and, if not disabled, configured using the `-torcontrol` and `-torpassword` sett
 To show verbose debugging information, pass `-debug=tor`.
 
 Connecting to Tor's control socket API requires one of two authentication methods to be
-configured. For cookie authentication the user running dashd must have write access
-to the `CookieAuthFile` specified in Tor configuration. In some cases, this is
+configured. It also requires the control socket to be enabled, e.g. put `ControlPort 9051`
+in `torrc` config file. For cookie authentication the user running dashd must have read
+access to the `CookieAuthFile` specified in Tor configuration. In some cases this is
 preconfigured and the creation of a hidden service is automatic. If permission problems
 are seen with `-debug=tor` they can be resolved by adding both the user running Tor and
 the user running dashd to the same group and setting permissions appropriately. On