Update for review comments

docs/book/src/topics/workload-identity.md

@@ -35,15 +35,15 @@ you have access to Azure cloud services.
 
 - Create two federated identity credentials
 
-  Export environment variables used for creating the federated identity credentials:
+  Export environment variables used for creating a federated identity credential:
 
   - `SERVICE_ACCOUNT_NAMESPACE`: Namespace where the capz-manager and
     azureserviceoperator-controller-manager pods will run.
   - `SERVICE_ACCOUNT_NAME`: Name of the capz-manager or azureserviceoperator-default k8s service account.
   - `SERVICE_ACCOUNT_ISSUER`: Path of the Azure storage container created in the previous step, specifically:
     - `"https://${AZURE_STORAGE_ACCOUNT}.blob.core.windows.net/${AZURE_STORAGE_CONTAINER}/"`
 
-  Create two federated identity credentials, one for CAPZ and one for ASO, by following [these instructions](https://azure.github.io/azure-workload-identity/docs/topics/federated-identity-credential.html).
+  Create two federated identity credentials, one for CAPZ and one for ASO, by following [these instructions](https://azure.github.io/azure-workload-identity/docs/topics/federated-identity-credential.html). You'll need to set `SERVICE_ACCOUNT_NAME` and `SERVICE_ACCOUNT_NAMESPACE` to different values for each credential.
   Use either `user-assigned-identity` or `AD application` when creating the credentials, and add the `contributor` role to each.
 
 - Create a kind cluster with the following command:
@@ -145,7 +145,7 @@ to give the identity Contributor access to the Azure subscription where the work
   - providerID: /subscriptions/${AZURE_SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/${USER_ASSIGNED_IDENTITY_NAME}
   ```
 
-  A sample `AzureMahineTemplate` after the edit should look like the below:
+  A sample `AzureMachineTemplate` after the edit should look like the below:
 
   ```yaml
   apiVersion: infrastructure.cluster.x-k8s.io/v1beta1