updating beverloo's fixes

index.html

@@ -555,7 +555,7 @@ <h2 class="name">font-feature-settings </h2>
             </header>
             <div class="more">
               <div class="recco">
-                <p>IE10 and Firefox 4 support low level control over font feature settings. What this means is other browsers merely will not render the flourishes you seek. </p>
+                <p>Internet Explorer 10 and Firefox 4 support low level control over font feature settings. What this means is other browsers merely will not render the flourishes you seek. Many features available through the property may be extracted to separate properties in the future, such as font-variant-ligatures. </p>
               </div>
               <div class="polyfills"></div> 
 
@@ -605,7 +605,7 @@ <h2 class="name">geolocation </h2>
             </header>
             <div class="more">
               <div class="recco">
-                <p><a href="https://gist.github.com/366184">geolocation shim</a> uses Google's IP-geocoding service as a fallback. <a href="http://code.google.com/p/geo-location-javascript/">geo-location-javascript</a> doesn't but has hooks into Blackberry, WebOS, and Google Gears specific APIs. In most cases, you should just not expose geo features in your app if the feature is not natively present.</p>
+                <p><a href="https://gist.github.com/366184">geolocation shim</a> uses Google's IP-GeoCoding service as a fallback. <a href="http://code.google.com/p/geo-location-javascript/">geo-location-javascript</a> doesn't but has hooks into BlackBerry, WebOS, and Google Gears specific APIs. In most cases, you should just not expose Geo features in your app if the feature is not natively present.</p>
               </div>
               <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://gist.github.com/366184">geolocation shim</a>, <a href="http://code.google.com/p/geo-location-javascript/">geo-location-javascript</a></p></div> 
 
@@ -631,7 +631,7 @@ <h2 class="name">gradients </h2>
               <div class="recco">
                 <p>We strongly recommend you use all the prefixes (<code>-o-</code>, <code>-webkit</code>, <code>-ms-</code>, <code>-moz-</code>) when you provide gradients as image values (<code>background</code> or <code>border-image</code>). Do provide a fallback color if you are using this as a value for <code>background</code> so browsers that do not support the gradients can render a solid background color. </p>
 
-<p>We also suggest you drop old webkit syntax and only use the <a href="https://developer.mozilla.org/en/CSS/-moz-linear-gradient">newer syntax</a> for gradient values and <a href="http://www.broken-links.com/2012/01/11/the-new-and-hopefully-final-linear-gradient-syntax/">not the latest one</a> (yet) until <a href="http://www.w3.org/TR/css3-images/">the spec</a> hits Candidate Recommendation. </p>
+<p>We also suggest you drop old WebKit syntax and only use the <a href="https://developer.mozilla.org/en/CSS/-moz-linear-gradient">latest syntax</a> for gradient values and <a href="http://www.broken-links.com/2012/01/11/the-new-and-hopefully-final-linear-gradient-syntax/">not the latest one</a> (yet) until <a href="http://www.w3.org/TR/css3-images/">the specification</a> hits Candidate Recommendation. </p>
               </div>
               <div class="polyfills"></div> 
 
@@ -655,7 +655,7 @@ <h2 class="name">grids </h2>
             </header>
             <div class="more">
               <div class="recco">
-                <p>This is also a spec that is in a flux. Older versions of the spec has found implementation, but you should wait until the spec is more stable to use this. </p>
+                <p>The <a href="http://dev.w3.org/csswg/css3-grid-align/">CSS Grid Layout</a> specification supersedes several older ones, and only features an experimental implementation in Internet Explorer 10. Until the specification matures and more implementations exist, we suggest that you avoid using this.</p>
               </div>
               <div class="polyfills"></div>