diff --git a/posts/img-srcset.md b/posts/img-srcset.md
index 3273417a..1c3eb474 100644
--- a/posts/img-srcset.md
+++ b/posts/img-srcset.md
@@ -9,4 +9,4 @@ The `srcset` attribute for images allows you to specify different resolutions or
 
 If you know what size the image will display at, the optional `sizes` attribute helps the browser to decide the most appropriate image before waiting to reflow the entire DOM first. For example, `sizes="100vw"` means a full-width image. (Percentage values will not work here, since the browser will have to answer the question "percent of what?", which requires a full DOM reflow.)
 
-Because `srcset` is an attribute on the standard `<img>` tag, browsers that do not understand it fallback to the image specified in `src`, making this safe to use immediately. Firefox supports `srcset` now as of version 38, but Safari only has [partial support](http://caniuse.com/#feat=srcset) for resolution switching only. A [polyfill](http://scottjehl.github.io/picturefill/) is available if you want to bring this functionality to older browsers and Internet Explorer, but it is not required.
+All major evergreen browsers now support `srcset`. Because `srcset` is an attribute on the standard `<img>` tag, browsers that do not understand it fallback to the image specified in `src`, making this safe to use immediately. Alhtough it is not required, a [polyfill](http://scottjehl.github.io/picturefill/) is available if you want to bring this functionality to older browsers and Internet Explorer.
diff --git a/posts/picture.md b/posts/picture.md
index 4da95c80..75359dbf 100644
--- a/posts/picture.md
+++ b/posts/picture.md
@@ -7,4 +7,4 @@ moreurl: http://www.html5rocks.com/en/tutorials/responsive/picture-element/
 
 The `<picture>` element allows a designer to explicitly specify the right image to use for different scenarios, similar to using media queries but for image tag sources. The element itself is merely a container; any number of `<source>` tags inside of `<picture>` is where all the magic happens. Finally, a required `<img>` element declares the default image to use if no other conditions are met. Browsers that do not support `<picture>` will gracefully fallback to this `<img>` tag, making this safe to use.
 
-Firefox supports `<picture>` now as of version 38, but Internet Explorer and Safari [lacks support](http://caniuse.com/#feat=picture). A [polyfill](http://scottjehl.github.io/picturefill/) is available, but it is not required.
+All major evergreen browsers [support](http://caniuse.com/#feat=picture). `<picture>`. Safari supports it as of version 9.1. For Internet Explorer and older browsers, a [polyfill](http://scottjehl.github.io/picturefill/) is available, but it is not required.