aboutsummaryrefslogtreecommitdiff
path: root/doc/Tor.txt
diff options
context:
space:
mode:
authorAPerson241 <setup.pyc@gmail.com>2013-04-23 13:17:59 -0300
committerAPerson241 <setup.pyc@gmail.com>2013-04-23 13:17:59 -0300
commit6ee82ddb70ba2e003d79709824edcfbcf39a420b (patch)
treeaba51f93f7ed4318c0d2ccca8313a106d57b1267 /doc/Tor.txt
parent2272f8bb47e9383f9c3d3236363e5845f319d7ad (diff)
Update Tor.txt for grammar fixes
Diffstat (limited to 'doc/Tor.txt')
-rw-r--r--doc/Tor.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/Tor.txt b/doc/Tor.txt
index f515f96f49..386e3b5466 100644
--- a/doc/Tor.txt
+++ b/doc/Tor.txt
@@ -3,7 +3,7 @@ TOR SUPPORT IN BITCOIN
It is possible to run Bitcoin as a Tor hidden service, and connect to such services.
-The following assumes you have a Tor proxy running on port 9050. Many distributions
+The following directions assume you have a Tor proxy running on port 9050. Many distributions
default to having a SOCKS proxy listening on port 9050, but others may not.
In particular, the Tor Browser Bundle defaults to listening on a random port. See
https://www.torproject.org/docs/faq.html.en#TBBSocksPort for how to properly
@@ -77,7 +77,7 @@ In a typical situation, where you're only reachable via Tor, this should suffice
./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen
-(obviously replace the Onion address with your own). If you don't care too much
+(obviously, replace the Onion address with your own). If you don't care too much
about hiding your node, and want to be reachable on IPv4 as well, additionally
specify: