Fixed some links and improved a recommendation

Author: bvaughn

content/docs/refs-and-the-dom.md

@@ -33,7 +33,7 @@ Your first inclination may be to use refs to "make things happen" in your app. I
 
 > Note
 >
-> The examples below have been updated to use the React.createRef() API introduced in React 16.3. If you are using an earlier release of React, we recommend using [#callback-refs](callback refs) instead.
+> The examples below have been updated to use the React.createRef() API introduced in React 16.3. If you are using an earlier release of React, we recommend using [callback refs](#callback-refs) instead.
 
 ### Creating Refs
 
@@ -345,7 +345,7 @@ If you worked with React before, you might be familiar with an older API where t
 
 > Note
 >
-> If you're currently using `this.refs.textInput` to access refs, we recommend the callback pattern instead.
+> If you're currently using `this.refs.textInput` to access refs, we recommend using either the [callback pattern](#callback-refs) or the [`createRef` API](#creating-refs) instead.
 
 ### Caveats with callback refs
 

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 recommendation 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](/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`