aboutsummaryrefslogtreecommitdiff
path: root/proposals/293-know-when-to-publish.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2018-07-16 23:42:35 -0400
committerRoger Dingledine <arma@torproject.org>2018-07-16 23:42:35 -0400
commitd31c33c95f146ecf616447495c48eb89a9fa9c63 (patch)
treef006c952ab1d725a5173339f52c776bc4892911e /proposals/293-know-when-to-publish.txt
parent6f0112693edd4cb2fb70eb3e36af4942b6381b6a (diff)
downloadtorspec-d31c33c95f146ecf616447495c48eb89a9fa9c63.tar.gz
torspec-d31c33c95f146ecf616447495c48eb89a9fa9c63.zip
one more typo
Diffstat (limited to 'proposals/293-know-when-to-publish.txt')
-rw-r--r--proposals/293-know-when-to-publish.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/293-know-when-to-publish.txt b/proposals/293-know-when-to-publish.txt
index ebc94e3..f2d96e0 100644
--- a/proposals/293-know-when-to-publish.txt
+++ b/proposals/293-know-when-to-publish.txt
@@ -49,7 +49,7 @@ Target: 0.3.5
4. Implications for proposal 275
- Once most relays are running verions that support the features
+ Once most relays are running versions that support the features
above, and once authorities are generating consensuses with the
StaleDesc flag, there will no longer be a need to keep the
published time in consensus documents accurate -- we can start