3 files changed, 14 insertions, 1 deletions
diff --git a/doc/build-windows.md b/doc/build-windows.md
index 129774491b..ec5f26c88b 100644
--- a/doc/build-windows.md
+++ b/doc/build-windows.md
@@ -27,6 +27,7 @@ To build executables for Windows 32-bit:
     cd depends
     make HOST=i686-w64-mingw32 -j4
     cd ..
+    ./autogen.sh # not required when building from tarball
     ./configure --prefix=`pwd`/depends/i686-w64-mingw32
     make
 
@@ -35,6 +36,7 @@ To build executables for Windows 64-bit:
     cd depends
     make HOST=x86_64-w64-mingw32 -j4
     cd ..
+    ./autogen.sh # not required when building from tarball
     ./configure --prefix=`pwd`/depends/x86_64-w64-mingw32
     make
 
diff --git a/doc/release-process.md b/doc/release-process.md
index e2ad3949d6..d07f9a89ad 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -5,6 +5,8 @@ Before every release candidate:
 
 * Update translations (ping wumpus on IRC) see [translation_process.md](https://github.com/bitcoin/bitcoin/blob/master/doc/translation_process.md#synchronising-translations).
 
+* Update manpages, see [gen-manpages.sh](https://github.com/bitcoin/bitcoin/blob/master/contrib/devtools/README.md#gen-manpagessh).
+
 Before every minor and major release:
 
 * Update [bips.md](bips.md) to account for changes since the last release.
diff --git a/doc/tor.md b/doc/tor.md
index 79f1563021..2f376af4c7 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -113,4 +113,13 @@ the user running bitcoind to the same group and setting permissions appropriatel
 Debian-based systems the user running bitcoind can be added to the debian-tor group, 
 which has the appropriate permissions. An alternative authentication method is the use 
 of the `-torpassword` flag and a `hash-password` which can be enabled and specified in 
-Tor configuration.
-\ No newline at end of file
+Tor configuration.
+
+4. Privacy recommendations
+---------------------------
+
+- Do not add anything but bitcoin ports to the hidden service created in section 2.
+  If you run a web service too, create a new hidden service for that.
+  Otherwise it is trivial to link them, which may reduce privacy. Hidden
+  services created automatically (as in section 3) always have only one port
+  open.