diff --git a/pages/docs/01-start/blacklisting.html b/pages/docs/01-start/blacklisting.html
index e9b76f5..814bb54 100644
--- a/pages/docs/01-start/blacklisting.html
+++ b/pages/docs/01-start/blacklisting.html
@@ -27,7 +27,7 @@ <h2>What to blacklist</h2>
 
 <h2>Blacklist a link</h2>
 
-<p>To blacklist a link, add it a <code>data-no-instant</code> attribute.
+<p>To blacklist a link, add a <code>data-no-instant</code> attribute.
 
 <div class="gist">
 <div class="gist-file">
diff --git a/pages/docs/01-start/download.html b/pages/docs/01-start/download.html
index a4d1fd4..81d7c81 100755
--- a/pages/docs/01-start/download.html
+++ b/pages/docs/01-start/download.html
@@ -47,7 +47,7 @@ <h2>Initialize InstantClick</h2>
 </div>
 </div>
 
-<p>InstantClick is now activated on your website. Read those articles to get a sufficient level of proficiency with InstantClick:
+<p>InstantClick is now activated on your website. Read these articles to get a sufficient level of proficiency with InstantClick:
 
 <ul>
   <li><a href="/how-it-works">How InstantClick works</a> will give you the correct mental model to deal with InstantClick’s mechanism.
diff --git a/pages/docs/01-start/how-it-works.html b/pages/docs/01-start/how-it-works.html
index 40c7f46..dc2b096 100644
--- a/pages/docs/01-start/how-it-works.html
+++ b/pages/docs/01-start/how-it-works.html
@@ -15,7 +15,7 @@ <h2>InstantClick eschews the browser’s page change cycle</h2>
 <ul>
   <li>You can’t rely on <code>DOMContentLoaded</code> or <code>jQuery.ready()</code> to trigger your code (use <a href="/scripts">InstantClick’s events</a> instead).
   <li>Third-party scripts that rely on them might need tweaking (see <a href="/scripts">Events and script re-evaluation</a>).
-  <li>The browser doesn’t show its loading indicator on page changes, <a href="/progress-bar">InstantClick shows his</a>.
+  <li>The browser doesn’t show its loading indicator on page changes, <a href="/progress-bar">InstantClick shows its own</a>.
 </ul>
 
 <p>The second most important thing to understand is that InstantClick only changes the <code>&lt;body&gt;</code> and <code>&lt;title&gt;</code>, so that your scripts are evaluated only once (this brings a nice, noticeable speed boost in and of itself).
diff --git a/pages/docs/02-go-further/assets-changes.html b/pages/docs/02-go-further/assets-changes.html
index f618aa6..3f3e4fe 100644
--- a/pages/docs/02-go-further/assets-changes.html
+++ b/pages/docs/02-go-further/assets-changes.html
@@ -6,7 +6,7 @@ <h1>Tracking assets changes</h1>
 
 <p class="warning">The current way of tracking asset changes is currently a bit clumsy. It will probably be changed later in InstantClick 4.0.
 
-<p>To check when a style sheet or script (either external or inline) is updated, add it a <code>data-instant-track</code> attribute:
+<p>To check when a style sheet or script (either external or inline) is updated, add a <code>data-instant-track</code> attribute:
 
 <div class="gist">
 <div class="gist-file">
diff --git a/pages/index.html b/pages/index.html
index 9178261..bdb334c 100755
--- a/pages/index.html
+++ b/pages/index.html
@@ -30,7 +30,7 @@ <h2>How does it work</h2>
 
 <p>If you don’t want any wasted requests, you may preload on “mousedown”. This is when you press your mouse button (a click is when you release it).
 
-<p>When loading pages with InstantClick, the browser doesn’t show its standard loading indicators anymore. To make sure the user knows a page has changed, InstantClick includes a (customizable) progress bar.<sup id="note-progress-bar-back"><a href="#note-progress-bar">3</a></sup> The bar automatically scales to appropriate size on mobile devices, so it works even when your site isn’t optimized for mobile.
+<p>When loading pages with InstantClick, the browser doesn’t show its standard loading indicators anymore. To make sure the user knows a page has changed, InstantClick includes a (customizable) progress bar.<sup id="note-progress-bar-back"><a href="#note-progress-bar">3</a></sup> The bar automatically scales to the appropriate size on mobile devices, so it works even when your site isn’t optimized for mobile.
 
 <hr>