Fix linter issues

CHANGELOG.md

@@ -3433,7 +3433,7 @@ can limit access by changing the options on the new `event` resource.
 The minimum set of Kubernetes permissions that need to be granted to Teleport
 proxies has been updated. If you use the Kubernetes integration, please make
 sure that the ClusterRole used by the proxy has [sufficient
-permissions](./docs/pages/kubernetes-access/manage-access/rbac.mdx).
+permissions](./docs/pages/kubernetes-access/controls.mdx).
 
 ##### Path prefix for etcd
 

docs/pages/access-controls/reference.mdx

@@ -99,7 +99,7 @@ Label              | `v3` Default   | `v4`, `v5` and `v6` Default
 `db_labels`         | `[{"*": "*"}]` | `[]`
 
 Role `v6` introduced a new field `kubernetes_resources` that allows
-fine-grained control over Kubernetes resources. See [Kubernetes RBAC](../kubernetes-access/manage-access/rbac.mdx) for more details.
+fine-grained control over Kubernetes resources. See [Kubernetes RBAC](../kubernetes-access/controls.mdx) for more details.
 
 Version              |  `kubernetes_resources`
 ------------------ | --------------

docs/pages/api/rbac.mdx

@@ -939,7 +939,7 @@ resources:
 
 - [Servers](../server-access/rbac.mdx)
 - [Databases](../database-access/rbac.mdx)
-- [Kubernetes clusters](../kubernetes-access/manage-access/rbac.mdx)
+- [Kubernetes clusters](../kubernetes-access/controls.mdx)
 - [Windows Desktops](../desktop-access/rbac.mdx)
 - [Applications](../application-access/controls.mdx)
 

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

@@ -83,7 +83,7 @@ GRANT rds_iam TO alice;
 For more information about connecting to the PostgreSQL instance directly,
 see the AWS [documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ConnectToPostgreSQLInstance.html).
 
-See the [Automatic User Provisioning](./rbac/configuring-access.mdx) guide for how to configure Teleport to create accounts for your PostgreSQL users on demand.
+See the [Automatic User Provisioning](./rbac.mdx) guide for how to configure Teleport to create accounts for your PostgreSQL users on demand.
 
 ## Step 2/5. Configure the Teleport Database Service
 

docs/pages/database-access/rbac.mdx

@@ -11,7 +11,7 @@ everything, QA team and engineers have full access to staging databases, and
 engineers can gain temporary access to the production database in case of
 emergency"*.
 
-For a more general description of Teleport roles and examples see [RBAC](../../access-controls/introduction.mdx), as
+For a more general description of Teleport roles and examples see [RBAC](../access-controls/introduction.mdx), as
 this section focuses on configuring RBAC for database access.
 
 ## Role configuration
@@ -99,13 +99,13 @@ is not currently enforced on MySQL connection attempts.
 Similar to other role fields, `db_*` fields support templating variables.
 
 The `external.xyz` traits are replaced with values from external [single
-sign-on](../../access-controls/sso.mdx) providers. For OIDC, they will be
+sign-on](../access-controls/sso.mdx) providers. For OIDC, they will be
 replaced with the value of an "xyz" claim. For SAML, they are replaced 
 with an "xyz" assertion value. 
 
 For full details on how traits work in Teleport roles, see
 the [Teleport Access Controls
-Reference](../../access-controls/reference.mdx).
+Reference](../access-controls/reference.mdx).
 
 For example, here is what a role may look like if you want to assign allowed
 database names from the user's Okta `databases` assertion:

docs/pages/deploy-a-cluster/helm-deployments/digitalocean.mdx

@@ -278,6 +278,5 @@ Teleport:
 
 - Connect another Kubernetes cluster to Teleport by [deploying the Teleport Kubernetes Service](../../kubernetes-access/getting-started.mdx)
 - [Set up Machine ID with Kubernetes](../../machine-id/access-guides/kubernetes.mdx)
-- [Federated Access using Trusted Clusters](../../kubernetes-access/manage-access/federation.mdx)
 - [Single-Sign On and Kubernetes Access Control](../../kubernetes-access/controls.mdx)
 

docs/pages/kubernetes-access/controls.mdx

@@ -13,8 +13,7 @@ Teleport role to manage access to Kubernetes clusters you have connected to
 Teleport.
 
 For an example of how to use Teleport roles to manage access to Kubernetes with
-a local `minikube` cluster, see our [RBAC how-to
-guide](./manage-access/rbac.mdx).
+a local `minikube` cluster, see our [RBAC how-to guide](./manage-access.mdx).
 
 ## Role fields for managing Kubernetes access
 

docs/pages/kubernetes-access/manage-access.mdx

@@ -442,14 +442,14 @@ $ kubectl config use-context minikube
 ## Next steps
 
 For more detailed information on how Teleport RBAC for Kubernetes works, consult
-the Kubernetes [Access Controls Guide](../controls.mdx). You can leave your
+the Kubernetes [Access Controls Guide](controls.mdx). You can leave your
 `minikube` cluster running so you can try out different Teleport and Kubernetes
 RBAC configurations.
 
 Now that you know how to configure Teleport's RBAC system to control access to
 Kubernetes clusters, learn how to set up [Resource Access
-Requests](../../access-controls/access-requests/resource-requests.mdx)
+Requests](../access-controls/access-requests/resource-requests.mdx)
 for just-in-time access and [Access Request
-plugins](../../access-controls/access-request-plugins/index.mdx) so you can manage
+plugins](../access-controls/access-request-plugins/index.mdx) so you can manage
 access with your communication workflow of choice.
 

docs/pages/machine-id/access-guides/databases.mdx

@@ -72,7 +72,7 @@ This rule will allow the bot to do two things:
 The `'*': '*'` label selector grants access to any database server configured in Teleport.
 In production, consider restricting the bot's access using a more specific
 label selector; see the
-[Database Access RBAC guide](../../database-access/rbac/configuring-access.mdx)
+[Database Access RBAC guide](../../database-access/rbac.mdx)
 for a full reference of database-related role options.
 
 ## Step 2/4. Configure a database `tbot` output
@@ -248,4 +248,4 @@ access controls.
 ## Next steps
 
 - Read the [configuration reference](../reference/configuration.mdx) to explore
-  all the available configuration options.
+  all the available configuration options.