aboutsummaryrefslogtreecommitdiff
path: root/doc/contrib
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2007-05-31 23:58:54 +0000
committerRoger Dingledine <arma@torproject.org>2007-05-31 23:58:54 +0000
commitd8a1f31283e575e4ec28afc070d784c8e83599c2 (patch)
treef323560bbf7c3ad1f79ea27c3c16bbaa4f8c97e8 /doc/contrib
parentcf8153beff68458aab383335be5f6f74aafb4051 (diff)
downloadtor-d8a1f31283e575e4ec28afc070d784c8e83599c2.tar
tor-d8a1f31283e575e4ec28afc070d784c8e83599c2.tar.gz
fix these typos too while i'm at it
svn:r10431
Diffstat (limited to 'doc/contrib')
-rw-r--r--doc/contrib/incentives.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/contrib/incentives.txt b/doc/contrib/incentives.txt
index 994310025..850a0d01e 100644
--- a/doc/contrib/incentives.txt
+++ b/doc/contrib/incentives.txt
@@ -290,7 +290,7 @@
One could argue, though, that once those servers are over-congested,
their bandwidth per circuit drops, which would in turn lower their
reputation in the future. A question is whether this would overall
- stablize.
+ stabilize.
Another possible way is to keep a cap on reputation. In this way, a
fraction of servers would have the same high reputation, thus balancing
@@ -347,7 +347,7 @@
gets preferred treatment at each node. A node "spends" its value, which
it earned a priori by providing service, to the next node by sending
and receiving bytes. Once a node has overspent its values, the circuit
- cannot stay as premium. It can either breaks or converts into a normal
+ cannot stay as premium. It either breaks or converts into a normal
circuit. Each node also reserves a small portion of bandwidth for
normal circuits to prevent starvation.