Update 2017-03-19-ember-2-12-released.md

source/blog/2017-03-19-ember-2-12-released.md

@@ -207,22 +207,22 @@ and [addons](https://github.com/ember-cli/ember-addon-output/compare/v2.11.0...v
 #### Switch to ESLint
 
 Ember CLI will now generate new projects with an ESLint setup. This changes the default linting system from JSHint (which has been used
-since we initially added linting support to ember-cli) to ESLint. The new project setup uses a fairly simple `.eslinrc.js` relying
+since we initially added linting support to Ember CLI) to ESLint. The new project setup uses a fairly simple `.eslinrc.js` relying
 largely on ESLint's own `recommended`.
 
-Using JSHint in projects and addons generated by prior versions of ember-cli is still supported, but we recommend that you update to
-ESLint as you upgrade your project and addons to newer ember-cli versions.
+Using JSHint in projects and addons generated by prior versions of Ember CLI is still supported, but we recommend that you update to
+ESLint as you upgrade your project and addons to newer Ember CLI versions.
 
 #### Reduced Dependencies
 
 In order to avoid inconsistencies and issues due to supporting many `npm` client versions, Ember CLI has had `npm` as a dependency
 for quite some time. This is used for both `ember new foo` (to initially install dependencies for a newly generated application) and
 to install packages via `ember install ember-cli-template-lint` (to install the addon specified). Having `npm` as a dependency
-introduces roughly 19MB to a freshly generated ember-cli application's `node_modules` size. As the `npm` client has become more stable (3.x series and
+introduces roughly 19MB to a freshly generated application's `node_modules` size. As the `npm` client has become more stable (3.x series and
 newer) this has seemed more and more wasteful.
 
-Starting with Ember CLI 2.12, `npm` is no longer a dependency of ember-cli. If a suitable version of `npm` is present on the system,
-it will be used. If either `npm` is not found or a version older than `3.0.0` is found, ember-cli will emit an error when you run commands that would utilize
+Starting with Ember CLI 2.12, `npm` is no longer a dependency of. If a suitable version of `npm` is present on the system,
+it will be used. If `npm` is not found, or a version older than `3.0.0` is found, Ember CLI will emit an error when you run commands that would utilize
 `npm` (e.g. `ember install`, `ember new`, `ember addon`, `ember init`).
 
 Similarly, Ember CLI had a dependency on `bower` in order to support the `bower install` phase while generating new projects and installing
@@ -232,7 +232,7 @@ Having `bower`
 as a dependency added roughly 21MB to a new application's total `node_modules` size. In Ember CLI 2.12, bower is only added as a dependency if a command
 requires `bower` and it is not already installed globally.
 
-Combined, these changes result in approximately 40MB of reduction in `node_modules` size on a newly generated application.
+Combined, these changes result in a `node_modules` size reduction of approximately 40MB for newly generated applications.
 
 #### Other Notable Changes
 
@@ -287,21 +287,21 @@ for more insight.
 
 #### Babel 6
 
-Babel 6 was introduced on stage during EmberCamp London way back on 2015-10-29, however ember-cli and the entire ember-cli ecosystem
+Babel 6 was introduced on stage during EmberCamp London, way back on 2015-10-29. However, Ember CLI and its ecosystem
 has continued to use the aging and nearly unsupported Babel 5. Babel 6 was a massive shift for Babel and the migration posed quite a
 challenge for ember-cli.
 
-After much work Babel 6 support has been added to ember-cli internally and for newly generated projects (both applications and addons).
-The latest beta of ember-cli-babel@6 takes advantage of the new `project.targets` API along with [babel-preset-env](https://github.com/babel/babel-preset-env)
+After much work, Babel 6 support has been added to Ember CLI internally and for newly generated projects (both applications and addons).
+The latest beta of `ember-cli-babel@6` takes advantage of the new `project.targets` API along with [`babel-preset-env`](https://github.com/babel/babel-preset-env)
 to allow applications to have significantly better control of exactly what is transpiled. `babel-preset-env` utilizes the [caniuse](http://caniuse.com/) and
 [@kangax]'s [ES6 compatibility database](https://kangax.github.io/compat-table/es6/) to know which features are available natively and which
-require transpilation. For example, with the proper targets configuration ember-cli-babel will no longer transpile `const` / `let`, 
+require transpilation. For example, with the proper targets configuration `ember-cli-babel` will no longer transpile `const` / `let`, 
 `() => { }` functions, `class`, etc.
 
-The work done in ember-cli-babel allows both ember-cli-babel@5 and ember-cli-babel@6 to coexist peacefully, so it is safe for addon authors
-to begin updating their internal ember-cli-babel dependency so that applications can take advantage of more of these babel@6 features.
+The work done in `ember-cli-babel` allows both `ember-cli-babel@5` and `ember-cli-babel@6` to coexist peacefully, so it is safe for addon authors
+to begin updating their internal `ember-cli-babel` dependency so that applications can take advantage of more of these `babel@6` features.
 
-Please test your applications and addons with ember-cli-babel@6 and report any issues you encounter. Due to the large number of changes required 
+Please test your applications and addons with `ember-cli-babel@6` and report any issues you encounter. Due to the large number of changes required 
 internally, we would like a larger than normal beta testing base to ensure things are as stable as possible before 2.13.0 is released.
 
 #### Other Notable Changes