More textual changes

posts/animations.md

@@ -4,4 +4,4 @@ tags: fallback
 kind: css
 polyfillurls:
 
-CSS Animations are still in a flux. The Working Group has [decided to provide](http://www.w3.org/2012/01/13-svg-minutes.html#action02) a universal animation spec that would work across CSS, SVG and HTML. For now, use animations for providing additional glamour and use feature detection to provide alternative experience on browsers that do not support this feature for critical animations.
+CSS Animations are still in a flux. The Working Group has [decided to provide](http://www.w3.org/2012/01/13-svg-minutes.html#action02) a universal animation spec that would work across CSS, SVG and HTML. For now, use animations for providing additional glamour and use feature detection to provide alternative experience for browsers that do not support this feature in case the animation is critical.

posts/audio.md

@@ -4,4 +4,4 @@ tags: polyfill
 kind: html
 polyfillurls: [jPlayer](https://github.com/happyworm/jPlayer), [Sound Manager 2](http://www.schillmania.com/projects/soundmanager2/)
 
-As with video, you need to provide your audio file in multiple formats for these to work—you'll need [Ogg and AAC](http://www.scirra.com/blog/44/on-html5-audio-formats-aac-and-ogg). jPlayer has a jQuery dependency. Sound Manager has an extensive API for further customization. 
+As is the case with video, you need to provide your audio file in multiple formats for these to work, namely in [Ogg Vorbis and AAC](http://www.scirra.com/blog/44/on-html5-audio-formats-aac-and-ogg). jPlayer has a jQuery dependency. Sound Manager has an extensive API for further customization. 

posts/border-image.md

@@ -4,4 +4,4 @@ tags: fallback prefixes
 kind: css
 polyfillurls:
 
-Make sure to use all the right prefixes (`-o-`, `-webkit`, `-ms-`, `-moz-`); additionally, [border-image.com](http://border-image.com/) may help. You should let this fallback to either a normal solid border or no border at all (depending on whether a border is essential for readability). We recommend you avoid polyfills. 
+Make sure to use all the right prefixes (`-o-`, `-webkit-`, `-ms-`, `-moz-`). Additionally, [border-image.com](http://border-image.com/) may help. You should let this fallback to either a normal solid border or no border at all, depending on whether a border is essential for readability. We recommend that you avoid polyfills. 

posts/box-reflection.md

@@ -5,4 +5,4 @@ kind: css
 polyfillurls:
 moreurl: http://www.webkit.org/blog/182/css-reflections/
 
-Box reflection has never been part of a CSS specification. Parts of what you can do with box-reflection would be possible to do with CSS Filters. Until then, you should avoid using WebKit-only reflection.
+Box reflection has never been part of a CSS specification. Parts of what you can do with box-reflection would be possible to immitate using CSS Filters. Until then, you should avoid using WebKit-only reflection.

posts/dataset.md

@@ -4,4 +4,4 @@ tags: fallback noie nooldmobile
 kind: api
 polyfillurls:[HTML5 dataset support](http://eligrey.com/blog/post/html-5-dataset-support)
 
-`elem.dataset` is unsupported in IE and older mobile browsers. Using data-* attributes will be totally fine in all browsers, but instead of using `elem.dataset.foo` just use `elem.getAttribute('data-foo')`. A polyfill is availble if you want terser syntax.
+`elem.dataset` is unsupported in Internet Explorer and older mobile browsers. Using data-* attributes will be totally fine in all browsers, but instead of using `elem.dataset.foo` just use `elem.getAttribute('data-foo')`. A polyfill is availble if you want terser syntax.

posts/details.md

@@ -4,4 +4,4 @@ tags: polyfill
 kind: html
 polyfillurls: [Details](http://mathiasbynens.be/notes/html5-details-jquery), [jquery-details](http://akral.bitbucket.org/details-tag)
 
-Use the details element if you intend to show a summary which when clicked reveals detailed information. 
+Use the details element if you intend to show a summary which when clicked reveals detailed information. Without any fallback, non-supporting browsers will fall back to displaying the element in the opened state.

posts/dragndrop.md

@@ -4,4 +4,4 @@ tags: polyfill nomobile
 kind: api
 polyfillurls:[dropfile](https://github.com/MrSwitch/dropfile), [fileSaver](https://github.com/eligrey/FileSaver.js), [jDataView](https://github.com/vjeux/jDataView)
 
-Drag n Drop was standardized in HTML5 but based on IE's original implementation. So it has wide support (except Opera), but many feel frustrated when using the API. You may want to use jQuery UI Draggable (or another JS library) to handle this for you.  Meanwhile the proposed [[dropzone]](http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#the-dropzone-attribute) attribute will improve the situation as it gains browser support.
+Drag and Drop has been standardized in HTML5 based on Internet Explorer's original implementation. It therefore has wide support (except Opera), but many feel frustrated when using the API. You may want to use jQuery UI Draggable (or another JavaScript library) to handle this for you. Meanwhile the proposed [[dropzone]](http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#the-dropzone-attribute) attribute will improve the situation as it gains browser support.

posts/flexbox.md

@@ -4,4 +4,4 @@ tags: none
 kind: css
 polyfillurls:
 
-Unfortunately, older versions of this spec have been implemented in Gecko, Webkit and Trident. But [the spec](http://dev.w3.org/csswg/css3-flexbox/) has changed significantly (starting from the syntax), hence we recommend you avoid using this until the stable version of the spec finds wide-spread implementation.
+Unfortunately, older versions of this spec have been implemented in Gecko, WebKit and Trident. But [the spec](http://dev.w3.org/csswg/css3-flexbox/) has changed significantly (starting from the syntax), hence we recommend you avoid using this until the stable version of the spec finds wide-spread implementation.

posts/history.md

@@ -4,4 +4,4 @@ tags: fallback
 kind: api
 polyfillurls:[History.js](https://github.com/balupton/history.js), [pjax](http://pjax.heroku.com/)
 
-`pushState` gives you real proper URLs along with permalinks to dynamic app state. You can use it and fall back to page refreshes if you'd like. Alternatively, History.js smooths out some browser implementation differences and an and optional hashchange fallback for HTML4 browsers. PJax (pushState + ajax) is what is used by Github for their fallback solution.
+`pushState` gives you real proper URLs along with permalinks to dynamic app state. You can use it and fall back to page refreshes if you'd like. Alternatively, History.js smooths out some browser implementation differences and an and optional hashchange fallback for HTML 4 browsers. PJax (pushState + ajax) is what is used by Github for their fallback solution.

posts/html5-sectioningelements.md

@@ -4,12 +4,12 @@ tags: gtie8,polyfill,article,header,nav
 kind: html
 polyfillurls: [html5shiv](http://code.google.com/p/html5shiv/), [html5shiv (github)](https://github.com/aFarkas/html5shiv/), [accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js)
 
-All browsers except oldIE (IE <=8) handle new sectioning elements (like `<header>`, `<footer>`, `<nav>`, `<article>`, and `<section>`) fine. However they aren’t always mapped to accessibility APIs as the [HTML5 spec](http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria) requires. Currently [only Firefox does this}(http://html5accessibility.com/) but other browsers are implementing the a11y APIs quickly. In the meantime, [Accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js) maps them correctly.
+All browsers except oldIE (IE <=8) handle new sectioning elements (like `<header>`, `<footer>`, `<nav>`, `<article>`, and `<section>`) fine. However they aren’t always mapped to accessibility APIs as the [HTML5 spec](http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria) requires. Currently [only Firefox does this](http://html5accessibility.com/) but other browsers are implementing the a11y APIs quickly. In the meantime, [Accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js) maps them correctly.
 
 The notes below only apply to oldIE:
 
 The [html5shiv](http://code.google.com/p/html5shiv/) enables you to use these in your markup (and Modernizr does the exact same by default). 
 
 If you introduce some of these elements later on (via AJAX or templating), html5shiv will also handle this for you (as of v3). [jQuery 1.7](http://blog.jquery.com/2011/11/03/jquery-1-7-released/) also has this functionality baked in.
 
-Lastly, if you need these elements to print correctly, use [html5shiv-printshiv.js](https://github.com/aFarkas/html5shiv/blob/master/src/html5shiv-printshiv.js) which addresses an IE bug there.
+Lastly, if you need these elements to print correctly, use [html5shiv-printshiv.js](https://github.com/aFarkas/html5shiv/blob/master/src/html5shiv-printshiv.js) which addresses an IE bug there.

posts/indexeddb.md

@@ -6,4 +6,4 @@ polyfillurls: [IDBWrapper](https://github.com/jensarps/IDBWrapper)
 
 IndexedDB was a volatile spec for a year, but has settled down. In addition to Chrome and Firefox, IE10 will have it; Opera and Safari have not yet committed to it.
 
-[IDBWrapper](https://github.com/jensarps/IDBWrapper) helps smooth out the cross-browser differences. You may still want to use WebSQL DB when IDB isn't present.
+[IDBWrapper](https://github.com/jensarps/IDBWrapper) helps smooth out the cross-browser differences. You may consider falling back to WebSQL when IndexedDB isn't available, but do keep in mind that WebSQL has been abandoned.

posts/match-media.md

@@ -4,4 +4,4 @@ tags: polyfill
 kind: api
 polyfillurls:
 
-matchMedia provides a javascript API to see if a media query will succeed. [MatchMedia.js](https://github.com/paulirish/matchMedia.js/) provides a shim for unsupported browsers. If you want a shim that is responsive to window resizing, you can use [this fork](http://www.paulrhayes.com/2011-11/use-css-transitions-to-link-media-queries-and-javascript/), though its limited to browsers that support css transitions.
+matchMedia provides a JavaScript API to see if a media query will succeed. [MatchMedia.js](https://github.com/paulirish/matchMedia.js/) provides a shim for unsupported browsers. If you want a shim that is responsive to window resizing, you can use [this fork](http://www.paulrhayes.com/2011-11/use-css-transitions-to-link-media-queries-and-javascript/), though its limited to browsers that support CSS Transitions.

posts/multicolumn.md

@@ -4,6 +4,6 @@ tags: prefixes gtie9
 kind: css
 polyfillurls:
 
-Internet Explorer (10+), and Opera support CSS Multiple Column without vendor prefixes, so you only need prefixed versions for `-webkit` and `-moz`. A further note, features like `column-break-after`, `column-break-before`, and `column-break-inside` which are necessary for advanced typography are webkit-only right now. 
+Internet Explorer (10+), and Opera support CSS Multiple Column without vendor prefixes, so you only need prefixed versions for `-webkit-` and `-moz`. A further note, features like `column-break-after`, `column-break-before`, and `column-break-inside` which are necessary for advanced typography are WebKit-only right now. 
 
 We recommend you do not polyfill this and let it fall back to single column text.

posts/opacity.md

@@ -4,4 +4,4 @@ tags: gtie8
 kind: css
 polyfillurls:
 
-CSS3 opacity allows you to set transparency to html elements and is safe to use.  For IE6-IE8, use the proprietary "filter" property to achieve the same effect.
+CSS3 opacity allows you to set transparency to html elements and is safe to use. For IE6-IE8, use the proprietary "filter" property to achieve the same effect.

posts/text-stroke.md

@@ -4,4 +4,4 @@ tags: none
 kind: css
 polyfillurls:
 
-Text stroke adds an outline or stroke to text and and is only supported by webkit. Text stroke has never been not part of the CSS spec and should be avoided.
+Text stroke adds an outline or stroke to text and and is only supported by WebKit. Text stroke has never been not part of a CSS specification and should be avoided.