Merge pull request #299681 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/app-service/overview-diagnostics.md

@@ -15,7 +15,7 @@ This article explains how to troubleshoot issues with your app in Azure App Serv
 
 Azure App Service diagnostics is an interactive experience to help you troubleshoot your app with no configuration required. App Service diagnostics points out what's wrong and guides you to the right information to more easily and quickly troubleshoot and resolve the problem.
 
-Although this experience is most helpful for problems that occured within the last 24 hours, all the diagnostic graphs are always available for you to analyze.
+Although this experience is most helpful for problems that occurred within the last 24 hours, all the diagnostic graphs are always available for you to analyze.
 
 App Service diagnostics works for not only apps on Windows, but also for apps on built-in or custom containers, [App Service Environments](./environment/intro.md), and [Azure Functions](../azure-functions/functions-overview.md).
 

articles/app-service/tutorial-java-jboss-mysql-app.md

@@ -665,7 +665,7 @@ If you see the error: `The subscription '701ea799-fb46-4407-bb67-9cbcf289f1c7' i
 
 Depending on your subscription and the region you select, you might see the deployment status for Azure Database for MySQL Flexible Server to be `Conflict`, with the following message in Operation details:
 
-`InternalServerError: An unexpected error occured while processing the request.`
+`InternalServerError: An unexpected error occurred while processing the request.`
 
 This error is most likely caused by a limit on your subscription for the region you select. Try choosing a different region for your deployment.
 

articles/app-service/tutorial-java-tomcat-mysql-app.md

@@ -697,7 +697,7 @@ You can ignore the warnings. The Maven Jetty plugin shows the warnings because t
 
 Depending on your subscription and the region you select, you might see the deployment status for Azure Database for MySQL Flexible Server to be `Conflict`, with the following message in Operation details:
 
-`InternalServerError: An unexpected error occured while processing the request.`
+`InternalServerError: An unexpected error occurred while processing the request.`
 
 This error is most likely caused by a limit on your subscription for the region you select. Try choosing a different region for your deployment.
 

articles/azure-resource-manager/templates/syntax.md

@@ -57,7 +57,7 @@ In the `definitions` section of the template, specify the schemas used for valid
 
 ```json
 "definitions": {
-  "<definition-name": {
+  "<definition-name>": {
     "type": "<data-type-of-definition>",
     "allowedValues": [ "<array-of-allowed-values>" ],
     "minValue": <minimum-value-for-int>,
@@ -287,8 +287,8 @@ You define resources with the following structure:
         "<settings-for-the-resource>",
         "copy": [
             {
-                "name": ,
-                "count": ,
+                "name": "<name-of-copy-loop>",
+                "count": <number-of-iterations>,
                 "input": {}
             }
         ]

articles/azure-resource-manager/templates/template-functions-deployment.md

@@ -52,7 +52,7 @@ The following example returns the deployer object.
   "outputs": {
     "developerOutput": {
       "type": "object",
-      "value": "[developer()]"
+      "value": "[deployer()]"
     }
   }
 }

articles/governance/machine-configuration/whats-new/migrating-from-dsc-extension.md

@@ -90,7 +90,7 @@ new solution for new machines.
 The expected steps for migration are:
 
 1. Download and expand the `.zip` package used for the DSC extension.
-1. Examine the DSC configuraiton file to understand the scenario.
+1. Examine the DSC configuration file to understand the scenario.
 1. Make any required changes to the configuration.
 1. Use the machine configuration PowerShell cmdlets to create, test, and publish a new package.
 1. Use machine configuration for future deployments rather than DSC extension.