Update RICG-newsletter-2015-01-23.md

Removed a duplicate word, added some commas

RICG-newsletter-2015-01-23.md

@@ -6,13 +6,13 @@
 
 Let’s talk about [WordPress](https://wordpress.org). According to some [websites](http://trends.builtwith.com/cms) that I just [found](https://managewp.com/14-surprising-statistics-about-wordpress-usage), the venerable pile of PHP and MySQL that we call “WordPress” serves up *1 in every 5 websites* and runs *more than half* of all websites that use a CMS at all.
 
-So it’s high time that WordPress had proper responsive image support. Tim Evko wrote [a fine blog post](http://web-design-weekly.com/2015/01/20/ricg-responsive-images-plugin/) about the efforts that he, along with with our illustrious chair and a few members of the WordPress core team, has made to create a drop-in responsive images plugin for WordPress. The plugin can be had [here](https://wordpress.org/plugins/ricg-responsive-images/) and its source lives [here](https://github.com/ResponsiveImagesCG/wp-tevko-responsive-images). It does the hard work of creating a range of source files from a single high-resolution image, and marking them up with `srcset` and `sizes`. If you want to art-direct your WordPress-hosted images, you’ll need to use `picture`; as luck has it Rory Douglas [wrote a thing](http://terrificwebdesign.net/use-case/) about how to do *that* last week, too.
+So it’s high time that WordPress had proper responsive image support. Tim Evko wrote [a fine blog post](http://web-design-weekly.com/2015/01/20/ricg-responsive-images-plugin/) about the efforts that he, along with our illustrious chair and a few members of the WordPress core team, has made to create a drop-in responsive images plugin for WordPress. The plugin can be had [here](https://wordpress.org/plugins/ricg-responsive-images/) and its source lives [here](https://github.com/ResponsiveImagesCG/wp-tevko-responsive-images). It does the hard work of creating a range of source files from a single high-resolution image, and marking them up with `srcset` and `sizes`. If you want to art-direct your WordPress-hosted images, you’ll need to use `picture`; as luck has it, Rory Douglas [wrote a thing](http://terrificwebdesign.net/use-case/) about how to do *that* last week, too.
 
 ## Alternate formats
 
 I love JPEG! [Mozilla likes it too](http://calendar.perfplanet.com/2014/mozjpeg-3-0/). The 22-year-old format recently received the strangest, highest compliment I have ever heard an engineer give when a researcher for the (awesome, exciting, in-development) Daala video standard [called it “alien technology from the future.”](https://people.xiph.org/~xiphmont/demo/daala/update1.shtml)
 
-But, while JPEG was the first image format to dominate the web, it will not be the last. New formats are coming; new formats are already here. `picture`, `source` and the `type` attribute let us use them now while providing fallbacks for non-supporting browsers.
+But, while JPEG was the first image format to dominate the web, it will not be the last. New formats are coming; new formats are already here. `picture`, `source` and the `type` attribute let us use them now, while providing fallbacks for non-supporting browsers.
 
 Jason Grigsby [posted a thing about `picture` and `type`-switching on the Cloud Four blog](http://blog.cloudfour.com/when-to-use-picture-for-resolution-switching/) this week; Zolton Dulac wrote [a *huge* article](http://www.useragentman.com/blog/2015/01/14/using-webp-jpeg2000-jpegxr-apng-now-with-picturefill-and-modernizr/) detailing the different formats currently on offer, when you should use each, and how to serve them to as many users as possible without breaking things for older browsers by using Modernizr and Picturefill. Read! Implement!