From d40d32b93e293fa52478fa0a28a52708c5ddd3c2 Mon Sep 17 00:00:00 2001
From: "autofix-ci[bot]" <114827586+autofix-ci[bot]@users.noreply.github.com>
Date: Fri, 2 Aug 2024 20:53:27 +0000
Subject: [PATCH] ci: apply automated fixes

---
 docs/guides/device-gateway/agent.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/guides/device-gateway/agent.md b/docs/guides/device-gateway/agent.md
index b93215bf8..748c91866 100644
--- a/docs/guides/device-gateway/agent.md
+++ b/docs/guides/device-gateway/agent.md
@@ -256,7 +256,7 @@ For **Owner**, select the bot user you use created, and select `bind:*.customer1
 This ACL will allow an agent with the authtoken to create tunnels on any subdomain of `customer1.{YOUR_DOMAIN}`.
 
 :::note
-If you did not create a [custom wildcard domain](#create-a-custom-wildcard-domain-optional), select your domain from the ACL rules drop-down box to bind to this authtoken. 
+If you did not create a [custom wildcard domain](#create-a-custom-wildcard-domain-optional), select your domain from the ACL rules drop-down box to bind to this authtoken.
 :::
 
 ![alt-text](img/authtoken.png)
@@ -320,6 +320,7 @@ tunnels:
     addr: 4040
     inspect: false
 ```
+
 ### Start the agent to access the agent API
 
 Now that you’ve updated the `ngrok.yml` config file, start the tunnel for the agent API by running the following