Merge pull request #297723 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: Taojunshen

articles/azure-maps/power-bi-visual-get-started.md

@@ -159,7 +159,7 @@ The Azure Maps Power BI visual is available in the following services and applic
 | Power BI export                          | No           |
 | Power BI subscriptions                   | No           |
 
-**Where is Azure Maps available?**
+**Where is Azure Maps Visual for Power BI available?**
 
 At this time, Azure Maps is currently available in all countries and regions except:
 

articles/azure-resource-manager/templates/deployment-modes.md

@@ -23,7 +23,7 @@ In incremental mode, Resource Manager **leaves unchanged** resources that exist
 
 > [!IMPORTANT]
 >
-> Incremental mode is the recommended deployment dode. If there is a need to delete resources as part of a Bicep file or ARM JSON template, use [deployment stacks](../bicep/deployment-stacks.md).
+> Incremental mode is the recommended deployment mode. If there is a need to delete resources as part of a Bicep file or ARM JSON template, use [deployment stacks](../bicep/deployment-stacks.md).
 >
 > When redeploying an existing resource in incremental mode, all properties are reapplied. The **properties aren't incrementally added**. A common misunderstanding is to think properties that aren't specified in the template are left unchanged. If you don't specify certain properties, Resource Manager interprets the deployment as overwriting those values. Properties that aren't included in the template are reset to the default values. Specify all non-default values for the resource, not just the ones you're updating. The resource definition in the template always contains the final state of the resource. It can't represent a partial update to an existing resource.
 

articles/azure-vmware/deploy-disaster-recovery-using-jetstream.md

@@ -324,7 +324,7 @@ This cmdlet disables JetStream DR only on one of the clusters and doesn't comple
 
 JetStream DR is a solution that [JetStream Software](https://www.jetstreamsoft.com/) supports. For any product or support issues with JetStream, contact [email protected].  
 
-Azure VMware Solution uses the Run command to automate both the install and uninstall of JetStream DR. Contact Microsoft support for any issue with the run commands. For issues with JetStream install and uninstall cmdlets, contact JetStream for support. 
+Azure VMware Solution uses the Run command to automate both the install and uninstall of JetStream DR. Contact Microsoft support for any issue with the run commands. For issues with JetStream install and uninstall cmdlets, contact JetStream for [support](https://jetstreamsoft.com/portal/online-docs/contactJS/ContactJetStreamSoftware.html). 
 
 
 

articles/communication-services/concepts/reference.md

@@ -38,7 +38,7 @@ For each area, we have external pages to track and review our SDKs. Consult the
 | SMS  | [npm](https://www.npmjs.com/package/@azure/communication-sms)             | [NuGet](https://www.nuget.org/packages/Azure.Communication.Sms) | [PyPi](https://pypi.org/project/azure-communication-sms/)            | [Maven](https://search.maven.org/artifact/com.azure/azure-communication-sms)     | -       | -                 | -      |
 | UI Library             | [npm](https://www.npmjs.com/package/@azure/communication-react)           | -         | -              | -        | [GitHub](https://github.com/Azure/communication-ui-library-ios)                 | [GitHub](https://github.com/Azure/communication-ui-library-android)     | [GitHub](https://github.com/Azure/communication-ui-library), [Storybook](https://azure.github.io/communication-ui-library/?path=/docs/overview--docs) |
 
-## Related lass/method articles
+## Related class/method articles
 
 For more information about class/reference information for each SDK, see:
 

articles/event-grid/authenticate-with-namespaces-using-json-web-tokens.md

@@ -131,7 +131,7 @@ az resource update \
  
 ```
 ## JSON Web Token format
-Json Web Tokens are divided into the JWT Header and JWT payload sections.
+JSON Web Tokens are divided into the JWT Header and JWT payload sections.
 
 ### JWT Header 
 

articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md

@@ -160,7 +160,7 @@ When the private endpoint is created, five fully qualified domain names (FQDNs)
 
 The five domain names are formatted in this pattern:
 
-`{Vault-ID}-asr-pod01-{type}-.{target-geo-code}.privatelink.siterecovery.windowsazure.com`
+`{Vault-ID}-asr-pod01-{type}.{target-geo-code}.privatelink.siterecovery.windowsazure.com`
 
 ### Approve private endpoints for site recovery
 
@@ -299,7 +299,7 @@ Create one private DNS zone to allow the Site Recovery provider (for Hyper-V mac
       private DNS zone.
 
       These fully qualified domain names match this pattern:
-      `{Vault-ID}-asr-pod01-{type}-.{target-geo-code}.siterecovery.windowsazure.com`
+      `{Vault-ID}-asr-pod01-{type}.{target-geo-code}.siterecovery.windowsazure.com`
 
       :::image type="content" source="./media/hybrid-how-to-enable-replication-private-endpoints/add-record-set.png" alt-text="Screenshot that shows the Add record set page.":::