lint fixes

docs/pages/database-access/getting-started.mdx

@@ -146,7 +146,7 @@ $ teleport db start \
   title="AWS Credentials"
 >
   The node that connects to the database should have AWS credentials configured
-  with the policy from [step 1](#step-13-set-up-aurora).
+  with the policy from [step 1](#step-14-set-up-aurora).
 </Admonition>
 
 ## Step 3/4. Create a user and role

docs/pages/database-access/guides/azure-sql-server-ad.mdx

@@ -194,15 +194,15 @@ connect with is not attached to the Teleport Database Service virtual machine.
 You can navigate to the [Virtual Machines](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Compute%2FVirtualMachines) page within Azure Portal,
 open the **Teleport instance**, **Identity** section, and choose **User
 assigned** to see all identities you can connect with. If you don’t see your
-identity check [Step 4](#step-47-configure-azure-managed-identities) to see how
+identity check [Step 4](#step-36-configure-azure-managed-identities) to see how
 to add it.
 
 ### Login failed for the user
 
 When connecting to your database, and you see the error `mssql: login error: Login
 failed for user '<token-identified principal>'`, it means your managed identity
 login is not present on the SQL database. You’ll need to create their users as
-described in [Step 5](#step-57-enable-managed-identities-login-on-sql-server).
+described in [Step 5](#step-46-enable-managed-identities-login-on-sql-server).
 Remember: you must create the users on all databases you want to connect.
 
 ## Next steps

docs/pages/database-access/guides/mongodb-atlas.mdx

@@ -146,7 +146,7 @@ See the full [YAML reference](../reference/configuration.mdx) for details.
 
 See below for details on how to configure the Teleport Database Service.
 
-#### Connection endpoint
+### Connection endpoint
 
 You will need to provide your Atlas cluster's connection endpoint for the `db_service.databases[*].uri` configuration option or `--uri` CLI flag. You can find this via the Connect dialog on the Database Deployments overview page:
 
@@ -163,7 +163,7 @@ Use only the scheme and hostname parts of the connection string in the URI:
 $ --uri=mongodb+srv://cluster0.abcde.mongodb.net
 ```
 
-#### Atlas CA certificate
+### Atlas CA certificate
 
 MongoDB Atlas uses certificates signed by Let's Encrypt.
 

docs/pages/desktop-access/getting-started.mdx

@@ -48,13 +48,7 @@ access to Windows desktops.
   encrypted LDAP connection). Typically this means installing
   [AD CS](https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/)
 
-## Step 1/2. Install Teleport
-
-### Set up the Teleport Auth and Proxy Services
-
-(!docs/pages/includes/database-access/start-auth-proxy.mdx!)
-
-## Step 2/2. Run the discovery wizard
+## Step 1/2. Run the discovery wizard
 
 In your web browser, access the teleport Web UI at <ScopedBlock scope={["oss", "enterprise"]}>
 `teleport.example.com`</ScopedBlock><ScopedBlock scope={["cloud"]}>
@@ -120,6 +114,8 @@ windows_desktop_service:
 
 Click **Next**.
 
+## Step 2/2. Start Teleport
+
 Once you've saved `/etc/teleport.yaml`, start Teleport:
 
 <Tabs>

docs/pages/reference/helm-reference/teleport-kube-agent.mdx

@@ -472,7 +472,7 @@ You can specify multiple database filters by adding additional list elements.
 </Admonition>
 
 <Admonition type="note" title="Azure IAM">
-  For Azure database auto-discovery to work, your Database Service pods will need to have appropriate IAM permissions as per the [database documentation](../../database-access/guides/azure-postgres-mysql.mdx#step-35-configure-iam-permissions-for-teleport).
+  For Azure database auto-discovery to work, your Database Service pods will need to have appropriate IAM permissions as per the [database documentation](../../database-access/guides/azure-postgres-mysql.mdx#step-46-configure-iam-permissions-for-teleport).
 
   After configuring a service principal with appropriate IAM permissions, you must pass credentials to the pods.
   The easiest way is to use an Azure client secret.