Merge pull request #96918 from tfitzmac/1122headers

shorten headers

Author: PRMerger8

articles/azure-resource-manager/template-tutorial-add-functions.md

@@ -17,7 +17,7 @@ We recommend that you complete the [tutorial about parameters](template-tutorial
 
 You must have Visual Studio Code with the Resource Manager Tools extension, and either Azure PowerShell or Azure CLI. For more information, see [template tools](template-tutorial-create-first-template.md#get-tools).
 
-## Review your template
+## Review template
 
 At the end of the previous tutorial, your template had the following JSON:
 
@@ -65,7 +65,7 @@ az group deployment create \
 
 ---
 
-## Verify the deployment
+## Verify deployment
 
 You can verify the deployment by exploring the resource group from the Azure portal.
 

articles/azure-resource-manager/template-tutorial-add-outputs.md

@@ -17,7 +17,7 @@ We recommend that you complete the [tutorial about variables](template-tutorial-
 
 You must have Visual Studio Code with the Resource Manager Tools extension, and either Azure PowerShell or Azure CLI. For more information, see [template tools](template-tutorial-create-first-template.md#get-tools).
 
-## Review your template
+## Review template
 
 At the end of the previous tutorial, your template had the following JSON:
 
@@ -41,7 +41,7 @@ It uses the [reference](resource-group-template-functions-resource.md#reference)
 
 Finally, it returns the **primaryEndpoints** property from the storage account
 
-## Deploy the template
+## Deploy template
 
 You're ready to deploy the template and look at the returned value.
 

articles/azure-resource-manager/template-tutorial-add-parameters.md

@@ -17,23 +17,23 @@ We recommend that you complete the [tutorial about resources](template-tutorial-
 
 You must have Visual Studio Code with the Resource Manager Tools extension, and either Azure PowerShell or Azure CLI. For more information, see [template tools](template-tutorial-create-first-template.md#get-tools).
 
-## Review your template
+## Review template
 
 At the end of the previous tutorial, your template had the following JSON:
 
 [!code-json[](~/resourcemanager-templates/get-started-with-templates/add-storage/azuredeploy.json)]
 
 You may have noticed that there's a problem with this template. The storage account name is hard-coded. You can only use this template to deploy the same storage account every time. To deploy a storage account with a different name, you would have to create a new template, which obviously isn't a practical way to automate your deployments.
 
-## Make your template reusable
+## Make template reusable
 
 To make your template reusable, let's add a parameter that you can use to pass in a storage account name. The highlighted JSON in the following example shows what changed in your template. The **storageName** parameter is identified as a string. The max length is set to 24 characters to prevent any names that are too long.
 
 Copy the whole file and replace your template with its contents.
 
 [!code-json[](~/resourcemanager-templates/get-started-with-templates/add-name/azuredeploy.json?range=1-26&highlight=4-10,15)]
 
-## Deploy the template
+## Deploy template
 
 Let's deploy the template. The following example deploys the template with Azure CLI or PowerShell. Notice that you provide the storage account name as one of the values in the deployment command. For the storage account name, provide the same name you used in the previous tutorial.
 
@@ -79,7 +79,7 @@ The previous template always deployed a Standard_LRS storage account. You might
 
 The **storageSKU** parameter has a default value. This value is used when a value isn't specified during the deployment. It also has a list of allowed values. These values match the values that are needed to create a storage account. You don't want users of your template to pass in SKUs that don't work.
 
-## Redeploy the template
+## Redeploy template
 
 You're ready to deploy again. Because the default SKU is set to **Standard_LRS**, you don't need to provide a value for that parameter.
 

articles/azure-resource-manager/template-tutorial-add-tags.md

@@ -17,7 +17,7 @@ We recommend that you complete the [tutorial about Quickstart templates](templat
 
 You must have Visual Studio Code with the Resource Manager Tools extension, and either Azure PowerShell or Azure CLI. For more information, see [template tools](template-tutorial-create-first-template.md#get-tools).
 
-## Review your template
+## Review template
 
 Your previous template deployed a storage account, App Service plan, and web app.
 
@@ -33,7 +33,7 @@ The following example highlights the changes to the template. Copy the whole fil
 
 [!code-json[](~/resourcemanager-templates/get-started-with-templates/add-tags/azuredeploy.json?range=1-118&highlight=46-52,64,78,100)]
 
-## Deploy the template
+## Deploy template
 
 It's time to deploy the template and look at the results.
 
@@ -63,7 +63,7 @@ az group deployment create \
 
 ---
 
-## Verify the deployment
+## Verify deployment
 
 You can verify the deployment by exploring the resource group from the Azure portal.
 

articles/azure-resource-manager/template-tutorial-add-variables.md

@@ -17,7 +17,7 @@ We recommend that you complete the [tutorial about functions](template-tutorial-
 
 You must have Visual Studio Code with the Resource Manager Tools extension, and either Azure PowerShell or Azure CLI. For more information, see [template tools](template-tutorial-create-first-template.md#get-tools).
 
-## Review your template
+## Review template
 
 At the end of the previous tutorial, your template had the following JSON:
 
@@ -45,7 +45,7 @@ The **storagePrefix** parameter enables you to pass in a prefix that helps you i
 
 Finally, notice that the storage name is now set to the variable instead of a parameter.
 
-## Deploy the template
+## Deploy template
 
 Let's deploy the template. Deploying this template is easier than the previous templates because you provide just the prefix for the storage name.
 
@@ -74,7 +74,7 @@ az group deployment create \
 
 ---
 
-## Verify the deployment
+## Verify deployment
 
 You can verify the deployment by exploring the resource group from the Azure portal.
 

articles/azure-resource-manager/template-tutorial-export-template.md

@@ -17,7 +17,7 @@ We recommend that you complete the [tutorial about outputs](template-tutorial-ad
 
 You must have Visual Studio Code with the Resource Manager Tools extension, and either Azure PowerShell or Azure CLI. For more information, see [template tools](template-tutorial-create-first-template.md#get-tools).
 
-## Review your template
+## Review template
 
 At the end of the previous tutorial, your template had the following JSON:
 
@@ -44,7 +44,7 @@ This template works well for deploying storage accounts, but you might want to a
 1. Select **Review and create**.
 1. Select **Create**. It takes a few moments to create the resource.
 
-## Export the template
+## Export template
 
 1. Select **Go to resource**.
 
@@ -63,7 +63,7 @@ This template works well for deploying storage accounts, but you might want to a
 > [!IMPORTANT]
 > Typically, the exported template is more verbose than you might want when creating a template. For example, the SKU object in the exported template has five properties. This template works, but you could just use the **name** property. You can start with the exported template, and then modify it as you like to fit your requirements.
 
-## Revise the existing template
+## Revise existing template
 
 The exported template gives you most of the JSON you need, but you need to customize it for your template. Pay particular attention to differences in parameters and variables between your template and the exported template. Obviously, the export process doesn't know the parameters and variables that you've already defined in your template.
 
@@ -73,7 +73,7 @@ Copy the whole file and replace your template with its contents.
 
 [!code-json[](~/resourcemanager-templates/get-started-with-templates/export-template/azuredeploy.json?range=1-77&highlight=28-31,50-69)]
 
-## Deploy the template
+## Deploy template
 
 Use either Azure CLI or Azure PowerShell to deploy a template.
 

articles/azure-resource-manager/template-tutorial-quickstart-template.md

@@ -17,15 +17,15 @@ We recommend that you complete the [tutorial about exported templates](template-
 
 You must have Visual Studio Code with the Resource Manager Tools extension, and either Azure PowerShell or Azure CLI. For more information, see [template tools](template-tutorial-create-first-template.md#get-tools).
 
-## Review your template
+## Review template
 
 At the end of the previous tutorial, your template had the following JSON:
 
 [!code-json[](~/resourcemanager-templates/get-started-with-templates/export-template/azuredeploy.json)]
 
 This template works for deploying storage accounts and app service plans, but you might want to add a website to it. You can use pre-built templates to quickly discover the JSON required for deploying a resource.
 
-## Find a template
+## Find template
 
 1. Open [Azure Quickstart templates](https://azure.microsoft.com/resources/templates/)
 1. In **Search**, enter **deploy linux web app**.
@@ -36,7 +36,7 @@ This template works for deploying storage accounts and app service plans, but yo
 
     ![Resource Manager template quickstart web site](./media/template-tutorial-quickstart-template/resource-manager-template-quickstart-template-web-site.png)
 
-## Revise the existing template
+## Revise existing template
 
 Merge the quickstart template with the existing template:
 
@@ -52,7 +52,7 @@ You'll notice it has an element named **dependsOn** that is set to the app servi
 
 The **serverFarmId** property uses the [resourceId](resource-group-template-functions-resource.md#resourceid) function. This function gets the unique identifier for a resource. In this case, it gets the unique identifier for the app service plan. The web app is associated with one specific app service plan.
 
-## Deploy the template
+## Deploy template
 
 Use either Azure CLI or Azure PowerShell to deploy a template.
 

articles/azure-resource-manager/template-tutorial-use-parameter-file.md

@@ -17,7 +17,7 @@ We recommend that you complete the [tutorial about tags](template-tutorial-add-t
 
 You must have Visual Studio Code with the Resource Manager Tools extension, and either Azure PowerShell or Azure CLI. For more information, see [template tools](template-tutorial-create-first-template.md#get-tools).
 
-## Review your template
+## Review template
 
 Your template has many parameters you can provide during deployment. At the end of the previous tutorial, your template looked like:
 
@@ -41,7 +41,7 @@ Again, create a new file with the following content. Save the file with the name
 
 This file is your parameter file for the production environment. Notice that it uses Standard_GRS for the storage account, names resources with a **contoso** prefix, and sets the **Environment** tag to **Production**. In a real production environment, you would also want to use an app service with a SKU other than free, but we'll continue to use that SKU for this tutorial.
 
-## Deploy the template
+## Deploy template
 
 Use either Azure CLI or Azure PowerShell to deploy the template.
 
@@ -111,7 +111,7 @@ az group deployment create \
 
 ---
 
-## Verify the deployment
+## Verify deployment
 
 You can verify the deployment by exploring the resource groups from the Azure portal.