Merge branch 'gh-pages'

README.md

@@ -12,9 +12,9 @@ Offline caching for [picturefill](https://github.com/scottjehl/picturefill) resp
 
 Responsive images and offline application caching do not play well together. For an explanation, see "Gotcha #6" of Jake Archibald's ["Application Cache is a Douchebag"](http://www.alistapart.com/articles/application-cache-is-a-douchebag/).
 
-Pickyfill (partially) solves the problem using Scott Jehl's picturefill as a starting point. Pickyfill stores responsive images as data URLs in LocalStorage. If your page is using the HTML5 offline Appcache, pickyfill will detect this and store picturefill images as they are loaded. It will only store the images that your device displays, so (for example) an iPhone will only cache iPhone-sized images; it will not download and store crazy large images designed for large screens.  
+Pickyfill (partially) solves the problem using Scott Jehl's picturefill as a starting point. Pickyfill stores responsive images as data URLs in LocalStorage. If your page is using the HTML5 offline Appcache, pickyfill will detect this and store picturefill images as they are loaded. It will only store the images that your device displays, so (for example) an iPhone will only cache iPhone-sized images; it will not download and store crazy large images designed for gigantic screens.  
 
-Pickyfill makes the cached images available if the user is offline. It can also improves page load time if the user is on a slow network.
+Pickyfill makes the cached images available if the user is offline. It can also improve page load time if the user is on a slow network.
 
 ## Support, or Where Won't This Work?
 
@@ -57,4 +57,4 @@ Because pickyfill will only cache images that are actually displayed, it is poss
 ```
 FALLBACK:
 imgs/    imgs/fallback.png
-```
+```