Fix broken links

Signed-off-by: Thomas Hallgren <thomas@tada.se>

Author: thallgren

versioned_docs/version-2.21/reference/rbac.md

@@ -266,4 +266,4 @@ roleRef:
   apiGroup: rbac.authorization.k8s.io
 ```
 
-The user will also need the [Traffic Manager connect permission](#traffic-manager-connect-permission) described above.
+The user will also need the [Traffic Manager connect permission](#cluster-wide-installation) described above.

versioned_docs/version-2.22/howtos/large-clusters.md

@@ -47,4 +47,4 @@ Managers, as long as each one manages its own unique set of namespaces.
 
 A client that connects to a Traffic Manager will automatically be limited to its managed namespaces.
 
-See [Installing a namespaced-scoped traffic-manager](../install/manager.md#installing-a-namespace-scoped-traffic-manager) for details.
+See [Limiting the Namespace Scope](../install/manager.md#limiting-the-namespace-scope) for details.

versioned_docs/version-2.22/reference/architecture.md

@@ -43,4 +43,4 @@ running `telepresence list` or `kubectl describe pod <pod-name>`.
 Depending on if an `replace` or `intercept` is active or not, the Traffic Agent will either route the incoming request 
 to your workstation, or it will pass it along to the container in the pod usually handling requests.
 
-Please see [Traffic Agent Sidecar](intercepts/sidecar.md) for details.
+Please see [Traffic Agent Sidecar](engagements/sidecar.md) for details.

versioned_docs/version-2.22/reference/rbac.md

@@ -58,6 +58,7 @@ is configured with a dynamic namespace selector.
 
 These are the permissions required by the `traffic-manager` account in such a configuration:
 
+### Traffic Manager Permissions
 ```yaml
 ---
 apiVersion: v1
@@ -262,4 +263,4 @@ roleRef:
   apiGroup: rbac.authorization.k8s.io
 ```
 
-The user will also need the [Traffic Manager connect permission](#traffic-manager-connect-permission) described above.
+The user will also need the [Traffic Manager connect permission](#traffic-manager-permissions) described above.