Fixed spacing issue in yaml and command ordering for keyvault creation.

Fixed the spacing issue in service provider class yaml and corrected the order of setting environment variables and creating keyvault command.

Author: sapinderpalsingh

articles/azure-arc/kubernetes/tutorial-akv-secrets-provider.md

@@ -244,16 +244,19 @@ You should see output similar to the example below.
 
 Next, specify the Azure Key Vault to use with your connected cluster. If you don't already have one, create a new Key Vault by using the following commands. Keep in mind that the name of your Key Vault must be globally unique.
 
-```azurecli
-az keyvault create -n $AZUREKEYVAULT_NAME -g $AKV_RESOURCE_GROUP -l $AZUREKEYVAULT_LOCATION
 
-Next, set the following environment variables:
+Set the following environment variables:
 
 ```azurecli-interactive
 export AKV_RESOURCE_GROUP=<resource-group-name>
 export AZUREKEYVAULT_NAME=<AKV-name>
 export AZUREKEYVAULT_LOCATION=<AKV-location>
 ```
+Next, run the following command
+
+```azurecli
+az keyvault create -n $AZUREKEYVAULT_NAME -g $AKV_RESOURCE_GROUP -l $AZUREKEYVAULT_LOCATION
+```
 
 Azure Key Vault can store keys, secrets, and certificates. For this example, you can set a plain text secret called `DemoSecret` by using the following command:
 
@@ -293,7 +296,7 @@ Currently, the Secrets Store CSI Driver on Arc-enabled clusters can be accessed
    apiVersion: secrets-store.csi.x-k8s.io/v1
    kind: SecretProviderClass
    metadata:
-   name: akvprovider-demo
+     name: akvprovider-demo
    spec:
      provider: azure
      parameters:
@@ -412,4 +415,4 @@ For more information about resolving common issues, see the open source troubles
 ## Next steps
 
 - Want to try things out? Get started quickly with an [Azure Arc Jumpstart scenario](https://aka.ms/arc-jumpstart-akv-secrets-provider) using Cluster API.
-- Learn more about [Azure Key Vault](../../key-vault/general/overview.md).
+- Learn more about [Azure Key Vault](../../key-vault/general/overview.md).