Signed-off-by: Daniel Kahn Gillmor <d...@fifthhorseman.net>
index.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/index.html b/index.html
index c3808c9..b361343 100644
@@ -37,13 +37,13 @@ layout: home
<div class="eight columns text">
- Most aspect of software verification is done on source code, as that is
+ Most aspects of software verification are 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 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
- <strong>grow confidence</strong> that a distributed binary code is indeed
+ <strong>gain confidence</strong> that a distributed binary code is indeed
coming from a given source code.
@@ -53,7 +53,7 @@ layout: home
about its sensors in a lab environment. Having the source code under
public scrutiny would have made adding such a misfeature only a little
more difficult. Without <em>reproducible builds</em>, it is hard to
- attest than the binary code running in the car was actually made using
+ confirm that the binary code installed in the car was actually made using
the source code that has been verified.
@@ -84,7 +84,7 @@ layout: home
Third, users should be given a way to recreate a close enough build
environment, perform the build process, and <strong>verify that the
- match the original build</strong>.
+ matches the original build</strong>.
Learn more on <a href="/docs/"><strong>how to make your software build
Reproducible-builds mailing list