aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Goulet <dgoulet@torproject.org>2024-07-22 14:54:42 +0000
committerDavid Goulet <dgoulet@torproject.org>2024-07-22 14:54:42 +0000
commit12dc46c9cafcce7d27d245e005ff56ed55958310 (patch)
treeba8c2c85d5fe32e258715c2d4a7fffecbdb5013a
parent8bb8ac2d9aba721bfa6efc4c979ba7dfb853c311 (diff)
parent1e44a359f5c79a69f5373649b0526d656f329767 (diff)
downloadtor-12dc46c9cafcce7d27d245e005ff56ed55958310.tar.gz
tor-12dc46c9cafcce7d27d245e005ff56ed55958310.zip
Merge branch 'manpage-typos' into 'main'
two small presentation issues in man page See merge request tpo/core/tor!824
-rw-r--r--doc/man/tor.1.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt
index 78449e3f72..2a936f6702 100644
--- a/doc/man/tor.1.txt
+++ b/doc/man/tor.1.txt
@@ -1010,7 +1010,7 @@ forward slash (/) in the configuration file and on the command line.
equivalent option for directory connections, because all Tor client versions
that support this option download directory documents via OR connections. +
+
- The only protocol supported right now 'haproxy'. This option is only for
+ The only protocol supported right now is 'haproxy'. This option is only for
clients. (Default: none) +
+
The HAProxy version 1 proxy protocol is described in detail at
@@ -3128,7 +3128,7 @@ hard and are likely different for each service operator.
Why is this not helping reachability of the service? Because the defenses are
at the introduction point, an attacker can easily flood all introduction point
rendering the service unavailable due to no client being able to pass through.
-But, the service itself is not overwhelmed with connetions allowing it to
+But, the service itself is not overwhelmed with connections allowing it to
function properly for the few clients that were able to go through or other any
services running on the same tor instance.