Fix markdown lint errors

Author: satya164

.markdownlint.yaml

@@ -5,3 +5,6 @@ MD013: false
 
 # Disable checks for inline HTML
 MD033: false
+
+# Descriptive link text
+MD059: false

versioned_docs/version-5.x/compatibility.md

@@ -56,7 +56,7 @@ The library exports the following APIs:
   - `createCompatNavigatorFactory` - Takes a navigator with the v5 API and returns a `createXNavigator` with the v4 API.
   - `createCompatNavigationProp` - Takes the v5 `navigation` object along with a `route` object and returns a v4 `navigation` object.
 
-### What does it handle?
+## What does it handle?
 
 The compatibility layer handles various API differences between React Navigation 4 and 5:
 
@@ -65,7 +65,7 @@ The compatibility layer handles various API differences between React Navigation
 - Add support for `screenProps` which is removed in v5.
 - Export action creators such as `NavigationActions`, `StackActions`, `SwitchActions` with same signature as v4.
 
-### What doesn't it handle?
+## What doesn't it handle?
 
 Due to the dynamic API of React Navigation 5, some functionality possible with the static API of v4 are not possible anymore, and hence the compatibility layer doesn't handle them:
 
@@ -78,7 +78,7 @@ Due to the dynamic API of React Navigation 5, some functionality possible with t
 
 While we have tried our best to make the compatibility layer handle most of the differences, there might be something missing. So make sure to test the code that you've migrated.
 
-### Why should we use it?
+## Why should we use it?
 
 Using the compatibility layer allows us to migrate our code to the new version incrementally. Unfortunately we do have to change some code to get the compatibility layer working (see "What doesn't it handle") properly, but it still allows majority of our code to remain unchanged. Some of the advantages of using the compatibility layer include:
 

versioned_docs/version-5.x/custom-android-back-button-handling.md

@@ -42,6 +42,6 @@ The presented approach will work well for screens that are shown in a `StackNavi
 
 If instead of overriding system back button, you'd like to prevent going back from the screen, see docs for [preventing going back](preventing-going-back.md).
 
-### Why not use component lifecycle methods
+## Why not use component lifecycle methods
 
 At first, you may be inclined to use `componentDidMount` to subscribe for the back press event and `componentWillUnmount` to unsubscribe, or use `useEffect` to add the listener. This approach will not work - learn more about this in [navigation lifecycle](navigation-lifecycle.md).

versioned_docs/version-5.x/drawer-actions.md

@@ -8,7 +8,7 @@ sidebar_label: DrawerActions
 
 The following actions are supported:
 
-### openDrawer
+## openDrawer
 
 The `openDrawer` action can be used to open the drawer pane.
 
@@ -20,7 +20,7 @@ import { DrawerActions } from '@react-navigation/native';
 navigation.dispatch(DrawerActions.openDrawer());
 ```
 
-### closeDrawer
+## closeDrawer
 
 The `closeDrawer` action can be used to close the drawer pane.
 
@@ -32,7 +32,7 @@ import { DrawerActions } from '@react-navigation/native';
 navigation.dispatch(DrawerActions.closeDrawer());
 ```
 
-### toggleDrawer
+## toggleDrawer
 
 The `toggleDrawer` action can be used to open the drawer pane if closed, or close if open.
 
@@ -44,7 +44,7 @@ import { DrawerActions } from '@react-navigation/native';
 navigation.dispatch(DrawerActions.toggleDrawer());
 ```
 
-### jumpTo
+## jumpTo
 
 The `jumpTo` action can be used to jump to an existing route in the drawer navigator.
 

versioned_docs/version-5.x/navigation-events.md

@@ -23,7 +23,7 @@ Each callback registered as an event listener receive an event object as its arg
 
 There are 2 ways to listen to events:
 
-### `navigation.addListener`
+## `navigation.addListener`
 
 Inside a screen, you can add listeners on the `navigation` prop with the `addListener` method. The `addListener` method takes 2 arguments: type of the event, and a callback to be called on the event. It returns a function that can be called to unsubscribe from the event.
 
