commit 6f0112693edd4cb2fb70eb3e36af4942b6381b6a Author: Roger Dingledine <arma@torproject.org> Date: Mon Jul 16 13:39:52 2018 -0400 three tiny fixes to prop#293 --- proposals/293-know-when-to-publish.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/proposals/293-know-when-to-publish.txt b/proposals/293-know-when-to-publish.txt index 4a46730..ebc94e3 100644 --- a/proposals/293-know-when-to-publish.txt +++ b/proposals/293-know-when-to-publish.txt @@ -23,10 +23,10 @@ Target: 0.3.5 2. Mechanism One: The StaleDesc flag - Authorities should begin voting aon a new StaleDesc flag. + Authorities should begin voting on a new StaleDesc flag. When authorities vote, if the most recent published_on date for - a descriptor has over DESC_IS_STALE_INTERVAL in the past, the + a descriptor is over DESC_IS_STALE_INTERVAL in the past, the authorities should vote to give the StaleDesc flag to that relay. If any relay sees that it has the StaleDesc flag, it should upload @@ -55,4 +55,3 @@ Target: 0.3.5 published time in consensus documents accurate -- we can start setting it to some time in the distant future, per proposal 275. -