Typo fixes

content/blog/2018-03-20-react-v-16-3.md

@@ -7,7 +7,7 @@ This release includes a new class component lifecycle (`getDerivedStateFromProps
 
 For the past few months, the React team has been working on support for [asynchronous rendering](/blog/2018/03/01/sneak-peek-beyond-react-16.html). We are excited about the new features it will enable.
 
-We've also learned that some long-term changes will be required to the way we write React components. However, we respect semver and **will not ship breaking changes in a minor version**!
+We've also learned that some long-term changes will be required to the way we write React components. However, we respect [semver](https://semver.org/) and **will not ship breaking changes in a minor version**!
 
 Read on to learn more about the release.
 
@@ -28,7 +28,7 @@ Here is an example illustrating how you might inject a "theme" using the new con
 
 ## `createRef` API
 
-Previously, React provided two ways for managing refs: the legacy string ref API and the callback API. Although the string ref API was the more convenient of the two, it had [several downsides](https://github.com/facebook/react/issues/1373) and so our official recomendation was to use the callback form instead.
+Previously, React provided two ways of managing refs: the legacy string ref API and the callback API. Although the string ref API was the more convenient of the two, it had [several downsides](https://github.com/facebook/react/issues/1373) and so our official recommendation was to use the callback form instead.
 
 Version 16.3 adds a new option for managing refs that offers the convenience of a string ref without any of the downsides:
 `embed:16-3-release-blog-post/create-ref-example.js`

content/docs/strict-mode.md

@@ -34,7 +34,7 @@ Addressing the issues identified by strict mode _now_ will make it easier for yo
 
 ### Warning about legacy string ref API usage
 
-Previously, React provided two ways for managing refs: the legacy string ref API and the callback API. Although the string ref API was the more convenient of the two, it had [several downsides](https://github.com/facebook/react/issues/1373) and so our official recomendation was to [use the callback form instead](https://reactjs.org/docs/refs-and-the-dom.html#legacy-api-string-refs).
+Previously, React provided two ways for managing refs: the legacy string ref API and the callback API. Although the string ref API was the more convenient of the two, it had [several downsides](https://github.com/facebook/react/issues/1373) and so our official recommendation was to [use the callback form instead](https://reactjs.org/docs/refs-and-the-dom.html#legacy-api-string-refs).
 
 React 16.3 added a third option that offers the convenience of a string ref without any of the downsides:
 `embed:16-3-release-blog-post/create-ref-example.js`