fixes md syntax in GraphQL Subscriptions (#3552)

Summary:
Adjusts markdown syntax around the automatically updating local store details.

Pull Request resolved: #3552

Reviewed By: alunyov

Differential Revision: D30675270

Pulled By: kassens

fbshipit-source-id: 3273696dc3714e75ae8f33b567b88fb4a32aa080

website/docs/guided-tour/updating-data/graphql-subscriptions.md

@@ -117,7 +117,7 @@ Let's distill what's happening here:
 * Note that the `input` for the subscription can be Flow typed with the autogenerated type available from the *`FeedbackLikeSubscription.graphql`* module. In general, the Relay will generate Flow types for subscriptions at build time, with the following naming format: `*<subscription_name>*.graphql.js`.
 * `requestSubscription` also takes an `onCompleted` and `onError` callbacks, which will respectively be called when the subscription is successfully established, or when an error occurs.
 * `requestSubscription` also takes an `onNext` callback, which will be called whenever a subscription payload is received.
-* When the subscription payload is received, *i**f the objects in the subscription payload have IDs, the records in the local store will *automatically* be updated with the new field values from the payload**.* In this case, it would automatically find the existing `Feedback` object matching the given ID in the store, and update the values for the `like_count` field.
+* When the subscription payload is received, **if the objects in the subscription payload have IDs, the records in the local store will _automatically_ be updated with the new field values from the payload.** In this case, it would automatically find the existing `Feedback` object matching the given ID in the store, and update the values for the `like_count` field.
 * Note that any local data updates caused by the subscription will automatically cause components subscribed to the data to be notified of the change and re-render.
 
 

website/versioned_docs/version-v11.0.0/guided-tour/updating-data/graphql-subscriptions.md

@@ -114,7 +114,7 @@ Let's distill what's happening here:
 * Note that the `input` for the subscription can be Flow typed with the autogenerated type available from the *`FeedbackLikeSubscription.graphql`* module. In general, the Relay will generate Flow types for subscriptions at build time, with the following naming format: `*<subscription_name>*.graphql.js`.
 * `requestSubscription` also takes an `onCompleted` and `onError` callbacks, which will respectively be called when the subscription is successfully established, or when an error occurs.
 * `requestSubscription` also takes an `onNext` callback, which will be called whenever a subscription payload is received.
-* When the subscription payload is received, *i**f the objects in the subscription payload have IDs, the records in the local store will *automatically* be updated with the new field values from the payload**.* In this case, it would automatically find the existing `Feedback` object matching the given ID in the store, and update the values for the `like_count` field.
+* When the subscription payload is received, **if the objects in the subscription payload have IDs, the records in the local store will _automatically_ be updated with the new field values from the payload.** In this case, it would automatically find the existing `Feedback` object matching the given ID in the store, and update the values for the `like_count` field.
 * Note that any local data updates caused by the subscription will automatically cause components subscribed to the data to be notified of the change and re-render.