Minor docs tweak

Summary: Pull Request resolved: #2945

Differential Revision: D18523959

Pulled By: jstejada

fbshipit-source-id: c5e4cd1ac231419768aac980965478056728a7a5

website/versioned_docs/version-experimental/RelayHooks-AGuidedTourOfRelay.md

@@ -1240,7 +1240,7 @@ Specifically, `fetchPolicy` can be any of the following options:
 * **"network-only"**: ***will not*** reuse locally cached data, and will ***always*** send a network request to fetch the query, ignoring any data that might be locally cached in Relay.
 * **"store-only"**: ***will only*** reuse locally cached data, and will ***never*** send a network request to fetch the query. In this case, the responsibility of fetching the query falls to the caller, but this policy could also be used to read and operate on data that is entirely [local](#local-data-updates).
 
-Note that the `refetch` function discussed in the [Fetching More Data and Rendering Different Data](#fetching-more-data-and-rendering-different-data) section  also takes a `fetchPolicy`.
+Note that the `refetch` function discussed in the [Fetching More Data and Rendering Different Data](#fetching-and-rendering-different-data) section  also takes a `fetchPolicy`.
 
 ### Garbage Collection in Relay
 
@@ -1502,7 +1502,7 @@ const environment = new Environment({/*...*/, missingFieldHandlers});
   * When handling a ***'linked'*** field, the handle function should return an ***ID***, referencing another object in the store that should be use in place of the missing field.
 * As Relay attempts to fulfill a query from the local cache, whenever it detects any missing data, it will run any of the provided missing field handlers that match the field type before definitively declaring that the data is missing.
 
-## Fetching More Data and Rendering *Different* Data
+## Fetching Rendering *Different* Data
 
 After an app has been initially rendered, there are various scenarios in which you might want to fetch and render more data, re-render your UI with *different* data, or maybe refresh existing data, usually as a result of an event or user interaction.