diff --git a/website/integrations/networking/technitium/index.md b/website/integrations/networking/technitium/index.md
index 4ed7b45ed0..4c11458ac2 100644
--- a/website/integrations/networking/technitium/index.md
+++ b/website/integrations/networking/technitium/index.md
@@ -58,10 +58,10 @@ Technitium DNS uses the `roles` claim to map SSO users to local groups. Create a
 
 1. Log in to authentik as an administrator and open the authentik Admin interface.
 2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard.
-    - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
+    - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Note the **slug** value because it will be required later.
     - **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
     - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
-        - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
+        - Note the **Client ID** and **Client Secret** values because they will be required later.
         - Add a **Redirect URI** of type `Strict` `Authorization` as `https://technitium.company/sso/callback`.
         - Select any available signing key.
         - Ensure that the `openid`, `email`, and `profile` scopes are selected. Remove the `email` scope if you prefer usernames to use the preferred username claim instead of the email address; if you do this, remove the `email` scope from Technitium in the next section.