[Reproducible-commits] [reproducible-website] 11/55: Typo fixes

Tue Aug 23 13:39:50 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 77ce01bce6b4b6632e3b89b9294592ed191a054b
Author: Niko Tyni <ntyni at debian.org>
Date:   Mon Nov 2 17:23:12 2015 +0200

    Typo fixes
---
 _docs/build_path.md                  | 2 +-
 _docs/build_toolchain_from_source.md | 2 +-
 _docs/definition_strategies.md       | 2 +-
 _docs/perimeter.md                   | 4 ++--
 _docs/recording.md                   | 2 +-
 _docs/stable_inputs.md               | 4 ++--
 _docs/stable_outputs.md              | 2 +-
 _docs/timezones.md                   | 6 +++---
 _docs/value_initialization.md        | 2 +-
 9 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/_docs/build_path.md b/_docs/build_path.md
index 1e94049..6d83d73 100644
--- a/_docs/build_path.md
+++ b/_docs/build_path.md
@@ -25,6 +25,6 @@ change them after a build to a pre-determined value[^debugedit]. A work-around i
 [^debugedit]: [debugedit](https://fedoraproject.org/wiki/Releases/FeatureBuildId) can replace the path used at build time by a predefined one but it will do it by rewriting bytes in place. As this does not reorder the hash table of strings, the resulting bytes will still be different depending on the original build path.
 
 This is also problematic because this will also apply to intermediate
-source file that other tools generate. As they typically will use [random
+source files that other tools generate. As they typically will use [random
 file names]({{ "/docs/randomness/" | prepend: site.baseurl }}), having a
 fixed build path will not be enough in such cases.
diff --git a/_docs/build_toolchain_from_source.md b/_docs/build_toolchain_from_source.md
index 6ba6dae..64a3b93 100644
--- a/_docs/build_toolchain_from_source.md
+++ b/_docs/build_toolchain_from_source.md
@@ -37,7 +37,7 @@ Another approach is to check the source of the entire toolchain in the
 project's version control system.
 
 This is how several integrated operating systems like *BSD are
-developped. “Building the world” will start by building the toolchain in
+developed. “Building the world” will start by building the toolchain in
 the version control system before building the rest of the system.
 
 It's also how it is done for Google's internal projects. They have
diff --git a/_docs/definition_strategies.md b/_docs/definition_strategies.md
index a418581..b184ac5 100644
--- a/_docs/definition_strategies.md
+++ b/_docs/definition_strategies.md
@@ -37,7 +37,7 @@ Reference distribution
 ----------------------
 
 Using a specific version of free software distribution is another viable
-options for a build environment.
+option for a build environment.
 
 Ideally, it should offer stable releases (like Debian, CentOS, or
 FreeBSD) to avoid having constant updates to the documentation or
diff --git a/_docs/perimeter.md b/_docs/perimeter.md
index 09b9e66..91e9028 100644
--- a/_docs/perimeter.md
+++ b/_docs/perimeter.md
@@ -49,8 +49,8 @@ build process and versions that must be used.
 The rest can be different from one project to the next, as long as it
 can be reproduced by interested users. To give some examples:
 
- * specific operating system if cross-compiling is not supported),
- * build system architecture if cross-compiling is not supported),
+ * specific operating system (if cross-compiling is not supported),
+ * build system architecture (if cross-compiling is not supported),
  * directory where the build must happen,
  * name of the user running the build,
  * locale,
diff --git a/_docs/recording.md b/_docs/recording.md
index 9bb85ad..8b9d37a 100644
--- a/_docs/recording.md
+++ b/_docs/recording.md
@@ -5,7 +5,7 @@ permalink: /docs/recording/
 ---
 
 It is been customary in user facing software to provide a way for
-developpers investigating bugs to learn how the software has been
+developers investigating bugs to learn how the software has been
 built. The “about dialog” or output of `--version` would contain
 information about the build environment.
 
diff --git a/_docs/stable_inputs.md b/_docs/stable_inputs.md
index 1ae9312..2c0bf69 100644
--- a/_docs/stable_inputs.md
+++ b/_docs/stable_inputs.md
@@ -27,7 +27,7 @@ tool: $(SRCS:.c=.o)
 
 Solutions:
 
-a) List all inputs explicitely and ensure they will be processed in that order.
+a) List all inputs explicitly and ensure they will be processed in that order.
 
 <div class="correct">
 {% highlight makefile %}
@@ -84,6 +84,6 @@ $ find src -print0 | LC_ALL=C sort -z |
 {% endhighlight %}
 </div>
 
-This might not be the only changes required for [Tar and other archive
+This might not be the only change required for [Tar and other archive
 formats]({{ "/docs/archives/" | prepend: site.baseurl }}) as they
 usually embed more metadata problems.
diff --git a/_docs/stable_outputs.md b/_docs/stable_outputs.md
index fd181b2..00c4df0 100644
--- a/_docs/stable_outputs.md
+++ b/_docs/stable_outputs.md
@@ -21,7 +21,7 @@ foreach my $package (keys %deps) {
 {% endhighlight %}
 </div>
 
-To get a deterministic output, the easiest way is to explicitely sort the keys:
+To get a deterministic output, the easiest way is to explicitly sort the keys:
 
 <div class="correct">
 {% highlight perl %}
diff --git a/_docs/timezones.md b/_docs/timezones.md
index 94e6279..cde0af4 100644
--- a/_docs/timezones.md
+++ b/_docs/timezones.md
@@ -56,11 +56,11 @@ For which timezone does it apply? How should it be understood?
 
 In the context of reproducible builds, it's best if time strings all
 contain timezone information. A fallback option is to assume they are all
-specificied as UTC.
+specified as UTC.
 
-If times trings without timezone specification are parsed in the
+If time strings without timezone specification are parsed in the
 timezone of the build system, hard to understand behavior might happen.
-An example is extra hours when doing time computations accross two days
+An example is extra hours when doing time computations across two days
 with different daylight saving changes. As different timezones have
 different policies, one user might get different results depending on
 the timezone used to perform the build.
diff --git a/_docs/value_initialization.md b/_docs/value_initialization.md
index 48e4ad6..73d7a75 100644
--- a/_docs/value_initialization.md
+++ b/_docs/value_initialization.md
@@ -4,7 +4,7 @@ layout: docs
 permalink: /docs/value-initialization/
 ---
 
-In languages which don't initialize values, this needs to be explicitely
+In languages which don't initialize values, this needs to be explicitly
 done in order to avoid capturing what random bytes are in memory when
 run.
 

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