@@ -78,7 +78,7 @@ class Profile extends React.Component {
 
 One thing to keep in mind is that you can only listen to events from the immediate navigator with `addListener`. For example, if you try to add a listener in a screen that's inside a stack that's nested in a tab, it won't get the `tabPress` event. If you need to listen to an event from a parent navigator, you may use `navigation.getParent()` to get a reference to parent navigator's navigation prop and add a listener.
 
-### `listeners` prop on `Screen`
+## `listeners` prop on `Screen`
 
 Sometimes you might want to add a listener from the component where you defined the navigator rather than inside the screen. You can use the `listeners` prop on the `Screen` component to add listeners. The `listeners` prop takes an object with the event names as keys and the listener callbacks as values.
 

versioned_docs/version-5.x/navigation-prop.md

@@ -24,7 +24,7 @@ It's important to highlight the `navigation` prop is _not_ passed in to _all_ co
 
 > `setParams`/`setOptions` etc. should only be called in `useEffect`/`useLayoutEffect`/`componentDidMount`/`componentDidUpdate` etc. Not during render or in constructor.
 
-### Navigator-dependent functions
+## Navigator-dependent functions
 
 There are several additional functions present on `navigation` prop based on the kind of the current navigator.
 

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

@@ -22,7 +22,7 @@ export default function App() {
 
 Notice that we wrap our components in a `Provider` like we'd normally do with `react-redux`. Ta da! Now feel free to use `connect` throughout your app.
 
-### Use a component that is `connect`ed in `options`
+## Use a component that is `connect`ed in `options`
 
 Create a component, `connect` it to the store, then use that component in the `title`.
 
@@ -44,7 +44,7 @@ const CounterContainer = connect((state) => ({ value: state.count }))(Counter);
 />
 ```
 
-### Pass the state you care about as a param to the screen
+## Pass the state you care about as a param to the screen
 
 If the value isn't expected to change, you can just pass it from a connected component to the other screen as a param.
 

versioned_docs/version-5.x/screen-options.md

@@ -10,7 +10,7 @@ In the [configuring the header bar](headers.md) section of the fundamentals docu
 
 There are 3 ways of specifying options for screens:
 
-### `options` prop on `Screen`
+## `options` prop on `Screen`
 
 You can pass a prop named `options` to the `Screen` component to configure a screen, where you can specify an object with different options for that screen:
 
@@ -46,7 +46,7 @@ You can also pass a function to `options`. The function will receive the [`navig
 />
 ```
 
-### `screenOptions` prop on the navigator
+## `screenOptions` prop on the navigator
 
 You can pass a prop named `screenOptions` to the navigator component, where you can specify an object with different options. The options specified in `screenOptions` apply to all of the screens in the navigator. So this is a good place to add options that will apply to all screens within the navigator.
 
@@ -87,7 +87,7 @@ Similar to `options`, you can also pass a function to `screenOptions`. The funct
 </Tab.Navigator>
 ```
 
-### `navigation.setOptions` method
+## `navigation.setOptions` method
 
 The `navigation` prop has a `setOptions` method that lets you update the options for a screen from within a component. See [navigation prop's docs](navigation-prop.md#setoptions) more details.
 

versioned_docs/version-5.x/stack-actions.md

@@ -8,7 +8,7 @@ sidebar_label: StackActions
 
 The following actions are supported:
 
-### replace
+## replace
 
 The `replace` action allows to replace a route in the [navigation state](navigation-state.md). It takes the following arguments:
 
@@ -45,7 +45,7 @@ navigation.dispatch({
 
 If the `source` property is explicitly set to `undefined`, it'll replace the focused route.
 
-### push
+## push
 
 The `push` action adds a route on top of the stack and navigates forward to it. This differs from `navigate` in that `navigate` will pop back to earlier in the stack if a route of the given name is already present there. `push` will always add on top, so a route can be present multiple times.
 
@@ -62,7 +62,7 @@ const pushAction = StackActions.push('Profile', { user: 'Wojtek' });
 navigation.dispatch(pushAction);
 ```
 
-### pop
+## pop
 
 The `pop` action takes you back to a previous screen in the stack. It takes one optional argument (`count`), which allows you to specify how many screens to pop back by.
 
@@ -76,7 +76,7 @@ const popAction = StackActions.pop(1);
 navigation.dispatch(popAction);
 ```
 
-### popToTop
+## popToTop
 
 The `popToTop` action takes you back to the first screen in the stack, dismissing all the others. It's functionally identical to `StackActions.pop({n: currentIndex})`.
 

versioned_docs/version-5.x/tab-actions.md

@@ -8,7 +8,7 @@ sidebar_label: TabActions
 
 The following actions are supported:
 
-### jumpTo
+## jumpTo
 
 The `jumpTo` action can be used to jump to an existing route in the tab navigator.