fixes headings

Author: davidsmatlak

articles/azure-resource-manager/troubleshooting/error-invalid-template.md

@@ -2,7 +2,7 @@
 title: Invalid template errors
 description: Describes how to resolve invalid template errors when deploying Bicep files or Azure Resource Manager templates (ARM templates).
 ms.topic: troubleshooting
-ms.date: 12/20/2021
+ms.date: 09/12/2022
 ---
 
 # Resolve errors for invalid template
@@ -26,7 +26,7 @@ This error can result from several different types of errors. They usually invol
 
 <a id="syntax-error"></a>
 
-## Solution 1 - syntax error
+## Solution 1: Syntax error
 
 If you receive an error message that indicates the template failed validation, you may have a syntax problem in your template.
 
@@ -56,13 +56,13 @@ When you receive this type of error, review the expression's syntax. To identify
 
 <a id="incorrect-segment-lengths"></a>
 
-## Solution 2 - incorrect segment lengths
+## Solution 2: Incorrect segment lengths
 
 Another invalid template error occurs when the resource name isn't in the correct format. To resolve that error, see [Resolve errors for name and type mismatch](error-invalid-name-segments.md).
 
 <a id="parameter-not-valid"></a>
 
-## Solution 3 - parameter isn't valid
+## Solution 3: Parameter isn't valid
 
 You can specify a parameter's allowed values in a template. During deployment, if you provide a value that isn't an allowed value, you receive a message similar to the following error:
 
@@ -77,13 +77,13 @@ Check the template for the parameter's allowed values, and use an allowed value
 
 <a id="too-many-resource-groups"></a>
 
-## Solution 4 - too many target resource groups
+## Solution 4: Too many target resource groups
 
 You may see this error in earlier deployments because you were limited to five target resource groups in a single deployment. In May 2020, that limit was increased to 800 resource groups. For more information, see how to deploy to multiple resource groups for [Bicep](../bicep/deploy-to-resource-group.md#deploy-to-multiple-resource-groups) or [ARM templates](../templates/deploy-to-resource-group.md#deploy-to-multiple-resource-groups).
 
 <a id="circular-dependency"></a>
 
-## Solution 5 - circular dependency detected
+## Solution 5: Circular dependency detected
 
 You receive this error when resources depend on each other in a way that prevents the deployment from starting. A combination of interdependencies makes two or more resource wait for other resources that are also waiting. For example, resource1 depends on resource3, resource2 depends on resource1, and resource3 depends on resource2. You can usually solve this problem by removing unnecessary dependencies.
 

articles/azure-resource-manager/troubleshooting/error-job-size-exceeded.md

@@ -1,13 +1,13 @@
 ---
 title: Job size exceeded error
-description: Describes how to troubleshoot errors when job size or template are too large for deployments using a Bicep file or Azure Resource Manager template (ARM template).
+description: Describes how to troubleshoot errors for job size exceeded or if the template is too large for deployments using a Bicep file or Azure Resource Manager template (ARM template).
 ms.topic: troubleshooting
-ms.date: 12/20/2021
+ms.date: 09/12/2022
 ---
 
 # Resolve errors for job size exceeded
 
-This article describes how to resolve the `JobSizeExceededException` and `DeploymentJobSizeExceededException` errors. The errors can occur when you deploy a Bicep file or Azure Resource Manager template (ARM template).
+This article describes how to resolve the `JobSizeExceededException` and `DeploymentJobSizeExceededException` errors. The job size exceeded errors can occur when you deploy a Bicep file or Azure Resource Manager template (ARM template).
 
 ## Symptom
 
@@ -29,7 +29,7 @@ Other template limits are:
 - 64 output values
 - 24,576 characters in a template expression
 
-## Solution 1 - use dependencies carefully
+## Solution 1: Use dependencies carefully
 
 # [Bicep](#tab/bicep)
 
@@ -53,7 +53,7 @@ dependsOn: [
 
 ---
 
-## Solution 2 - simplify template
+## Solution 2: Simplify template
 
 # [Bicep](#tab/bicep)
 
@@ -70,7 +70,7 @@ You can set other resources as dependent on the linked template, and [get values
 
 ---
 
-## Solution 3 - reduce name size
+## Solution 3: Reduce name size
 
 # [Bicep](#tab/bicep)
 

articles/azure-resource-manager/troubleshooting/error-parent-resource.md

@@ -2,7 +2,7 @@
 title: Parent resource errors
 description: Describes how to resolve errors when you deploy a resource that's dependent on a parent resource in a Bicep file or Azure Resource Manager template (ARM template).
 ms.topic: troubleshooting
-ms.date: 12/20/2021
+ms.date: 09/12/2022
 ---
 
 # Resolve errors for parent resources
@@ -25,7 +25,7 @@ When one resource is a child to another resource, the parent resource must exist
 # [Bicep](#tab/bicep)
 
 ```bicep
-resource sqlDatabase 'Microsoft.Sql/servers/databases@2021-05-01-preview' = {
+resource sqlDatabase 'Microsoft.Sql/servers/databases@2022-02-01-preview' = {
   name: '${sqlServerName}/${databaseName}'
   ...
 }
@@ -50,7 +50,7 @@ If you deploy the server and the database in the same template, but don't specif
 
 If the parent resource already exists and isn't deployed in the same template, you get the `ParentResourceNotFound` error when Resource Manager can't associate the child resource with a parent. This error might happen when the child resource isn't in the correct format. Or if the child resource is deployed to a resource group that's different than the resource group for parent resource.
 
-## Solution 1 - deployed in same template
+## Solution 1: Deployed in same template
 
 To resolve this error when parent and child resources are deployed in the same template, use a dependency.
 
@@ -59,7 +59,7 @@ To resolve this error when parent and child resources are deployed in the same t
 This example uses a nested child resource within the parent resource and that creates the dependency. The child gets the resource type and API version from the parent resource.
 
 ```bicep
-resource sqlServer 'Microsoft.Sql/servers@2021-05-01-preview' = {
+resource sqlServer 'Microsoft.Sql/servers@2022-02-01-preview' = {
   name: sqlServerName
   properties: {
     ...
@@ -87,7 +87,7 @@ For more information about `dependsOn`, see [Define the order for deploying reso
 
 ---
 
-## Solution 2 - deployed in different templates
+## Solution 2: Deployed in different templates
 
 To resolve this error when the parent resource was deployed in a different template, don't set a dependency. Instead, deploy the child to the same resource group and provide the name of the parent resource.
 
@@ -100,11 +100,11 @@ param location string = resourceGroup().location
 param sqlServerName string
 param databaseName string
 
-resource sqlServer 'Microsoft.Sql/servers@2021-05-01-preview' existing = {
+resource sqlServer 'Microsoft.Sql/servers@2022-02-01-preview' existing = {
   name: sqlServerName
 }
 
-resource sqlDatabase 'Microsoft.Sql/servers/databases@2021-05-01-preview' = {
+resource sqlDatabase 'Microsoft.Sql/servers/databases@2022-02-01-preview' = {
   parent: sqlServer
   name: databaseName
   location: location
@@ -130,7 +130,7 @@ The `name` element uses the names of the parent resource and child resources.
   "resources": [
     {
       "type": "Microsoft.Sql/servers/databases",
-      "apiVersion": "2021-05-01-preview",
+      "apiVersion": "2022-02-01-preview",
       "name": "[concat(parameters('sqlServerName'), '/', parameters('databaseName'))]",
       "location": "[resourceGroup().location]",
       "properties": {