[tor-commits] [tor/master] Fix a changelog typo

[nickm at torproject.org]

commit 9662a13d7e587ec9b78af77cdb6607b4ad23a918
Author: Nick Mathewson <nickm at torproject.org>
Date:   Thu Jan 30 12:56:06 2020 -0500

    Fix a changelog typo
---
 ChangeLog    | 6 +++---
 ReleaseNotes | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 195093a5b..3d05bea86 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -9,7 +9,7 @@ Changes in version 0.4.2.6 - 2020-01-30
     - Correct how we use libseccomp. Particularly, stop assuming that
       rules are applied in a particular order or that more rules are
       processed after the first match. Neither is the case! In
-      libseccomp <2.4.0 this lead to some rules having no effect.
+      libseccomp <2.4.0 this led to some rules having no effect.
       libseccomp 2.4.0 changed how rules are generated, leading to a
       different ordering, which in turn led to a fatal crash during
       startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
@@ -64,7 +64,7 @@ Changes in version 0.4.1.8 - 2020-01-30
     - Correct how we use libseccomp. Particularly, stop assuming that
       rules are applied in a particular order or that more rules are
       processed after the first match. Neither is the case! In
-      libseccomp <2.4.0 this lead to some rules having no effect.
+      libseccomp <2.4.0 this led to some rules having no effect.
       libseccomp 2.4.0 changed how rules are generated, leading to a
       different ordering, which in turn led to a fatal crash during
       startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
@@ -146,7 +146,7 @@ Changes in version 0.4.3.1-alpha - 2020-01-22
     - Correct how we use libseccomp. Particularly, stop assuming that
       rules are applied in a particular order or that more rules are
       processed after the first match. Neither is the case! In
-      libseccomp <2.4.0 this lead to some rules having no effect.
+      libseccomp <2.4.0 this led to some rules having no effect.
       libseccomp 2.4.0 changed how rules are generated, leading to a
       different ordering, which in turn led to a fatal crash during
       startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
diff --git a/ReleaseNotes b/ReleaseNotes
index c33355f68..7d981e2c4 100644
--- a/ReleaseNotes
+++ b/ReleaseNotes
@@ -13,7 +13,7 @@ Changes in version 0.4.2.6 - 2020-01-30
     - Correct how we use libseccomp. Particularly, stop assuming that
       rules are applied in a particular order or that more rules are
       processed after the first match. Neither is the case! In
-      libseccomp <2.4.0 this lead to some rules having no effect.
+      libseccomp <2.4.0 this led to some rules having no effect.
       libseccomp 2.4.0 changed how rules are generated, leading to a
       different ordering, which in turn led to a fatal crash during
       startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
@@ -68,7 +68,7 @@ Changes in version 0.4.1.8 - 2020-01-30
     - Correct how we use libseccomp. Particularly, stop assuming that
       rules are applied in a particular order or that more rules are
       processed after the first match. Neither is the case! In
-      libseccomp <2.4.0 this lead to some rules having no effect.
+      libseccomp <2.4.0 this led to some rules having no effect.
       libseccomp 2.4.0 changed how rules are generated, leading to a
       different ordering, which in turn led to a fatal crash during
       startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by