diff --git a/cmd/mountlib/mount.md b/cmd/mountlib/mount.md
index 30bcee983..1b73feb9d 100644
--- a/cmd/mountlib/mount.md
+++ b/cmd/mountlib/mount.md
@@ -240,7 +240,7 @@ to run as the SYSTEM account. A third alternative is to use the
 Read more in the [install documentation](https://rclone.org/install/).
 Note that when running rclone as another user, it will not use
 the configuration file from your profile unless you tell it to
-with the [`--config`](https://rclone.org/docs/#config-config-file) option.
+with the [`--config`](https://rclone.org/docs/#config) option.
 Note also that it is now the SYSTEM account that will have the owner
 permissions, and other accounts will have permissions according to the
 group or others scopes. As mentioned above, these will then not get the
diff --git a/docs/content/docs.md b/docs/content/docs.md
index d5da9e5a4..437bdc04f 100644
--- a/docs/content/docs.md
+++ b/docs/content/docs.md
@@ -17,7 +17,7 @@ Configure
 
 First, you'll need to configure rclone.  As the object storage systems
 have quite complicated authentication these are kept in a config file.
-(See the [`--config`](#config-config-file) entry for how to find the config
+(See the [`--config`](#config) entry for how to find the config
 file and choose its location.)
 
 The easiest way to make the config is to run rclone with the config
@@ -936,7 +936,7 @@ compare directory must not overlap the destination directory.
 
 See `--copy-dest` and `--backup-dir`.
 
-### --config=CONFIG_FILE
+### --config
 
 Specify the location of the rclone configuration file, to override
 the default. E.g. `rclone config --config="rclone.conf"`.
@@ -2823,7 +2823,7 @@ a valid password, and `--password-command` has not been supplied.
 
 Whenever running commands that may be affected by options in a
 configuration file, rclone will look for an existing file according
-to the rules described [above](#config-config-file), and load any it
+to the rules described [above](#config), and load any it
 finds. If an encrypted file is found, this includes decrypting it,
 with the possible consequence of a password prompt. When executing
 a command line that you know are not actually using anything from such
diff --git a/docs/content/install.md b/docs/content/install.md
index a2234fc8a..bb286b2d9 100644
--- a/docs/content/install.md
+++ b/docs/content/install.md
@@ -491,7 +491,7 @@ the locations that rclone will use.
 
 To override them set the corresponding options (as command-line arguments, or as
 [environment variables](https://rclone.org/docs/#environment-variables)):
-  - [--config](https://rclone.org/docs/#config-config-file)
+  - [--config](https://rclone.org/docs/#config)
   - [--cache-dir](https://rclone.org/docs/#cache-dir-dir)
   - [--temp-dir](https://rclone.org/docs/#temp-dir-dir)
 
@@ -546,7 +546,7 @@ NOTE: Remember that when rclone runs as the `SYSTEM` user, the user profile
 that it sees will not be yours. This means that if you normally run rclone with
 configuration file in the default location, to be able to use the same configuration
 when running as the system user you must explicitly tell rclone where to find
-it with the [`--config`](https://rclone.org/docs/#config-config-file) option,
+it with the [`--config`](https://rclone.org/docs/#config) option,
 or else it will look in the system users profile path (`C:\Windows\System32\config\systemprofile`).
 To test your command manually from a Command Prompt, you can run it with
 the [PsExec](https://docs.microsoft.com/en-us/sysinternals/downloads/psexec)