Apply suggestion from @boruszak

Co-authored-by: Jeff Boruszak <[email protected]>

Author: nphilbrook

content/consul/v1.22.x/content/docs/deploy/server/cloud-auto-join.mdx

@@ -191,13 +191,7 @@ Variables can also be provided by environmental variables:
 - `ARM_CLIENT_ID` for client
 - `ARM_CLIENT_SECRET` for secret access key
 
-<Note>
-
-If any of the tentant, client, or client_secret arguments are omitted, then Consul will fall back to Managed Service Identities (see below) and
-any client_id that _was_ specified will be ignored for the purposes of MSI. To pass a specific client_id to MSI (for example,
-to use a User-Managed identity on a VM that also has a System-Managed identity, you must use the environment variable `AZURE_CLIENT_ID` (reference the [Azure autorest package documentation](https://github.com/Azure/go-autorest/blob/autorest/v0.11.29/autorest/azure/auth/auth.go#L43)
-
-</Note>
+If you omit any of the `TENANT`, `CLIENT`, or `CLIENT_SECRET` arguments, then Consul defaults to Managed Service Identities instead. Any client identification that was specified is ignored for the purposes of MSI. To pass client identity to MSI, you must use the `AZURE_CLIENT_ID` environment variable. For more information, refer to the [Azure autorest package documentation](https://github.com/Azure/go-autorest/blob/autorest/v0.11.29/autorest/azure/auth/auth.go#L43).
 
 Use these configuration parameters when using tags: