Hyperlint Automation: Broken Link Fixes

src/content/docs/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/as-a-service/windows.mdx

@@ -64,7 +64,7 @@ By default, Cloudflare Tunnel expects all of the configuration to exist in the `
    cloudflared.exe tunnel create <Tunnel Name>
    ```
 
-   This will generate a [credentials file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#credentials-file) in `.json` format.
+   This will generate a [credentials file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) in `.json` format.
 
 10. [Create a configuration file](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#4-create-a-configuration-file) with the following content:
 

src/content/docs/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel.mdx

@@ -105,7 +105,7 @@ cloudflared tunnel login
 Running this command will:
 
 - Open a browser window and prompt you to log in to your Cloudflare account. After logging in to your account, select your hostname.
-- Generate an account certificate, the [cert.pem file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#certpem), in the [default `cloudflared` directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#default-cloudflared-directory).
+- Generate an account certificate, the [cert.pem file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#certpem), in the [default `cloudflared` directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/).
 
 ## 3. Create a tunnel and give it a name
 
@@ -116,7 +116,7 @@ cloudflared tunnel create <NAME>
 Running this command will:
 
 - Create a tunnel by establishing a persistent relationship between the [name you provide](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#tunnel-name) and a [UUID](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#tunnel-uuid) for your tunnel. At this point, no connection is active within the tunnel yet.
-- Generate a [tunnel credentials file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#credentials-file) in the [default `cloudflared` directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#default-cloudflared-directory).
+- Generate a [tunnel credentials file](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) in the [default `cloudflared` directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/).
 - Create a subdomain of `.cfargotunnel.com`.
 
 From the output of the command, take note of the tunnel's UUID and the path to your tunnel's credentials file.

src/content/docs/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/local-tunnel-terms.mdx

@@ -18,7 +18,7 @@ This page contains terminology specific to locally-managed Cloudflare Tunnels. F
 
 ## Configuration file
 
-This is a YAML file that functions as the operating manual for `cloudflared`. `cloudflared` will automatically look for the configuration file in the [default `cloudflared` directory](#default-cloudflared-directory), but you can store your configuration file in any directory. It is recommended to always specify the file path for your configuration file whenever you reference it. By creating a configuration file, you can have fine-grained control over how their instance of `cloudflared` will operate. This includes operations like what you want `cloudflared` to do with traffic (for example, proxy websockets to port `xxxx` or SSH to port `yyyy`), where `cloudflared` should search for authorization (credentials file, tunnel token), and what mode it should run in (for example, [`warp-routing`](/cloudflare-one/connections/connect-networks/private-net/)). In the absence of a configuration file, cloudflared will proxy outbound traffic through port `8080`. For more information on how to create, store, and structure a configuration file, refer to the [dedicated instructions](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/).
+This is a YAML file that functions as the operating manual for `cloudflared`. `cloudflared` will automatically look for the configuration file in the [default `cloudflared` directory](), but you can store your configuration file in any directory. It is recommended to always specify the file path for your configuration file whenever you reference it. By creating a configuration file, you can have fine-grained control over how their instance of `cloudflared` will operate. This includes operations like what you want `cloudflared` to do with traffic (for example, proxy websockets to port `xxxx` or SSH to port `yyyy`), where `cloudflared` should search for authorization (credentials file, tunnel token), and what mode it should run in (for example, [`warp-routing`](/cloudflare-one/connections/connect-networks/private-net/)). In the absence of a configuration file, cloudflared will proxy outbound traffic through port `8080`. For more information on how to create, store, and structure a configuration file, refer to the [dedicated instructions](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/).
 
 ## Cert.pem
 

src/content/docs/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/tunnel-permissions.mdx

@@ -23,7 +23,7 @@ Refer to the table below for a comparison between the two files and the purposes
 | **Purpose**             | Authenticates your instance of `cloudflared` against your Cloudflare account                                                     | Authenticates the tunnel it is associated with                                                                                   |
 | **Scope**               | Account-wide                                                                                                                     | Tunnel-specific                                                                                                                  |
 | **File type**           | `.pem`                                                                                                                           | `.json`                                                                                                                          |
-| **Stored in**           | [Default directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#default-cloudflared-directory) | [Default directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#default-cloudflared-directory) |
+| **Stored in**           | [Default directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) | [Default directory](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) |
 | **Issued when running** | `cloudflared tunnel login`                                                                                                       | `cloudflared tunnel create <NAME>`                                                                                               |
 | **Valid for**           | At least 10 years, and the service token it contains is valid until revoked                                                      | Does not expire                                                                                                                  |
 | **Needed to**           | Manage tunnels (for example, create, route, delete and list tunnels)                                                             | Run a tunnel. Create a config file.                                                                                              |