docs: fix links

docs/usage/configuration-options.md

@@ -23,7 +23,7 @@ You can store your Renovate configuration file in one of the following locations
 Renovate always uses the config from the repository's default branch, even if that configuration specifies multiple `baseBranches`.
 Renovate does not read/override the config from within each base branch if present.
 
-Also, be sure to check out Renovate's [shareable config presets](/config-presets/) to save yourself from reinventing any wheels.
+Also, be sure to check out Renovate's [shareable config presets](./config-presets.md) to save yourself from reinventing any wheels.
 
 If you have any questions about the config options, or want to get help/feedback about a config, go to the [discussions tab in the Renovate repository](https://github.com/renovatebot/renovate/discussions) and start a new "config help" discussion.
 We will do our best to answer your question(s).

docs/usage/faq.md

@@ -37,7 +37,7 @@ You can set more than one PR target branch in the `baseBranches` array.
 
 ### Support private npm modules
 
-See the dedicated [Private npm module support](/private-modules/) page.
+See the dedicated [Private npm module support](./private-modules.md) page.
 
 ### Control Renovate's schedule
 

docs/usage/node.md

@@ -30,7 +30,7 @@ When Renovate processes your project's repository it will look for the files lis
 
 ## Configuring Support Policy
 
-Renovate supports a [`supportPolicy`](/configuration-options/#supportpolicy) option that can be passed the following values and associated versions (current as of April 2021):
+Renovate supports a [`supportPolicy`](./configuration-options.md#supportpolicy) option that can be passed the following values and associated versions (current as of April 2021):
 
 **Default:** `lts`
 
@@ -54,7 +54,7 @@ For example, to instruct Renovate to upgrade your project to the latest [Long-te
 We recommend that you define this support policy inside the `node` configuration object.
 This way, it is applied to all Node.js-related files.
 
-For additional language support see the [`supportPolicy` documentation](/configuration-options/#supportpolicy).
+For additional language support see the [`supportPolicy` documentation](./configuration-options.md#supportpolicy).
 
 ## Configuring which version of npm Renovate uses
 

docs/usage/noise-reduction.md

@@ -20,7 +20,7 @@ If you have any ideas on this topic, please contact the author by starting a [ne
 
 To reduce noise, you can reduce the number of updates in total, and a good way to do that is via intelligent grouping of related packages.
 
-As an example, our default `":app"` and `":library"` [presets](/config-presets/) include the rule `"group:monorepos"`, which means that "sibling" packages from known monorepos will always be grouped into the same branch/PR by renovate.
+As an example, our default `":app"` and `":library"` [presets](./config-presets.md) include the rule `"group:monorepos"`, which means that "sibling" packages from known monorepos will always be grouped into the same branch/PR by renovate.
 For example, all `@angular/*` packages that are updated at the same time will be raised in a "Renovate angular monorepo packages" PR.
 And every package in the React monorepo will be grouped together in a React monorepo PR too.
 

docs/usage/private-modules.md

@@ -136,7 +136,7 @@ The command run is `git config --global url."https://${token}@github.com/".inste
 
 The best way to do this now is using `hostRules` and no longer via `.npmrc` files on disk or in config.
 `hostRules` credentials with `hostType=npm` are written to a `.npmrc` file in the same directory as the `package.json` being updated.
-See [private npm modules](./private-npm-modules) for more details.
+See [private npm modules](./private-npm-modules.md) for more details.
 
 ### nuget