Update Openshift SCC docs link

Signed-off-by: Shubham Pampattiwar <[email protected]>

site/content/docs/main/csi-snapshot-data-movement.md

@@ -502,7 +502,7 @@ advanced configuration options for `BackupPVC`, allowing users to fine-tune acce
 [3]: file-system-backup.md
 [4]: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/
 [5]: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation
-[6]: https://docs.openshift.com/container-platform/3.11/admin_guide/manage_scc.html
+[6]: https://docs.openshift.com/container-platform/4.16/authentication/managing-security-context-constraints.html
 [7]: https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv
 [8]: api-types/backupstoragelocation.md
 [9]: supported-providers.md

site/content/docs/main/file-system-backup.md

@@ -138,7 +138,7 @@ To mount the correct hostpath to pods volumes, run the node-agent pod in `privil
 
 If node-agent is not running in a privileged mode, it will not be able to access pods volumes within the mounted 
 hostpath directory because of the default enforced SELinux mode configured in the host system level. You can 
-[create a custom SCC](https://docs.openshift.com/container-platform/3.11/admin_guide/manage_scc.html) to relax the 
+[create a custom SCC](https://docs.openshift.com/container-platform/4.16/authentication/managing-security-context-constraints.html) to relax the 
 security in your cluster so that node-agent pods are allowed to use the hostPath volume plugin without granting 
 them access to the `privileged` SCC.