ci: apply automated fixes

Author: autofix-ci[bot]

docs/agent/cli-api.mdx

@@ -1395,7 +1395,7 @@ thus a private key is not included in the resource.
 | --------------------------------------------------- | ----------------------------------------------- |
 | [create](#ngrok-api-certificate-authorities-create) | Upload a new Certificate Authority              |
 | [delete](#ngrok-api-certificate-authorities-delete) | Delete a Certificate Authority                  |
-| [get](#ngrok-api-certificate-authorities-get)       | Get detailed information about a certificate...  |
+| [get](#ngrok-api-certificate-authorities-get)       | Get detailed information about a certificate... |
 | [list](#ngrok-api-certificate-authorities-list)     | List all Certificate Authority on this account  |
 | [update](#ngrok-api-certificate-authorities-update) | Update attributes of a Certificate Authority... |
 

docs/agent/index.mdx

@@ -132,13 +132,13 @@ Authtoken ACLs restrict what actions an ngrok agent connecting with that
 authtoken is allowed to take. You may define multiple ACLs. Authtokens with no
 ACLs may take all actions. The following ACLs are supported:
 
-| Example              | Description                                                              |
-| -------------------- | ------------------------------------------------------------------------ |
-| `bind:foo.ngrok.app` | The agent may only create an endpoint on `foo.ngrok.app`                 |
-| `bind:*.example.com` | The agent may only create endpoints on subdomains of `example.com`       |
+| Example              | Description                                                                |
+| -------------------- | -------------------------------------------------------------------------- |
+| `bind:foo.ngrok.app` | The agent may only create an endpoint on `foo.ngrok.app`                   |
+| `bind:*.example.com` | The agent may only create endpoints on subdomains of `example.com`         |
 | `bind:foo=bar`       | The agent may create a labeled endpoint with the label `foo=bar`           |
 | `bind:app=*`         | The agent may create labeled endpoints with labels like `app=x` or `app=y` |
-| `bind:*`             | The agent may listen on all endpoints                                    |
+| `bind:*`             | The agent may listen on all endpoints                                      |
 
 ## API Keys
 

docs/pricing-limits/free-plan-limits.mdx

@@ -8,9 +8,9 @@ import Tabs from "@theme/Tabs";
 
 Learn about the limits enforced in the free ngrok for developers plan.
 
-:::note 
+:::note
 The free tier does NOT have timeouts on tunnels. If you'd like to run your endpoint all the time, you can do so, on the free tier, as a [background service](https://ngrok.com/docs/agent/#background-service).
-::: 
+:::
 
 :::tip
 See [Pricing and Limits](https://ngrok.com/pricing?ref=docs) to learn how to increase or remove these limits.

docs/universal-gateway/domains.mdx

@@ -78,7 +78,7 @@ Reserving subdomains of a wildcard domain within the ngrok dashboard count towar
 
 ### Random Domains
 
-For some applications, you may not care much about the actual domain for the endpoint. Generating these can be a pain, so we've included an easy way 
+For some applications, you may not care much about the actual domain for the endpoint. Generating these can be a pain, so we've included an easy way
 to create and use these for endpoints. Using the value `https://${randomUrl}` in the `url` field will generate a random url for you to use with your endpoint.
 
 ```bash

docs/using-ngrok-with/virtualHosts.md

@@ -4,7 +4,7 @@ title: Virtual hosts (MAMP, WAMP, etc)
 
 # Using ngrok with Virtual hosts (MAMP, WAMP, etc)
 
-Popular web servers such as MAMP and WAMP rely on a technique popularly referred to as 'Virtual Hosting' which means that they consult the HTTP request's `Host` header to determine which of their multiple sites they should serve. To expose a site like this it is possible to ask ngrok to rewrite the `Host` header of all  requests to match what your web server expects. You can do this by using the `--host-header` option (see: [Rewriting the Host header](/universal-gateway/http/#rewrite-host-header)) to pick which virtual host you want to target. For example, to route to your local site `myapp.dev`, you would run:
+Popular web servers such as MAMP and WAMP rely on a technique popularly referred to as 'Virtual Hosting' which means that they consult the HTTP request's `Host` header to determine which of their multiple sites they should serve. To expose a site like this it is possible to ask ngrok to rewrite the `Host` header of all requests to match what your web server expects. You can do this by using the `--host-header` option (see: [Rewriting the Host header](/universal-gateway/http/#rewrite-host-header)) to pick which virtual host you want to target. For example, to route to your local site `myapp.dev`, you would run:
 
     ngrok http --host-header=myapp.dev 80