docs: fix uninstall commands in openshift

Signed-off-by: Anish Ramasekar <anish.ramasekar@gmail.com>

website/content/en/configurations/deploy-in-openshift.md

@@ -47,6 +47,6 @@ description: >
 
     ```bash
     # Replace $target_namespace with the namespace used for helm install
-    oc adm policy remove-scc-to-user privileged system:serviceaccount:$target_namespace:secrets-store-csi-driver
-    oc adm policy remove-scc-to-user privileged system:serviceaccount:$target_namespace:csi-secrets-store-provider-azure
+    oc adm policy remove-scc-from-user privileged system:serviceaccount:$target_namespace:secrets-store-csi-driver
+    oc adm policy remove-scc-from-user privileged system:serviceaccount:$target_namespace:csi-secrets-store-provider-azure
     ```

website/content/en/configurations/feature-flags.md

@@ -11,7 +11,7 @@ description: >
 
 > Available in AKV Provider release `0.0.12+`
 
-> This feature will be enabled by default in AKV Provider release `v0.2.0`
+> This feature is enabled by default in AKV Provider release `v0.2.0`
 
 The Azure Key Vault provider for Secrets Store CSI Driver by default fetches the chain of certificates from Keyvault and writes to the mount in the same order in which the certificate chain was uploaded. This is an experimental feature that supports reordering of the certificate chain in the following order:
 

website/content/en/configurations/identity-access-modes/service-principal-mode.md

@@ -126,9 +126,8 @@ spec:
 ## Pros
 
 1. Supported on both Windows and Linux.
-1. Easiest option to connect to Azure Key Vault.
+2. Supports Kubernetes clusters hosted in any cloud or on-premises.
 
 ## Cons
 
 1. Service Principal credentials(client id & client secret) need to be created as a kubernetes *Secret* which is stored as plaintext in etcd.
-1. The only supported way to connect to Azure Key Vault from a non Azure environment.