aboutsummaryrefslogtreecommitdiff
path: root/proposals/341-better-oos.md
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2022-07-27 01:25:09 -0400
committerRoger Dingledine <arma@torproject.org>2022-07-27 01:25:09 -0400
commitb5e2002983fc4682b88fedb73a9101cc8090b053 (patch)
treeec012dae6cfdc7f929b577ab9a44d0fad5402ec2 /proposals/341-better-oos.md
parent6f9ec72e279c837a07101b37c8790117cdfaf8a5 (diff)
downloadtorspec-b5e2002983fc4682b88fedb73a9101cc8090b053.tar.gz
torspec-b5e2002983fc4682b88fedb73a9101cc8090b053.zip
fix some easy typos in proposals
Diffstat (limited to 'proposals/341-better-oos.md')
-rw-r--r--proposals/341-better-oos.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/proposals/341-better-oos.md b/proposals/341-better-oos.md
index 0715c14..8ddf7fd 100644
--- a/proposals/341-better-oos.md
+++ b/proposals/341-better-oos.md
@@ -56,7 +56,7 @@ other words, when you see "A - B" below, read it as "MAX(A-B, 0)".
## Phase 1: Deciding how many connections to close
-When we are find that we are low on sockets, we pick a number of sockets
+When we find that we are low on sockets, we pick a number of sockets
that we want to close according to our existing algorithm. (That is, we
try to close 1/4 of our maximum sockets if we have reached our upper
limit, or 1/10 of our maximum sockets if we have encountered a failure
@@ -133,8 +133,8 @@ until we have closed at least our target number of exit connections.
> This approach probabilistically favors closing circuits with a large
> number of sockets open, regardless of how long those sockets have been
> open. This defeats the easiest way of opening a large number of exit
-> streams ("open them all on once circuit") without making the
-> counter-approach ("open each exit stream on a its own circuit") much
+> streams ("open them all on one circuit") without making the
+> counter-approach ("open each exit stream on its own circuit") much
> more attractive.
## Phase 3: Closing OR connections.