Rephrase

docs/_posts/2016-04-04-react-v15.md

@@ -15,7 +15,9 @@ React 15 brings significant improvements to how we interact with the DOM:
 
 * We received some amazing contributions from the community in this release, and we would like to highlight [this pull request](https://github.com/facebook/react/pull/5753) by [Michael Wiencek](https://github.com/mwiencek) in particular. Thanks to Michael’s work, React 15 no longer emits extra `<span>` nodes around the text, making the DOM output much cleaner. This was a longstanding annoyance for React users so it’s exciting to accept this as an outside contribution.
 
-While this isn’t directly related to the release, we understand that in order to receive more community contributions like Michael’s, we need to communicate our goals and priorities more openly, and review pull requests more decisively. As a first step towards this, we started publishing [React core team weekly meeting notes](https://github.com/reactjs/core-notes) again. We also intend to introduce an RFC process inspired by [Ember RFCs](https://github.com/emberjs/rfcs) so external contributors can have more insight and influence in the future development of React. We will keep you updated about this on our blog. We are also trying a new changelog format in this post with links to the corresponding pull requests. Let us know whether you find this useful!
+While this isn’t directly related to the release, we understand that in order to receive more community contributions like Michael’s, we need to communicate our goals and priorities more openly, and review pull requests more decisively. As a first step towards this, we started publishing [React core team weekly meeting notes](https://github.com/reactjs/core-notes) again. We also intend to introduce an RFC process inspired by [Ember RFCs](https://github.com/emberjs/rfcs) so external contributors can have more insight and influence in the future development of React. We will keep you updated about this on our blog.
+
+We are also experimenting with a new changelog format in this post. Every change now links to the corresponding pull request and mentions the author. Let us know whether you find this useful!
 
 ## Upgrade Guide
 
@@ -77,22 +79,22 @@ If you can’t use `npm` yet, we provide pre-built browser builds for your conve
 
 - #### `React.cloneElement()` now resolves `defaultProps`
 
-    We fixed a bug in `React.cloneElement()` that some components may rely on. If some of the `props` received by `cloneElement()` are `undefined`, React 0.14 returns an element with `undefined` values for those props. In React 15, we’re changing it to be consistent with `createElement()`. Now any `undefined` props are resolved to the corresponding component’s `defaultProps`. Only one of our 20,000 React components was negatively affected by this so we feel comfortable releasing this change without keeping the old behavior for another release cycle. ([@truongduy134](https://github.com/facebook/react/pull/5997))
+    We fixed a bug in `React.cloneElement()` that some components may rely on. If some of the `props` received by `cloneElement()` are `undefined`, it used to return an element with `undefined` values for those props. In React 15, we’re changing it to be consistent with `createElement()`. Now any `undefined` props passed to `cloneElement()` are resolved to the corresponding component’s `defaultProps`. Only one of our 20,000 React components was negatively affected by this so we feel comfortable releasing this change without keeping the old behavior for another release cycle. ([@truongduy134](https://github.com/facebook/react/pull/5997))
 
 - #### `ReactPerf.getLastMeasurements()` is opaque
 
-    This change won’t affect applications but may break some third-party tools. We are [revamping `ReactPerf` implementation](https://github.com/facebook/react/pull/6046) and plan to release it during the 15.x cycle. This means the internal performance measurement format will change, and for now, we consider the return value of `ReactPerf.getLastMeasurements()` an opaque data structure that shouldn’t be relied upon. ([@gaearon](https://github.com/facebook/react/pull/6286))
+    This change won’t affect applications but may break some third-party tools. We are [revamping `ReactPerf` implementation](https://github.com/facebook/react/pull/6046) and plan to release it during the 15.x cycle. The internal performance measurement format is subject to change so, for the time being, we consider the return value of `ReactPerf.getLastMeasurements()` an opaque data structure that should not be relied upon. ([@gaearon](https://github.com/facebook/react/pull/6286))
 
 - #### Removed deprecations
 
-    These deprecations were introduced in v0.14 with a warning and the APIs are now removed:
+    These deprecations were introduced nine months ago in v0.14 with a warning and are removed:
 
-    - Deprecated APIs are removed from `React`, specifically `findDOMNode`, `render`, `renderToString`, `renderToStaticMarkup`, and `unmountComponentAtNode`. ([@jimfb](https://github.com/facebook/react/pull/5832))
-    - Deprecated APIs are removed from `React.addons`, specifically `batchedUpdates` and `cloneWithProps`. ([@jimfb](https://github.com/facebook/react/pull/5859), [@zpao](https://github.com/facebook/react/pull/6016))
-    - Deprecated APIs are removed from component instances, specifically `setProps`, `replaceProps`, and `getDOMNode`. ([@jimfb](https://github.com/facebook/react/pull/5570))
-    - Deprecated CommonJS entry point `react/addons` is removed in favor of the separate `react-addons-*` packages. This does not affect the `react-with-addons.js` UMD build. ([@gaearon](https://github.com/facebook/react/pull/6285))
+    - Deprecated APIs are removed from the `React` top-level export: `findDOMNode`, `render`, `renderToString`, `renderToStaticMarkup`, and `unmountComponentAtNode`. As a reminder, they are now available on `ReactDOM` and `ReactDOMServer`. ([@jimfb](https://github.com/facebook/react/pull/5832))
+    - Deprecated addons are removed: `batchedUpdates` and `cloneWithProps`. ([@jimfb](https://github.com/facebook/react/pull/5859), [@zpao](https://github.com/facebook/react/pull/6016))
+    - Deprecated component instance methods are removed: `setProps`, `replaceProps`, and `getDOMNode`. ([@jimfb](https://github.com/facebook/react/pull/5570))
+    - Deprecated CommonJS `react/addons` entry point is removed. As a reminder, you should use separate `react-addons-*` packages instead. This only applies if you use the CommonJS builds. ([@gaearon](https://github.com/facebook/react/pull/6285))
     - Passing `children` to void elements like `<input>` was deprecated, and now throws an error. ([@jonhester](https://github.com/facebook/react/pull/3372))
-    - Accessing React-specific properties on DOM `refs` (e.g. `this.refs.div.props`) was deprecated in React 0.14 and won’t work in React 15. ([@jimfb](https://github.com/facebook/react/pull/5495))
+    - React-specific properties on DOM `refs` (e.g. `this.refs.div.props`) were deprecated, and are removed now. ([@jimfb](https://github.com/facebook/react/pull/5495))
 
 ### New deprecations, introduced with a warning