Merge pull request #242739 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: v-alje

articles/aks/azure-cni-overlay.md

@@ -132,7 +132,7 @@ resourceGroup="myResourceGroup"
 location="westcentralus"
 
 az aks update --name $clusterName \
---group $resourceGroup \
+--resource-group $resourceGroup \
 --network-plugin-mode overlay \
 --pod-cidr 192.168.0.0/16
 ```

articles/aks/use-kms-etcd-encryption.md

@@ -24,7 +24,7 @@ For more information on using the KMS plugin, see [Encrypting Secret Data at Res
 
 > [!WARNING]
 > KMS supports Konnectivity or [API Server Vnet Integration][api-server-vnet-integration]. 
-> You can use `kubectl get po -n kube-system` to verify the results show that a konnectivity-agent-xxx pod is running. If there is, it means the AKS cluster is using Konnectivity. When using VNet integration, you can run the command `az aks cluster show -g -n` to verify the setting `enableVnetIntegration` is set to **true**.
+> You can use `kubectl get po -n kube-system` to verify the results show that a konnectivity-agent-xxx pod is running. If there is, it means the AKS cluster is using Konnectivity. When using VNet integration, you can run the command `az aks show -g -n` to verify the setting `enableVnetIntegration` is set to **true**.
 
 ## Limitations
 

articles/azure-resource-manager/bicep/deploy-github-actions.md

@@ -111,7 +111,7 @@ Create secrets for your Azure credentials, resource group, and subscriptions.
 
 1. In [GitHub](https://github.com/), navigate to your repository.
 
-1. Select **Security > Secrets and variables > Actions > New repository secret**. 
+1. Select **Settings > Secrets and variables > Actions > New repository secret**. 
 
 1. Paste the entire JSON output from the Azure CLI command into the secret's value field. Name the secret `AZURE_CREDENTIALS`.