[rb-commits] [website] master: native en_US speaker website tweaks (c01f9d9)

[lunar at jenkins.debian.net]

Repository : ssh://jenkins/website

On branch  : master

>---------------------------------------------------------------

commit c01f9d996a7b78234209a8bc3a344e2ceab68178
Author: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
Date:   Tue Nov 10 16:30:45 2015 -0500

    native en_US speaker website tweaks


>---------------------------------------------------------------

c01f9d996a7b78234209a8bc3a344e2ceab68178
 index.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.html b/index.html
index c3808c9..b361343 100644
--- a/index.html
+++ b/index.html
@@ -37,13 +37,13 @@ layout: home
   </div>
   <div class="eight columns text">
     <p>
-      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.
     </p>
     <p>
@@ -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.
     </p>
     <p>
@@ -84,7 +84,7 @@ layout: home
     <p>
       Third, users should be given a way to recreate a close enough build
       environment, perform the build process, and <strong>verify that the output
-      match the original build</strong>.
+      matches the original build</strong>.
     </p>
     <p>
       Learn more on <a href="/docs/"><strong>how to make your software build