Fix broken markdown

Summary: Newer versions of Docusaurus are a lot less lenient when parsing. This blocks future updates.

Reviewed By: lawrencelomax

Differential Revision: D52481989

fbshipit-source-id: 21e5fe7d6313616501f76659b3abf4cb7ba99708

docs/extending/debugging.mdx

@@ -14,7 +14,7 @@ In addition, to assist you with the JavaScript, the JS console displays uncaught
 
 As an alternative to using built-in Developer Tools, you can also attach to the running Flipper instance from Google Chrome Developer Tools. Sometimes this is useful because the version of Dev Tools in Google Chrome is more recent than the embedded one, and it is possible to easily install additional extensions if required.
 
-To attach the running Flipper instance, open a new tab in Google Chrome, navigate to <http://localhost:9222> and choose 'Flipper' in the opened list, as shown in the following screenshot
+To attach the running Flipper instance, open a new tab in Google Chrome, navigate to http://localhost:9222 and choose 'Flipper' in the opened list, as shown in the following screenshot
 
 <img alt="Attach From Google Chrome" src={useBaseUrl("img/debugging-from-google-chrome.png")} />
 

docs/extending/flipper-plugin.mdx

@@ -1436,7 +1436,7 @@ The following members are only available for Client plugins:
 
 * `sendEvent(event, params)`: Emulates an event being sent by the client plugin. Will trigger the corresponding `onMessage` handler in the plugin.
 * `sendEvents({ method: string, params: object}[])`: Like `sendEvent`, but sends multiple events at once.
-* `onSend`: A `jest.fn()` that can be used to assert that `client.send()` was called by the plugin under test. For example, `expect(runner.onSend).toBeCalledWith('currentLogs`, { since: 0})`.
+* `onSend`: A `jest.fn()` that can be used to assert that `client.send()` was called by the plugin under test. For example, `expect(runner.onSend).toBeCalledWith('currentLogs', { since: 0})`.
 * `connect()`: Triggers the `onConnect()` event. (For non-background plugins `activate()` could as well be used for this).
 * `disconnect()`: Triggers the `onDisconnect()` event. (For non-background plugins `deactivate()` could as well be used for this).
 

docs/extending/testing.mdx

@@ -198,7 +198,7 @@ Focus on the plugins, or Flipper code you want but with the `--with-tests` param
 arc focus ... --with-tests`
 ```
 
-Then, click the '<->' icon in xcode and you run from there.
+Then, click the `<->` icon in Xcode and you run from there.
 
 </FbInternalOnly>
 

docs/getting-started/troubleshooting/general.mdx

@@ -23,7 +23,7 @@ Flipper is a 'work in progress' and issues may occur. This page mostly contains
 
 * Check your device isn't on the list of [known incompatibilities](#known-incompatibilities).
 * Make sure your version of Flipper is up to date.
-* Make sure the mobile SDK you are using is relatively recent (<1 month old).
+* Make sure the mobile SDK you are using is relatively recent (&lt;1 month old).
 * Open Chrome dev tools within Flipper. To do so, from the View menu select Toggle Developer Tools or press CMD+Option+I and check if there are any errors on the console.
 * Delete `~/.flipper`.
 * **Uninstall** and reinstall the mobile app.

docs/getting-started/troubleshooting/install-android-sdk.mdx

@@ -1,5 +1,5 @@
 import useBaseUrl from '@docusaurus/useBaseUrl';
-export const imgStyle = {display: 'block', margin: 'auto', maxWidth: 600}
+export const imgStyle = {display: 'block', margin: 'auto', maxWidth: 600};
 
 # Install Android SDK
 

docs/getting-started/troubleshooting/ios.mdx

@@ -29,4 +29,4 @@ Ensure that your simulator is on the same version as selected in `xcode-select`.
 
 ## iOS app connection error "Connection failed. Failed to find device..."
 
-If during connecting iOS app to Flipper you see error message "Connection failed. Failed to find device <device_id> while trying to connect app" - try executing `idb kill` on a terminal and restarting Flipper as workaround to reset idb state.
+If during connecting iOS app to Flipper you see error message "Connection failed. Failed to find device [device_id] while trying to connect app" - try executing `idb kill` on a terminal and restarting Flipper as workaround to reset idb state.

docs/getting-started/troubleshooting/react-native.mdx

@@ -30,7 +30,7 @@ When using Flipper with React Native, two devices should show up:
 ### I see my device / emulator, but I can't see the app
 
 1. Make sure you are running a debug build. Flipper *only* supports debug builds.
-2. If you are upgraded from RN < 0.62.2, make sure you've updated all the dependencies and build related files according to the upgrade helper. For example: <https://react-native-community.github.io/upgrade-helper/?from=0.61.4&to=0.62.2>
+2. If you are upgraded from RN < 0.62.2, make sure you've updated all the dependencies and build related files according to the upgrade helper. For example: https://react-native-community.github.io/upgrade-helper/?from=0.61.4&to=0.62.2
 3. If you upgraded, make sure you made a clean build: `cd android && ./gradlew clean`, `cd iOS && pod install --repo-update`.
 4. For iOS, make sure it works on a simulator first.
 5. (Unconfirmed) check the deployment info target in the XCode project settings. Target should be `iOS 9.0`.