[Git][reproducible-builds/reproducible-website][master] 8 commits: Fix misspellings

Mattia Rizzolo gitlab at salsa.debian.org
Fri Jul 3 12:28:49 UTC 2020 


Mattia Rizzolo pushed to branch master at Reproducible Builds / reproducible-website


Commits:
04e943e3 by Gonzalo Bulnes Guilpain at 2020-07-03T20:46:13+10:00
Fix misspellings

- - - - -
1b86b330 by Gonzalo Bulnes Guilpain at 2020-07-03T20:47:47+10:00
Remove trailing whitespaces

- - - - -
b06b9d1b by Gonzalo Bulnes Guilpain at 2020-07-03T20:48:19+10:00
Fix product name case

- - - - -
dfdde389 by Gonzalo Bulnes Guilpain at 2020-07-03T20:49:39+10:00
Fix dangling pronoun

The context doesn't mention who "theirs" refers to.
I assume the software users are the one with interest in building it.

- - - - -
9cb4ffa0 by Gonzalo Bulnes Guilpain at 2020-07-03T20:54:29+10:00
Reword sentence for clarity

- - - - -
9aa37965 by Gonzalo Bulnes Guilpain at 2020-07-03T20:55:25+10:00
Reword sentence for clarity

- - - - -
3685ff35 by Gonzalo Bulnes Guilpain at 2020-07-03T21:58:49+10:00
Reword example for clarity

- - - - -
81ee3248 by Gonzalo Bulnes Guilpain at 2020-07-03T21:58:49+10:00
Fix minor grammar issue, reword sentence

"Weird" is a somewhat charged word, I believe "unexpected" would
work just as well in this context.

- - - - -


5 changed files:

- _docs/buy_in.md
- _docs/jvm.md
- _docs/perimeter.md
- _docs/plans.md
- _docs/system_images.md


Changes:

