Update external-tor-usage.md

docs/external-tor-usage.md

@@ -4,22 +4,22 @@
 
 ### 1. Download and Install Tor
 #### Linux
-You can install Tor through your system's package manager, or directly by going to torproject.org. Note that your package manager's version of tor might be outdated or non-GNU (see below note).
+You can install Tor through your system's package manager (on Debian/Ubuntu: ```apt install tor```; see note 1. below), or directly by going to torproject.org. Note that your package manager's version of tor might be outdated or non-GNU (see note 2. below).
 #### MacOS
-You can install Tor through Homebrew (brew install tor), or directly by going to torproject.org. Note that the Homebrew version of tor might be outdated or non-GNU (see note below).
+You can install Tor through Homebrew (```brew install tor```), or directly by going to torproject.org. Note that the Homebrew version of tor might be outdated or non-GNU (see note 2. below).
 #### Windows
 You can install Tor directly by going to torproject.org.
-> For best results, ensure that your version of tor matches the one currently used by Haveno. To improve loading times, it is highly recommended to use the GNU build, as it has support for POW. You can check if your build is GNU by running tor --version and looking for a response mentioning GNU.
+>1. Tor recommends using their own repository on Debian/Ubuntu, see [here](https://support.torproject.org/apt/tor-deb-repo/).
+>2. For best results, ensure that your version of tor matches the one currently used by Haveno. To improve loading times, it is highly recommended to use the GNU build, as it has support for POW. You can check if your build is GNU by running tor --version and looking for a response mentioning GNU.
 
-### 2. Add the following lines to your torrc:
+### 2. Add the following lines to your torrc file:
 ```
 controlPort=9051
 CookieAuthentication 1
 CookieAuthFile <path to cookie auth file>
 ```
-> The "CookieAuthFile" path should be in a relatively stable and safe place. A good place to put it is in the same directory as torrc.
-
-### The location of your torrc file varies depending on your system:
+> The "CookieAuthFile" will not exist until after Tor is ran, so running Tor once will create it if it does not exist. The file's location, while technically arbitrary, should be in a relatively stable and safe place. For example, on Linux it could be placed at ```/etc/tor/control_auth_cookie```, or next to your torrc file.
+#### The location of your torrc file varies depending on your system:
 
 #### Linux
 ```/etc/tor/torrc```
@@ -28,7 +28,7 @@ CookieAuthFile <path to cookie auth file>
 #### Windows
 ```\Browser\TorBrowser\Data\Tor\torrc``` (when using the Tor Browser Bundle)
 
-> The above locations are best guesses, and may be incorrect depending on your installation method or platform distribution. In the case that you cannot find the correct directory to place your torrc, tor can be ran in the following format to use a custom torrc: ```tor -f <torrc>```
+> The above locations are best guesses, and may be incorrect depending on your installation method or platform distribution. In the case that you cannot find the correct directory to place your torrc, tor can be ran in the following format to use a custom torrc: ```tor -f <path to torrc>```
 
 ### 3. Stop any currently running tor processes
 #### Linux/MacOS
@@ -46,4 +46,4 @@ Run the Haveno binary with the following extra flags:
 ```
 > Replace the ```<path to cookie auth file>``` with the location you specified in step 2.
 
-> Depending on how your version of Haveno was distributed, you may not have direct access to the haveno binary. In this case, you should look inside your Haveno distribution for the binary, and then run the binary using the above flags. For example, on MacOS the binary will be located within the app at Haveno.app/Contents/MacOS/Haveno, or something similar.
+> Depending on how your version of Haveno was distributed, you may not have direct access to the Haveno binary. In this case, you should look inside your Haveno distribution for the binary, and then run the binary using the above flags. For example, on MacOS the binary will be located within the app at Haveno.app/Contents/MacOS/Haveno, or something similar.