Update authorization-rbac links (#9463)

* update authorization-rbac links

* fix broken links

* undo modification of cn content

content/en/docs/concepts/policy/pod-security-policy.md

@@ -80,8 +80,8 @@ pod's service account (see [example](#run-another-pod)).
 
 ### Via RBAC
 
-[RBAC](/docs/admin/authorization/rbac/) is a standard Kubernetes authorization
-mode, and can easily be used to authorize use of policies.
+[RBAC](/docs/reference/access-authn-authz/rbac/) is a standard Kubernetes
+authorization mode, and can easily be used to authorize use of policies.
 
 First, a `Role` or `ClusterRole` needs to grant access to `use` the desired
 policies. The rules to grant access look like this:
@@ -136,8 +136,8 @@ paired with system groups to grant access to all pods run in the namespace:
 ```
 
 For more examples of RBAC bindings, see [Role Binding
-Examples](/docs/admin/authorization/rbac#role-binding-examples). For a complete
-example of authorizing a PodSecurityPolicy, see
+Examples](/docs/reference/access-authn-authz/rbac#role-binding-examples).
+For a complete example of authorizing a PodSecurityPolicy, see
 [below](#example).
 
 
@@ -149,7 +149,7 @@ and must not have superuser permissions. Otherwise requests would bypass
 authentication and authorization modules, all PodSecurityPolicy objects would be
 allowed, and users would be able to create privileged containers. For more details
 on configuring Controller Manager authorization, see [Controller
-Roles](/docs/admin/authorization/rbac/#controller-roles).
+Roles](/docs/reference/access-authn-authz/rbac/#controller-roles).
 
 ## Policy Order