=====================================
_docs/buy_in.md
=====================================
@@ -17,7 +17,7 @@ In March 2015, The Intercept
 [published](https://theintercept.com/2015/03/10/ispy-cia-campaign-steal-apples-secrets/)
 from the Snowden leaks the abstract of a talk at an
 [internal CIA conference in
-2012](https://theintercept.com/document/2015/03/10/tcb-jamboree-2012-invitation/) about 
+2012](https://theintercept.com/document/2015/03/10/tcb-jamboree-2012-invitation/) about
 [Strawhorse: Attacking the MacOS and iOS Software Development
 Kit](https://theintercept.com/document/2015/03/10/strawhorse-attacking-macos-ios-software-development-kit/).
 The abstract clearly explains how unnamed researchers have been creating
@@ -32,7 +32,7 @@ embedded in iOS applications. Palo Alto Networks
 > XcodeGhost is the first compiler malware in OS X. Its malicious code is
 > located in a Mach-O object file that was repackaged into some versions
 > of Xcode installers. These malicious installers were then uploaded to
-> Baidu’s cloud file sharing service for used by Chinese iOS/OS X
+> Baidu’s cloud file sharing service for use by Chinese iOS/OS X
 > developers
 
 The purpose of *reproducible builds* is exactly to resist such attacks.
@@ -106,7 +106,7 @@ development speeds and lower cost.
 
 Build speeds can also be improved by showing that cross-compilation
 produces the same result as native compilation and then doing the
-mojority of builds with cross-compilation on faster machines.
+majority of builds with cross-compilation on faster machines.
 
 “But how can I trust my compiler?”
 ----------------------------------


=====================================
_docs/jvm.md
=====================================
@@ -4,7 +4,7 @@ layout: docs
 permalink: /docs/jvm/
 ---
 
-The conventions for the JVM ecosystem are under active development, 
+The conventions for the JVM ecosystem are under active development,
 see how-to [contribute]({{ "/contribute/" | relative_url }}).
 
 The JVM ecosystem provides many languages and build tools.
@@ -92,15 +92,15 @@ But you can try to rebuild them and measure how much they are not reproducible:
 
 1. download the jar from a public repository,
 2. determine which major version of JDK was used to produce it: usually, the full Java version is found in `META-INF/MANIFEST.MF` by running `unzip -p xxx.jar META-INF/MANIFEST.MF`
-3. find sources and build instruction on originating project site
+3. find sources and build instructions on originating project site
 4. rebuild with a JDK of the same major version than the version found on step 2
 4. examine the differences using [diffoscope](https://diffoscope.org/)
 
 Usually, you'll find a few files that are different, in addition to zip content timestamp and order.
 Notice that if you didn't use the same JDK major version, you'll see many differences in .class files.
 
-Improving the build to get reproducible build will then be specific with each build tool.
-You may discuss issues and fixes on [Reproducible Builds mailinglist]({{ "/docs/contribute/" | relative_url }}).
+Improving the build to get reproducible builds will then be specific to each build tool.
+You may discuss issues and fixes on the [Reproducible Builds mailing list]({{ "/docs/contribute/" | relative_url }}).
 
 ## Reproducible Builds for Maven
 
@@ -121,9 +121,9 @@ Classical arguments contain following patterns:
 - `package` phase: no need to `deploy` or even `install`
 - `-Dmaven.test.skip`: avoid running tests and even compiling tests
 - `-DskipTests`: avoid running tests, but still builds (necessary for some projects)
-- `-Dgpg.skip`: avoid pgp signing
+- `-Dgpg.skip`: avoid PGP signing
 - `-Papache-release` or any release profile: activate release-specific tasks used by `maven-release-plugin`
-- `-Dline.separator=$'\r\n'`: define Windows line endings from an Unix environmenent
+- `-Dline.separator=$'\r\n'`: define Windows line endings from an Unix environment
 
 ### multi-module build
 For multi-module builds, each produced artifact will have its


=====================================
_docs/perimeter.md
=====================================
@@ -24,8 +24,8 @@ each project. There might even be several build environments for a
 single release to accommodate different target operating systems.
 But there are some important aspects common to all environments.
 
-It should be **easy to install** a matching build environment on their
-system. Ideally it should only be made of free software available on
+It should be **easy to install** a matching build environment on the users'
+systems. Ideally it should only be made of free software available on
 public Internet sites. The best way to provide the environment is
 probably using a documented and easily understood script.
 


=====================================
_docs/plans.md
=====================================
@@ -57,8 +57,8 @@ Providing a comparison protocol
 Users must have an easy way to recreate the build environment, get the
 source code, perform the build, and compare the results.
 
-Ideally, the comparison protocol should be simple to see if resulting
-binaries are identical. Comparing bytes or cryptographic hash
+Ideally, the comparison protocol to verify that resulting
+binaries are identical should be simple. Comparing bytes or cryptographic hash
 values is easy to do and understand.
 
 Other technologies might require removing cryptographic signatures or


=====================================
_docs/system_images.md
=====================================
@@ -15,7 +15,7 @@ Usually the problems are:
 
 * Filesystem needs to be created *at once*
 * Filesystems have creation and/or modification timestamps
-* Filesystems containing UUID or a label which are not set explicit
+* Filesystems containing UUID or a label which are not set explicitly
 * Included files have timestamps
 * Included files may be generated or updated at build time in a non-reproducible manner
 * The bootloader which is integrated might have timestamps
@@ -87,8 +87,8 @@ E.g. Tails does this:
 
 Beware: this can have hard to predict consequences. For example,
 Tails considered dropping even more stuff - such as the fontconfig cache -,
-but they've seen weird results and performance issues when doing so
-and finally discarded this idea.
+but they've seen unexpected results and performance issues when doing so
+and finally discarded the idea.
 
 Files metadata
 --------------
@@ -112,8 +112,8 @@ In order to counter this, one possible approach is to replace these scripts and
 later (e.g. at first boot).
 
 Another approach is to ensure these scripts generate/update files
-in a reproducible manner. This approach has the advantage to fix the problem
-at the cause for every project that uses these programs.
+in a reproducible manner. This approach has the advantage of addressing the root cause
+of the problem and fixing it for every project that uses these programs.
 For example such problems were fixed in:
 
  - `/etc/kernel/postinst.d/apt-auto-removal`:
@@ -143,8 +143,8 @@ gettext
 GNU gettext's POT, PO and MO files were an interesting challenge.
 One way to approach this problem is to:
 
-* only update POT files when it is really needed, i.e. if the only change
-  after refreshing them is in the POT-Creation-Date field;
+* only update POT files when it is really needed, e.g. if the POT-Creation-Date field
+  is the only change after refreshing a POT file, the file doesn't need to be updated;
 * avoid updating PO — and thus MO — files when only comments (e.g.
   line numbers) have changed.
   <https://git-tails.immerda.ch/tails/tree/config/chroot_local-includes/usr/local/lib/tails-shell-library/po.sh>



View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/02be51587733c8acf44445c53fee39cf11896e5e...81ee3248f4fbb9e5d3108f0e533c9349ecde35b9

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/02be51587733c8acf44445c53fee39cf11896e5e...81ee3248f4fbb9e5d3108f0e533c9349ecde35b9
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-commits/attachments/20200703/181346f5/attachment.htm>

More information about the rb-commits mailing list