[tor-commits] [tor/release-0.3.0] improve the blurbs.

[nickm at torproject.org]

commit 6f9af947577f478ea002061743894036b9e35f13
Author: Nick Mathewson <nickm at torproject.org>
Date:   Wed Apr 26 14:10:49 2017 -0400

    improve the blurbs.
---
 ChangeLog    | 12 ++++++------
 ReleaseNotes | 10 +++++-----
 2 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 962bce1..7efebf1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -4,7 +4,7 @@ Changes in version 0.3.0.6 - 2017-04-26
   With the 0.3.0 series, clients and relays now use Ed25519 keys to
   authenticate their link connections to relays, rather than the old
   RSA1024 keys that they used before. (Circuit crypto has been
-  Curve25519- authenticated since 0.2.4.8-alpha.)  We have also replaced
+  Curve25519-authenticated since 0.2.4.8-alpha.)  We have also replaced
   the guard selection and replacement algorithm to behave more robustly
   in the presence of unreliable networks, and to resist guard-capture
   attacks.
@@ -13,10 +13,10 @@ Changes in version 0.3.0.6 - 2017-04-26
   along with more groundwork for the upcoming hidden-services revamp.
 
   Per our stable release policy, we plan to support the Tor 0.3.0
-  release series will be supported for at least the next nine months, or
-  for three months after the release the first stable 0.3.1 series:
-  whichever is longer.  If you need release with long-term support,
-  we recommend that you stay with the 0.2.9 series.
+  release series for at least the next nine months, or for three months
+  after the first stable release of the 0.3.1 series: whichever is
+  longer.  If you need a release with long-term support, we recommend
+  that you stay with the 0.2.9 series.
 
   Below are the changes since 0.3.0.5-rc. For a list of all changes
   since 0.2.9, see the ReleaseNotes file.
@@ -31,7 +31,7 @@ Changes in version 0.3.0.6 - 2017-04-26
       refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
 
   o Minor bugfixes (crash prevention):
-    - Fix an (currently untriggerable, but potentially dangerous) crash
+    - Fix a (currently untriggerable, but potentially dangerous) crash
       bug when base32-encoding inputs whose sizes are not a multiple of
       5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
 
diff --git a/ReleaseNotes b/ReleaseNotes
index 7ac3761..a36036c 100644
--- a/ReleaseNotes
+++ b/ReleaseNotes
@@ -9,7 +9,7 @@ Changes in version 0.3.0.6 - 2017-04-26
   With the 0.3.0 series, clients and relays now use Ed25519 keys to
   authenticate their link connections to relays, rather than the old
   RSA1024 keys that they used before. (Circuit crypto has been
-  Curve25519- authenticated since 0.2.4.8-alpha.)  We have also replaced
+  Curve25519-authenticated since 0.2.4.8-alpha.)  We have also replaced
   the guard selection and replacement algorithm to behave more robustly
   in the presence of unreliable networks, and to resist guard-capture
   attacks.
@@ -18,10 +18,10 @@ Changes in version 0.3.0.6 - 2017-04-26
   along with more groundwork for the upcoming hidden-services revamp.
 
   Per our stable release policy, we plan to support the Tor 0.3.0
-  release series will be supported for at least the next nine months, or
-  for three months after the release the first stable 0.3.1 series:
-  whichever is longer.  If you need release with long-term support,
-  we recommend that you stay with the 0.2.9 series.
+  release series for at least the next nine months, or for three months
+  after the first stable release of the 0.3.1 series: whichever is
+  longer.  If you need a release with long-term support, we recommend
+  that you stay with the 0.2.9 series.
 
   Below are the changes since 0.2.9.10. For a list of only the changes
   since 0.3.0.5-rc, see the ChangeLog file.