[tor-commits] [torspec/master] fix typos in proposal 290

[arma@xxxxxxxxxxxxxx]

commit ba05c9a935a96a4d8e94be1f3db768808b738b1c
Author: Roger Dingledine <arma@xxxxxxxxxxxxxx>
Date:   Sat Mar 3 01:48:33 2018 -0500

    fix typos in proposal 290
---
 proposals/290-deprecate-consensus-methods.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/proposals/290-deprecate-consensus-methods.txt b/proposals/290-deprecate-consensus-methods.txt
index db047c8..54e900c 100644
--- a/proposals/290-deprecate-consensus-methods.txt
+++ b/proposals/290-deprecate-consensus-methods.txt
@@ -21,7 +21,7 @@ Status: Open
    With proposal 215, we deprecated and removed support for all
    consensus methods before method 13.  That was good as far as it went,
    but it didn't solve the problem going forward: the latest consensus
-   methods is now 28.
+   method is now 28.
 
    This proposal describes a policy for removing older consensus methods
    going forward, so we won't have to keep supporting them forever.
@@ -32,7 +32,7 @@ Status: Open
    deprecated.
 
    Specifically, I propose that we deprecate all methods older than the
-   highest method supported in first stable release of the oldest LTS
+   highest method supported in the first stable release of the oldest LTS
    (long-term support) release series.
 
    For example, the current oldest LTS series is 0.2.5.x.  The first
@@ -57,7 +57,7 @@ Status: Open
    previous implementations of the feature.
 
    Some consensus methods remove a feature that was used up to method
-   N. Deprecating method M means that the feature is no longer used by
+   M. Deprecating method M means that the feature is no longer used by
    any supported consensus methods. Therefore, we can remove any code
    that implements the feature.
 

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits