Merge pull request #199983 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: huypub

articles/active-directory/verifiable-credentials/decentralized-identifier-overview.md

@@ -108,7 +108,7 @@ There are three primary actors in the verifiable credential solution. In the fol
 
 - **Step 1**, the **user** requests a verifiable credential from an issuer.
 - **Step 2**, the **issuer** of the credential attests that the proof the user provided is accurate and creates a verifiable credential signed with their DID and the user’s DID is the subject.
-- **In Step 3**, the user signs a verifiable presentation (VP) with their DID and sends to the **verifier.** The verifier then validates of the credential by matching with the public key placed in the DPKI.
+- **In Step 3**, the user signs a verifiable presentation (VP) with their DID and sends to the **verifier.** The verifier then validates the credential by matching with the public key placed in the DPKI.
 
 The roles in this scenario are:
 

articles/azure-functions/functions-bindings-storage-blob.md

@@ -146,7 +146,7 @@ Functions 1.x apps automatically have a reference to the extension.
 
 ## host.json settings
 
-This section describes the function app configuration settings available for functions that this binding. These settings only apply when using extension version 5.0.0 and higher. The example host.json file below contains only the version 2.x+ settings for this binding. For more information about function app configuration settings in versions 2.x and later versions, see [host.json reference for Azure Functions](functions-host-json.md).
+This section describes the function app configuration settings available for functions that use this binding. These settings only apply when using extension version 5.0.0 and higher. The example host.json file below contains only the version 2.x+ settings for this binding. For more information about function app configuration settings in versions 2.x and later versions, see [host.json reference for Azure Functions](functions-host-json.md).
 
 > [!NOTE]
 > This section doesn't apply to extension versions before 5.0.0. For those earlier versions, there aren't any function app-wide configuration settings for blobs.

articles/cognitive-services/language-service/question-answering/tutorials/adding-synonyms.md

@@ -79,6 +79,8 @@ As you can see, when `troubleshoot` was not added as a synonym, we got a low con
 
 ## Notes
 * Synonyms can be added in any order. The ordering is not considered in any computational logic.
+* Synonyms can only be added to a project that has at least one question and answer pair.
+* Synonyms can be added only when there is at least one question and answer pair present in a knowledge base.
 * In case of overlapping synonym words between 2 sets of alterations, it may have unexpected results and it is not recommended to use overlapping sets.
 * Special characters are not allowed for synonyms. For hyphenated words like "COVID-19", they are treated the same as "COVID 19", and "space" can be used as a term separator. Following is the list of special characters **not allowed**:
 

articles/container-apps/revisions-manage.md

@@ -120,7 +120,7 @@ As you interact with this example, replace the placeholders surrounded by `<>` w
 
 ## Deactivate
 
-Deactivate revisions that are no longer in use with `az container app revision deactivate`. Deactivation stops all running replicas of a revision.
+Deactivate revisions that are no longer in use with `az containerapp revision deactivate`. Deactivation stops all running replicas of a revision.
 
 # [Bash](#tab/bash)
 

articles/container-registry/TOC.yml

@@ -185,7 +185,7 @@
           items:
           - name: Scan with Microsoft Defender for Cloud
             href: scan-images-defender.md
-          - name: Scan with GitHub actions
+          - name: Scan with GitHub Actions
             href: github-action-scan.md
     - name: Troubleshoot
       expanded: false

articles/cost-management-billing/reservations/reservation-renew.md

@@ -43,7 +43,7 @@ The following conditions are required to renew a reservation:
 
 ## Default renewal settings
 
-By default, the renewal inherits all properties from the expiring reservation. A reservation renewal purchase has the same SKU, region, scope, billing subscription, term, and quantity.
+By default, the renewal inherits all properties except automatic renewal setting from the expiring reservation. A reservation renewal purchase has the same SKU, region, scope, billing subscription, term, and quantity.
 
 However, you can update the renewal reservation purchase quantity to optimize your savings.
 

articles/devops-project/index.yml

@@ -1,7 +1,7 @@
 ### YamlMime:Landing
 
 title: DevOps Starter documentation to deploy to Azure
-summary: DevOps Starter presents a simplified experience where you bring your existing code and Git repository, or choose from one of the sample applications to create a continuous integration (CI) and continuous delivery (CD) pipeline or workflow to Azure. DevOps Starter now supports creating GitHub actions workflows.
+summary: DevOps Starter presents a simplified experience where you bring your existing code and Git repository, or choose from one of the sample applications to create a continuous integration (CI) and continuous delivery (CD) pipeline or workflow to Azure. DevOps Starter now supports creating GitHub Actions workflows.
 
 metadata:
   title: DevOps Starter documentation
@@ -32,7 +32,7 @@ landingContent:
     linkLists:
       - linkListType: quickstart
         links:
-          - text: Node.js using GitHub actions
+          - text: Node.js using GitHub Actions
             url: ./devops-starter-gh-nodejs.md
           - text: .NET
             url: ./azure-devops-project-aspnet-core.md
@@ -54,7 +54,7 @@ landingContent:
     linkLists:
       - linkListType: tutorial
         links:
-          - text: Deploy your app to Azure Web App using GitHub actions
+          - text: Deploy your app to Azure Web App using GitHub Actions
             url: devops-starter-gh-web-app.md
           - text: Bring your own code with GitHub
             url: azure-devops-project-vms.md

articles/governance/blueprints/overview.md

@@ -16,7 +16,7 @@ Just as a blueprint allows an engineer or an architect to sketch a project's des
 Azure Blueprints enables cloud architects and central information technology groups to define a
 repeatable set of Azure resources that implements and adheres to an organization's standards,
 patterns, and requirements. Azure Blueprints makes it possible for development teams to rapidly
-build and stand up new environments with trust they're building within organizational compliance
+build and start up new environments with trust they're building within organizational compliance
 with a set of built-in components, such as networking, to speed up development and delivery.
 
 Blueprints are a declarative way to orchestrate the deployment of various resource templates and

articles/healthcare-apis/fhir/get-started-with-fhir.md

@@ -58,7 +58,7 @@ You can obtain an Azure AD access token using PowerShell, Azure CLI, REST CCI, o
 #### Access using existing tools
 
 - [Postman](../fhir/use-postman.md)
-- [Rest Client](../fhir/using-rest-client.md)
+- [REST Client](../fhir/using-rest-client.md)
 - [cURL](../fhir/using-curl.md)
 
 #### Load data

articles/machine-learning/component-reference/import-data.md

@@ -19,7 +19,7 @@ This article describes a component in Azure Machine Learning designer.
 Use this component to load data into a machine learning pipeline from existing cloud data services. 
 
 > [!Note]
-> All functionality provided by this component can be done by **datastore** and **datasets** in the worksapce landing page. We recommend you use **datastore** and **dataset** which includes additional features like data monitoring. To learn more, see [How to Access Data](../v1/how-to-access-data.md) and [How to Register Datasets](../v1/how-to-create-register-datasets.md) article.
+> All functionality provided by this component can be done by **datastore** and **datasets** in the workspace landing page. We recommend you use **datastore** and **dataset** which includes additional features like data monitoring. To learn more, see [How to Access Data](../v1/how-to-access-data.md) and [How to Register Datasets](../v1/how-to-create-register-datasets.md) article.
 >  After you register a dataset, you can find it in the **Datasets** -> **My Datasets** category in designer interface. This component is reserved for Studio(classic) users to for a familiar experience. 
 >