Fix syntax in markdown files

Author: satya164

.gitignore

@@ -8,3 +8,11 @@ translated_docs/
 
 i18n/*
 !i18n/en.json
+
+# Yarn
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/sdks
+!.yarn/versions

blog/2018-04-06-react-navigation-2.0-rc.md

@@ -15,7 +15,7 @@ Exactly two months after the release of React Navigation 1.0, we are close to an
 yarn add react-navigation@^2.0.0-rc.1
 ```
 
-The documentation for 2.0 is available at <https://reactnavigation.org/>
+The documentation for 2.0 is available at [reactnavigation.org](https://reactnavigation.org)
 
 We’re bumping the major version because some of the changes in this release are backwards incompatible. That said, this should be a fairly easy upgrade. We are improving React Navigation incrementally because we don't want to leave developers feeling stranded in an old version. If you use React Navigation in a conventional way and don't have any custom navigators, I can't imagine this update would take you more than an hour.
 
@@ -77,5 +77,5 @@ This change was made to improve the ease of learning and understanding the libra
 ## New feature highlights
 
 - State persistence - automatically save state and reload it when the app restarts. See [state persistence docs](docs/state-persistence)
-- Transitions between screens in stack with headers and without headers now animates as expected on iOS. <https://github.com/react-navigation/react-navigation/pull/3821>. Thanks [skevy](https://github.com/skevy)!
+- Transitions between screens in stack with headers and without headers now animates as expected on iOS. [#3821](https://github.com/react-navigation/react-navigation/pull/3821). Thanks [skevy](https://github.com/skevy)!
 - As mentioned above, `createMaterialBottomNavigator` is a new navigator type that provides the material design bottom tab bar pattern.

blog/2018-05-07-react-navigation-2.0.md

@@ -7,7 +7,7 @@ author_image_url: https://avatars0.githubusercontent.com/u/90494?s=200&v=4
 tags: [release, announcement]
 ---
 
-The documentation is now live at <https://reactnavigation.org>, and v1 lives [here](/docs/1.x/getting-started).
+The documentation is now live at [reactnavigation.org](https://reactnavigation.org), and v1 lives [here](/docs/1.x/getting-started).
 
 <!--truncate-->
 

blog/2018-11-01-react-navigation-3.0-rc.md

@@ -23,7 +23,7 @@ First, install the library using your favorite package manager: `yarn add react-
 
 Next, install react-native-gesture-handler. If you’re using Expo you don’t need to do anything here, it’s included in the SDK. Otherwise: `yarn add react-native-gesture-handler && react-native link`
 
-Optionally, you can install react-native-screens. If you’re using Expo you don’t need to do anything here, it’s included in SDK 30 and higher. Otherwise, follow the instructions in the README on <https://github.com/kmagiera/react-native-screens>.
+Optionally, you can install react-native-screens. If you’re using Expo you don’t need to do anything here, it’s included in SDK 30 and higher. Otherwise, follow the instructions in the README on [`react-native-screens`](https://github.com/software-mansion/react-native-screens).
 
 > **Warning**: if you have manually installed any navigators in your project, for example react-navigation-material-bottom-tabs, you will need to update those to a version that is compatible with 3.0.0. In the case of react-navigation-material-bottom-tabs, 1.0.0-alpha.2 is compatible.
 
@@ -133,15 +133,15 @@ const Store = createStackNavigator({
 - Basic support for hooks in `react-navigation-hooks`
 - `headerBackgroundTransitionPreset: 'toggle' | 'fade' | 'translate'` lets you choose how to transition your custom `headerBackground` components between screens.
 - Add options to opt in/out of the stack card overlay and shadow that are visible during transitions: `cardShadowEnabled` defaults to `true` and  `cardOverlayEnabled` defaults to `false`.
-- Export `StackGestureContext` and `DrawerGestureContext` from react-navigation-stack and react-navigation-drawer, so you can use the ref from the corresponding gestures with other gesture handlers (eg: <https://github.com/react-navigation/react-navigation-drawer/blob/bf4bdba7f6a4fbc12192f5d5ba2285f6280431b7/example/src/GestureInteraction.js>).
+- Export `StackGestureContext` and `DrawerGestureContext` from react-navigation-stack and react-navigation-drawer, so you can use the ref from the corresponding gestures with other gesture handlers (eg: [GestureInteraction.js](https://github.com/react-navigation/react-navigation-drawer/blob/bf4bdba7f6a4fbc12192f5d5ba2285f6280431b7/example/src/GestureInteraction.js)).
 
 ## Assorted fixes & improvements
 
 - Stack transition performance improved greatly by removing the shadow from the entire card and rendering it only on the slice where it is needed. The card opacity is also no longer directly animated but instead an overlay is put on top to create a similar effect but with better performance.
-- Fix long-standing issues with stack that led to quietly re-mounting screens when navigating quickly in certain patterns: <https://github.com/react-navigation/react-navigation/issues/4155>
+- Fix long-standing issues with stack that led to quietly re-mounting screens when navigating quickly in certain patterns: [react-navigation/issues/415](https://github.com/react-navigation/react-navigation/issues/4155)
 - Support inverted gesture in modals.
 - Stack card gesture uses react-native-gesture-handler and native driver so the gesture runs on the UI thread (except when the gesture ends, then it calls back to JS).
-- Fix a variety of issues with drawer navigator, including issues around nesting (<https://github.com/react-navigation/react-navigation/issues/4154>) and bugs with firing open / close (eg: <https://github.com/react-navigation/react-navigation/issues/5146>).
+- Fix a variety of issues with drawer navigator, including issues around nesting ([react-navigation/issues/4154](https://github.com/react-navigation/react-navigation/issues/4154)) and bugs with firing open / close (eg: [react-navigation/issues/5146](https://github.com/react-navigation/react-navigation/issues/5146)).
 
 ## Ecosystem and web support
 
@@ -215,4 +215,4 @@ See a simple web app with Create React App [here](https://github.com/react-navig
 
 ----------
 
-Thanks for reading, please post any issues you encounter to <https://github.com/react-navigation/react-navigation/issues>!
+Thanks for reading, please post any issues you encounter to [react-navigation/issues](https://github.com/react-navigation/react-navigation/issues)!

blog/2018-11-17-react-navigation-3.0.md

@@ -7,7 +7,7 @@ author_image_url: https://avatars0.githubusercontent.com/u/90494?s=200&v=4
 tags: [release, announcement]
 ---
 
-The documentation is now live at <https://reactnavigation.org>, and v2 lives [here](/docs/2.x/getting-started).
+The documentation is now live at [reactnavigation.org](https://reactnavigation.org), and v2 lives [here](/docs/2.x/getting-started).
 
 This is the first release where React Navigation depends on a native module outside of React Native core: it now depends on react-native-gesture-handler. This library provides an excellent set of primitives for leveraging the operating systems’ native gesture APIs and has enabled us to fix a variety of issues with stack and drawer navigators. React Navigation also depends on react-native-screens, but you don’t need to install the native module if you prefer not to use it (we have a blog post coming soon that will explain what react-native-screens is and why you may want to use it, or you can watch [this talk](https://www.youtube.com/watch?v=Z0Jl1KCWiag) by the author of the library).
 
@@ -23,7 +23,7 @@ First, install the library using your favorite package manager: `yarn add react-
 
 Next, install react-native-gesture-handler. If you’re using Expo you don’t need to do anything here, it’s included in the SDK. Otherwise, follow [these installation instructions](https://kmagiera.github.io/react-native-gesture-handler/docs/getting-started.html#installation).
 
-Optionally, you can install react-native-screens. If you’re using Expo you don’t need to do anything here, it’s included in SDK 30 and higher. Otherwise, follow the instructions in the README on <https://github.com/kmagiera/react-native-screens>.
+Optionally, you can install react-native-screens. If you’re using Expo you don’t need to do anything here, it’s included in SDK 30 and higher. Otherwise, follow the instructions in the README on [`react-native-screens`](https://github.com/software-mansion/react-native-screens).
 
 > **Warning**: if you have manually installed any navigators in your project, for example react-navigation-material-bottom-tabs, you will need to update those to a version that is compatible with 3.0.0. In the case of react-navigation-material-bottom-tabs, 1.0.0 is compatible.
 
@@ -150,16 +150,16 @@ const Store = createStackNavigator({
 - Basic support for hooks in `react-navigation-hooks` (although this isn't too useful yet without a stable react-native build that supports hooks, you can play with it on the web!).
 - `headerBackgroundTransitionPreset: 'toggle' | 'fade' | 'translate'` lets you choose how to transition your custom `headerBackground` components between screens.
 - Add options to opt in/out of the stack card overlay and shadow that are visible during transitions: `cardShadowEnabled` defaults to `true` and `cardOverlayEnabled` defaults to `false`.
-- Export `StackGestureContext` and `DrawerGestureContext` from react-navigation-stack and react-navigation-drawer, so you can use the ref from the corresponding gestures with other gesture handlers (eg: <https://github.com/react-navigation/react-navigation-drawer/blob/bf4bdba7f6a4fbc12192f5d5ba2285f6280431b7/example/src/GestureInteraction.js>).
+- Export `StackGestureContext` and `DrawerGestureContext` from react-navigation-stack and react-navigation-drawer, so you can use the ref from the corresponding gestures with other gesture handlers (eg: [GestureInteraction.js](https://github.com/react-navigation/react-navigation-drawer/blob/bf4bdba7f6a4fbc12192f5d5ba2285f6280431b7/example/src/GestureInteraction.js)).
 - Tab navigators support `tabBarOnLongPress` configuration option, which defaults to the same as the tab press event.
 
 ## Assorted fixes & improvements
 
 - Stack transition performance improved greatly by removing the shadow from the entire card and rendering it only on the slice where it is needed. The card opacity is also no longer directly animated but instead an overlay is put on top to create a similar effect but with better performance.
-- Fix long-standing issues with stack that led to quietly re-mounting screens when navigating quickly in certain patterns: <https://github.com/react-navigation/react-navigation/issues/4155>
+- Fix long-standing issues with stack that led to quietly re-mounting screens when navigating quickly in certain patterns: [react-navigation/issues/4155](https://github.com/react-navigation/react-navigation/issues/4155)
 - Support inverted gesture in modals.
 - Stack card gesture uses react-native-gesture-handler and native driver so the gesture runs on the UI thread (except when the gesture ends, then it calls back to JS).
-- Fix a variety of issues with drawer navigator, including issues around nesting (<https://github.com/react-navigation/react-navigation/issues/4154>) and bugs with firing open / close (eg: <https://github.com/react-navigation/react-navigation/issues/5146>).
+- Fix a variety of issues with drawer navigator, including issues around nesting ([react-navigation/issues/4154](https://github.com/react-navigation/react-navigation/issues/4154)) and bugs with firing open / close (eg: [react-navigation/react-navigation/issues/5146](https://github.com/react-navigation/react-navigation/issues/5146)).
 - Fix accessibility voiceover for tabs and stack back button.
 
 ## Ecosystem and web support
@@ -234,4 +234,4 @@ See a simple web app with Create React App [here](https://github.com/react-navig
 
 ---
 
-Thanks for reading, please post any issues you encounter to <https://github.com/react-navigation/react-navigation/issues>!
+Thanks for reading, please post any issues you encounter to [react-navigation/issues](https://github.com/react-navigation/react-navigation/issues)!

blog/2019-09-16-react-navigation-4.0.md

@@ -7,7 +7,7 @@ author_image_url: https://avatars2.githubusercontent.com/u/1174278?s=200&v=4
 tags: [release, announcement]
 ---
 
-The documentation is now live at <https://reactnavigation.org>, and v3 lives [here](/docs/3.x/getting-started).
+The documentation is now live at [reactnavigation.org](https://reactnavigation.org), and v3 lives [here](/docs/3.x/getting-started).
 
 In this release, we have removed the navigators from the react-navigation package. The navigators have lived in separate packages for quite a while and you could already use those packages manually, but we still bundled them in the react-navigation package. This made it difficult for us to release significant updates to navigators, because we had to then do a major version release of react-navigation too. By separating the navigator packages there is more freedom to update and improve navigators without any impact on folks that don't use them.
 
@@ -29,4 +29,4 @@ If you're using TypeScript, navigator specific types were also removed from the
 
 ---
 
-Thanks for reading, please post any issues you encounter to <https://github.com/react-navigation/react-navigation/issues>!
+Thanks for reading, please post any issues you encounter to [react-navigation/issues](https://github.com/react-navigation/react-navigation/issues)!

versioned_docs/version-1.x/stack-navigator.md

@@ -62,8 +62,7 @@ Visual options:
   * `fade-in-place` - Header components cross-fade without moving, similar to the Twitter, Instagram, and Facebook app for iOS. This is the default value.
   * `uikit` - An approximation of the default behavior for iOS.
 * `cardStyle` - Use this prop to override or extend the default style for an individual card in stack.
-* `transitionConfig` - Function to return an object that is merged with the default screen transitions (take a look at TransitionConfig in [type definitions](
-<https://github.com/react-navigation/react-navigation/blob/1.x/flow/react-navigation.js>)). Provided function will be passed the following arguments:
+* `transitionConfig` - Function to return an object that is merged with the default screen transitions (take a look at TransitionConfig in [type definitions](https://github.com/react-navigation/react-navigation/blob/1.x/flow/react-navigation.js)). Provided function will be passed the following arguments:
   * `transitionProps` - Transition props for the new screen.
   * `prevTransitionProps` - Transitions props for the old screen.
   * `isModal` - Boolean specifying if screen is modal.

versioned_docs/version-2.x/custom-navigators.md

@@ -96,7 +96,7 @@ To help developers implement custom navigators, the following utilities are prov
 
 ### `createNavigator`
 
-> Note: The `createNavigator` API has changed in version 2. The old doc for v1 can be accessed here: <https://v1.reactnavigation.org/docs/custom-navigators.html>
+> Note: The `createNavigator` API has changed in version 2. The old doc for v1 can be accessed here: [v1.reactnavigation.org/docs/custom-navigators.html](https://v1.reactnavigation.org/docs/custom-navigators.html)
 
 This utility combines a [router](routers.md) and a [navigation view](navigation-views.md) together in a standard way:
 

versioned_docs/version-2.x/stack-navigator.md

@@ -68,8 +68,7 @@ Visual options:
   * `left` - Anchor the title to the left, near the back button or other left component. This is the default on Android. When used on iOS, the header back title is hidden. Content from the left component will overflow underneath the title, if you need to adjust this you can use `headerLeftContainerStyle` and `headerTitleContainerStyle`. Additionally, this alignment is incompatible with `headerTransitionPreset: 'uikit'`.
   * `center` - Center the title, this is the default on iOS.
 * `cardStyle` - Use this prop to override or extend the default style for an individual card in stack.
-* `transitionConfig` - Function to return an object that is merged with the default screen transitions (take a look at TransitionConfig in [type definitions](
-<https://github.com/react-navigation/react-navigation/blob/2.x/flow/react-navigation.js>)). Provided function will be passed the following arguments:
+* `transitionConfig` - Function to return an object that is merged with the default screen transitions (take a look at TransitionConfig in [type definitions](https://github.com/react-navigation/react-navigation/blob/2.x/flow/react-navigation.js)). Provided function will be passed the following arguments:
   * `transitionProps` - Transition props for the new screen.
   * `prevTransitionProps` - Transitions props for the old screen.
   * `isModal` - Boolean specifying if screen is modal.

versioned_docs/version-3.x/custom-navigators.md

@@ -96,7 +96,7 @@ To help developers implement custom navigators, the following utilities are prov
 
 ### `createNavigator`
 
-> Note: The `createNavigator` API has changed in version 2. The old doc for v1 can be accessed here: <https://v1.reactnavigation.org/docs/custom-navigators.html>
+> Note: The `createNavigator` API has changed in version 2. The old doc for v1 can be accessed here: [v1.reactnavigation.org/docs/custom-navigators.html](https://v1.reactnavigation.org/docs/custom-navigators.html)
 
 This utility combines a [router](routers.md) and a [navigation view](navigation-views.md) together in a standard way:
 

versioned_docs/version-3.x/redux-integration.md

@@ -4,7 +4,7 @@ title: Redux integration
 sidebar_label: Redux integration
 ---
 
-It is extremely easy to use Redux in an app with React Navigation. It's basically no different than without React Navigation. The following example shows how to do it end to end: <https://snack.expo.io/@react-navigation/redux-example>. The most important piece from it is the following:
+It is extremely easy to use Redux in an app with React Navigation. It's basically no different than without React Navigation. The following example shows how to do it end to end: [snack.expo.io/@react-navigation/redux-example](https://snack.expo.io/@react-navigation/redux-example). The most important piece from it is the following:
 
 ```js
 let RootStack = createStackNavigator({

versioned_docs/version-3.x/stack-navigator.md

@@ -72,8 +72,7 @@ Visual options:
 * `cardStyle` - Use this prop to override or extend the default style for an individual card in stack.
 * `cardShadowEnabled` - Use this prop to have visible shadows during transitions. Defaults to `true`
 * `cardOverlayEnabled` - Use this prop to have visible stack card overlays during transitions. Defaults to `false`.
-* `transitionConfig` - Function to return an object that is merged with the default screen transitions (take a look at TransitionConfig in [type definitions](
-<https://github.com/react-navigation/react-navigation/blob/3.x/flow/react-navigation.js>)). Provided function will be passed the following arguments:
+* `transitionConfig` - Function to return an object that is merged with the default screen transitions (take a look at TransitionConfig in [type definitions](https://github.com/react-navigation/react-navigation/blob/3.x/flow/react-navigation.js)). Provided function will be passed the following arguments:
   * `transitionProps` - Transition props for the new screen.
   * `prevTransitionProps` - Transitions props for the old screen.
   * `isModal` - Boolean specifying if screen is modal.

versioned_docs/version-4.x/custom-navigators.md

@@ -96,7 +96,7 @@ To help developers implement custom navigators, the following utilities are prov
 
 ### `createNavigator`
 
-> Note: The `createNavigator` API has changed in version 2. The old doc for v1 can be accessed here: <https://v1.reactnavigation.org/docs/custom-navigators.html>
+> Note: The `createNavigator` API has changed in version 2. The old doc for v1 can be accessed here: [v1.reactnavigation.org/docs/custom-navigators.html](https://v1.reactnavigation.org/docs/custom-navigators.html)
 
 This utility combines a [router](routers.md) and a [navigation view](navigation-views.md) together in a standard way: