edit

Author: mumian

articles/azure-resource-manager/templates/export-template-portal.md

@@ -37,7 +37,7 @@ To export one or more resources from a resource group:
 
    :::image type="content" source="./media/export-template-portal/show-template.png" alt-text="Screenshot of the displayed exported template in Azure portal.":::
 
-   **Include parameters** is selected by default.  When selected, all template parameters will be included when the template is generated. If you’d like to author your own parameters, toggle this checkbox to not include them.
+   **Include parameters** is selected by default.  When selected, all template parameters are included when the template is generated. If you’d like to author your own parameters, toggle this checkbox to not include them.
 
 ## Export template from a resource
 
@@ -51,7 +51,7 @@ To export one resource:
 
    :::image type="content" source="./media/export-template-portal/export-single-resource.png" alt-text="Screenshot of exporting a single resource in Azure portal.":::
 
-1. The exported template is displayed, and is available to download and deploy. The template only contains the single resource. **Include parameters** is selected by default.  When selected, all template parameters will be included when the template is generated. If you’d like to author your own parameters, toggle this checkbox to not include them.
+1. The exported template is displayed, and is available to download and deploy. The template only contains the single resource. **Include parameters** is selected by default.  When selected, all template parameters are included when the template is generated. If you’d like to author your own parameters, toggle this checkbox to not include them.
 
 ## Download template before deployment
 

articles/azure-resource-manager/templates/frequently-asked-questions.yml

@@ -40,7 +40,7 @@ sections:
       - question: |
           I missed your presentation at Microsoft Build 2020. Is the presentation available for viewing?
         answer: |
-            Yes, please [watch it anytime](https://mybuild.microsoft.com/sessions/82984db4-37a4-4ed3-bf8b-13298841ed18?source=sessions).
+            Yes, [watch it anytime](https://mybuild.microsoft.com/sessions/82984db4-37a4-4ed3-bf8b-13298841ed18?source=sessions).
 
       - question: |
           Where can I get more information about the new features you announced at Build?
@@ -80,7 +80,7 @@ sections:
         answer: |
             We recommend running the [ARM test toolkit](https://github.com/azure/arm-ttk) and the [what-if operation](./deploy-what-if.md) on your templates before deploying them. The test toolkit checks whether your template uses best practices. It provides warnings when it identifies changes that could improve how you've implemented your template.
 
-            The what-if operation shows the changes your template will make to your environment. You can see unintended changes before they're deployed. What-if also returns any errors it can detect during preflight validation. For example, if your template contains a syntactical error, it returns that error. It also returns any errors it can determine about the final state of the deployed resources. For example, if your template deploys a storage account with a name that is already in use, what-if returns that error.
+            The what-if operation shows the changes your template makes to your environment. You can see unintended changes before they're deployed. What-if also returns any errors it can detect during preflight validation. For example, if your template contains a syntactical error, it returns that error. It also returns any errors it can determine about the final state of the deployed resources. For example, if your template deploys a storage account with a name that is already in use, what-if returns that error.
 
       - question: |
           Where can I find information about the properties that are available for each resource type?
@@ -101,7 +101,7 @@ sections:
 
       - question: |
           Is there a plan to support creating templates in YAML?
-        answer:   Currently, there's no plan to support YAML. We believe the new template language will offer a solution that is easier to use than YAML or JSON.
+        answer:   Currently, there's no plan to support YAML. We believe the new template language offers a solution that is easier to use than YAML or JSON.
 
       - question: |
           Can I still write templates in JSON after the new template language has been released?
@@ -116,7 +116,7 @@ sections:
     questions:
       - question: |
           How are template specs and Azure Blueprints related?
-        answer:   Azure Blueprints will use template specs in its implementation by replacing the `blueprint definition` resource with a `template spec` resource. We'll provide a migration path to convert the blueprint definition into a template spec, but the blueprint definition APIs will still be supported. There are no changes to the `blueprint assignment` resource. Blueprints will remain a user-experience to compose a governed environment in Azure.
+        answer:   Azure Blueprints will use template specs in its implementation by replacing the `blueprint definition` resource with a `template spec` resource. We provide a migration path to convert the blueprint definition into a template spec, but the blueprint definition APIs will still be supported. There are no changes to the `blueprint assignment` resource. Blueprints remain a user-experience to compose a governed environment in Azure.
 
       - question: |
           Do template specs replace linked templates?
@@ -144,7 +144,7 @@ sections:
   - name: Preview changes before deployment
     questions:
       - question: |
-          Can I preview the changes that will happen before deploying a template?
+          Can I preview the changes that happen before deploying a template?
         answer: |
             Yes, use the [what-if feature](./deploy-what-if.md). It evaluates the current state of your environment and compares it to the state that will exist after deployment. You can examine the summarized changes to make sure the template doesn't have any unexpected results.
 

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

@@ -10,7 +10,7 @@ ms.date: 03/20/2024
 
 To deploy a resource through an Azure Resource Manager template (ARM template), you add a resource declaration. Use the `resources` array in a JSON template.
 
-[languageVersion 2.0](./syntax.md#languageversion-20) makes a list of enhancements to ARM JSON templates, such as changing the resources declaration from an array to an object. The majority of the samples shown in this article still use `resources` array.  For languageVersion 2.0 specific information, see [Use symbolic name](#use-symbolic-name).
+[languageVersion 2.0](./syntax.md#languageversion-20) makes a list of enhancements to ARM JSON templates, such as changing the resources declaration from an array to an object. Most the samples shown in this article still use `resources` array.  For languageVersion 2.0 specific information, see [Use symbolic name](#use-symbolic-name).
 
 
 
@@ -21,7 +21,7 @@ To deploy a resource through an Azure Resource Manager template (ARM template),
 > [!TIP]
 > We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [resource declaration](../bicep/resource-declaration.md).
 
-You are limited to 800 resources in a template. For more information, see [Template limits](./best-practices.md#template-limits).
+You're limited to 800 resources in a template. For more information, see [Template limits](./best-practices.md#template-limits).
 
 ## Set resource type and version
 
@@ -207,7 +207,7 @@ Symbolic names are case-sensitive. The allowed characters for symbolic names are
 }
 ```
 
-The [reference](./template-functions-resource.md#reference) function can use a resource's symbolic name, as shown in the preceding example. The reference function can no longer use a resource's name, for example, `reference(parameters('storageAccountName'))` is not allowed.
+The [reference](./template-functions-resource.md#reference) function can use a resource's symbolic name, as shown in the preceding example. The reference function can no longer use a resource's name, for example, `reference(parameters('storageAccountName'))` isn't allowed.
 
 If [Deployments resource](/azure/templates/microsoft.resources/deployments?tabs=json) is used in a symbolic-name deployment, use apiVersion `2020-09-01` or later.