[Reproducible-commits] [reproducible-website] 26/55: Fixed some typos and orthography

Tue Aug 23 13:39:52 UTC 2016

This is an automated email from the git hooks/post-receive script.

lamby pushed a commit to branch master
in repository reproducible-website.

commit 5d0dee374a5fd920771eca91d1621b8881ef10b9
Author: Dhole <dhole at openmailbox.org>
Date:   Thu Nov 5 14:58:09 2015 +0100

    Fixed some typos and orthography
---
 _docs/locales.md                        | 6 +++---
 _docs/stable_outputs.md                 | 4 ++--
 _docs/timezones.md                      | 2 +-
 _docs/volatile_inputs.md                | 2 +-
 _posts/2015-10-16-new-homepage.markdown | 2 +-
 index.html                              | 2 +-
 tools.html                              | 2 +-
 7 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/_docs/locales.md b/_docs/locales.md
index c64a30d..04ba2a5 100644
--- a/_docs/locales.md
+++ b/_docs/locales.md
@@ -18,7 +18,7 @@ Time format
 
 Several common time formatting functions will have output depending
 on the current locale. On POSIX system the formatting will depend on
-the `LC_CTIME` environment variable, which can be overriden by
+the `LC_CTIME` environment variable, which can be overridden by
 `LC_ALL`.
 
 For build systems, it's thus best to use `LC_ALL` directly:
@@ -38,7 +38,7 @@ Collation order
 ---------------
 
 Common sorting functions are affected by the `LC_COLLATE` environment
-variable, which can which can be overriden by `LC_ALL`. Some locales can
+variable, which can which can be overridden by `LC_ALL`. Some locales can
 be quite surprising:
 
 This typically shows when using `sort`. The `fr_FR` locale will sort
@@ -70,7 +70,7 @@ Default character encoding
 
 The default system character encoding will affect both the input and
 output of many tools. It is defined using the `LC_CTYPE` environment
-variable, and can also be overriden using `LC_ALL`.
+variable, and can also be overridden using `LC_ALL`.
 
 Here's an example when using `lynx` to convert HTML documentation into
 text:
diff --git a/_docs/stable_outputs.md b/_docs/stable_outputs.md
index 00c4df0..b4797e3 100644
--- a/_docs/stable_outputs.md
+++ b/_docs/stable_outputs.md
@@ -35,9 +35,9 @@ For Perl, it is possible to set `PERL_HASH_SEED=0` in the environment. This
 will result in hash keys always being in the same order. See
 [perlrun(1)](http://perldoc.perl.org/perlrun.html) for more information.
 
-Python users can similarily set the environment variable
+Python users can similarly set the environment variable
 [PYTHONHASHSEED](https://docs.python.org/2/using/cmdline.html#envvar-PYTHONHASHSEED).
-When set to a given integer value, orders in dictionnaries will be the same on
+When set to a given integer value, orders in dictionaries will be the same on
 every run.
 
 Beware that the [locale settings]({{ "/docs/locales/ | prepend: site.baseurl }})
diff --git a/_docs/timezones.md b/_docs/timezones.md
index c07e7cd..e6a0189 100644
--- a/_docs/timezones.md
+++ b/_docs/timezones.md
@@ -51,7 +51,7 @@ modification times.
 Use date string with timezone information
 -----------------------------------------
 
-Time strings like “Wed, 21 Oct 2015 11:18:50” are inherently ambigious.
+Time strings like “Wed, 21 Oct 2015 11:18:50” are inherently ambiguous.
 Which timezone does it use? How should it be understood?
 
 In the context of reproducible builds, it's best if time strings all
diff --git a/_docs/volatile_inputs.md b/_docs/volatile_inputs.md
index 8e563ab..43fb745 100644
--- a/_docs/volatile_inputs.md
+++ b/_docs/volatile_inputs.md
@@ -4,7 +4,7 @@ layout: docs
 permalink: /docs/volatile-inputs/
 ---
 
-Inputs from the network—even if it doesn’t seem like
+Inputs from the network—even if it doesn't seem like
 it—are volatile. It's best to make a build system not rely
 on remote data.
 
diff --git a/_posts/2015-10-16-new-homepage.markdown b/_posts/2015-10-16-new-homepage.markdown
index 14cd1cd..3f6e7d9 100644
--- a/_posts/2015-10-16-new-homepage.markdown
+++ b/_posts/2015-10-16-new-homepage.markdown
@@ -11,7 +11,7 @@ developers from Bitcoin and the Tor Project. Since then, [several major free
 software projects]({{ "/who/" | prepend: site.baseurl }}) are now actively
 working on supporting reproducible builds.
 
-It was time to increase the visibility of the various initiatives and establigh a
+It was time to increase the visibility of the various initiatives and establish a
 common ground to share general information, specifications, and tutorials. So here's a
 new homepage!
 
diff --git a/index.html b/index.html
index ebb8f99..0cc00c7 100644
--- a/index.html
+++ b/index.html
@@ -39,7 +39,7 @@ layout: home
     <p>
       Most aspect of software verification is done on source code, as that is
       what humans can reasonably understand. But most of the time, computers
-      require software to be first built into long a string of numbers to be
+      require software to be first built into a long string of numbers to be
       used. With <em>reproducible builds</em>, multiple parties can
       <strong>redo this process independently</strong> and ensure they
       <strong>all get <em>exactly</em> the same result</strong>. We can thus
diff --git a/tools.html b/tools.html
index 05dd219..effd113 100644
--- a/tools.html
+++ b/tools.html
@@ -21,7 +21,7 @@ permalink: /tools/
       <a href="https://diffoscope.org/">diffoscope</a> will try to <strong>get
       to the bottom of what makes files or directories different</strong>. It
       will recursively unpack archives of many kinds and transform various
-      binary formats into more human readable forms for comparsion. It can
+      binary formats into more human readable forms for comparison. It can
       compare two tarballs, ISO images, or PDFs just as easily.
     </p>
     <p>

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-website.git

