edit

Author: mumian

articles/azure-resource-manager/bicep/bicep-functions-deployment.md

@@ -47,7 +47,7 @@ When deploying a local Bicep file to a resource group, the function returns the
 }
 ```
 
-When you deploy to an Azure subscription, management group, or tenant, the return object includes a `location` property. The `location` property is not included when deploying a local Bicep file. The format is:
+When you deploy to an Azure subscription, management group, or tenant, the return object includes a `location` property. The `location` property isn't included when deploying a local Bicep file. The format is:
 
 ```json
 {

articles/azure-resource-manager/bicep/bicep-functions-parameters-file.md

@@ -8,7 +8,7 @@ ms.date: 03/20/2024
 
 # Parameters file function for Bicep
 
-Bicep provides a function called `readEnvironmentVariable()` that allows you to retrieve values from environment variables. It also offers the flexibility to set a default value if the environment variable does not exist. This function can only be used in the `.bicepparam` files. For more information, see [Bicep parameters file](./parameter-files.md).
+Bicep provides a function called `readEnvironmentVariable()` that allows you to retrieve values from environment variables. It also offers the flexibility to set a default value if the environment variable doesn't exist. This function can only be used in the `.bicepparam` files. For more information, see [Bicep parameters file](./parameter-files.md).
 
 ## getSecret
 
@@ -26,7 +26,7 @@ param secureUserName = getSecret('exampleSubscription', 'exampleResourceGroup',
 param securePassword = getSecret('exampleSubscription', 'exampleResourceGroup', 'exampleKeyVault', 'exampleSecretPassword')
 ```
 
-You'll get an error if you use this function with string interpolation.
+You get an error if you use this function with string interpolation.
 
 A [namespace qualifier](bicep-functions.md#namespaces-for-functions) (`az`) can be used, but it's optional, because the function is available from the _default_ Azure Namespace.
 
@@ -46,15 +46,15 @@ The value for the secret.
 
 ### Example
 
-The following `.bicepparam` file has a `securePassword` parameter that will have the latest value of the _\<secretName\>_ secret.
+The following `.bicepparam` file has a `securePassword` parameter that has the latest value of the _\<secretName\>_ secret.
 
 ```bicep
 using './main.bicep'
 
 param securePassword = getSecret('exampleSubscription', 'exampleResourceGroup', 'exampleKeyVault', 'exampleSecretPassword')
 ```
 
-The following `.bicepparam` file has a `securePassword` parameter that will have the value of the _\<secretName\>_ secret, but it's pinned to a specific _\<secretValue\>_.
+The following `.bicepparam` file has a `securePassword` parameter that has the value of the _\<secretName\>_ secret, but it's pinned to a specific _\<secretValue\>_.
 
 ```bicep
 using './main.bicep'
@@ -75,7 +75,7 @@ Namespace: [sys](bicep-functions.md#namespaces-for-functions).
 | Parameter | Required | Type | Description |
 |:--- |:--- |:--- |:--- |
 | variableName | Yes | string | The name of the variable. |
-| defaultValue | No | string | A default string value to be used if the environment variable does not exist. |
+| defaultValue | No | string | A default string value to be used if the environment variable doesn't exist. |
 
 ### Return value
 

articles/azure-resource-manager/bicep/bicep-functions-resource.md

@@ -500,7 +500,7 @@ Returns an object representing a resource's runtime state.
 
 Namespace: [az](bicep-functions.md#namespaces-for-functions).
 
-The Bicep files provide access to the reference function, although it is typically unnecessary. Instead, it is recommended to use the symbolic name of the resource. The reference function can only be used within the `properties` object of a resource and cannot be employed for top-level properties like `name` or `location`. The same generally applies to references using the symbolic name. However, for properties such as `name`, it is possible to generate a template without utilizing the reference function. Sufficient information about the resource name is known to directly emit the name. It is referred to as compile-time properties. Bicep validation can identify any incorrect usage of the symbolic name.
+The Bicep files provide access to the reference function, although it's typically unnecessary. Instead, it's recommended to use the symbolic name of the resource. The reference function can only be used within the `properties` object of a resource and can't be employed for top-level properties like `name` or `location`. The same generally applies to references using the symbolic name. However, for properties such as `name`, it's possible to generate a template without utilizing the reference function. Sufficient information about the resource name is known to directly emit the name. It's referred to as compile-time properties. Bicep validation can identify any incorrect usage of the symbolic name.
 
 The following example deploys a storage account. The first two outputs give you the same results.
 
@@ -586,7 +586,7 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' existing
 output storageID string = storageAccount.id
 ```
 
-For more information, see the [JSON template resourceId function](../templates/template-functions-resource.md#resourceid)
+For more information, see the [JSON template resourceId function](../templates/template-functions-resource.md#resourceid).
 
 ## subscriptionResourceId
 

articles/azure-resource-manager/bicep/deploy-vscode.md

@@ -1,5 +1,5 @@
 ---
-title: Deploy Bicep files with visual Studio Code
+title: Deploy Bicep files with Visual Studio Code
 description: Deploy Bicep files from Visual Studio Code.
 ms.topic: conceptual
 ms.custom: devx-track-bicep

articles/azure-resource-manager/bicep/installation-troubleshoot.md

@@ -67,17 +67,17 @@ See [User and Workspace Settings](https://code.visualstudio.com/docs/getstarted/
 
 ## Visual Studio Code error
 
-If you see the following error message popup in VSCode:
+If you see the following error message popup in Visual Studio Code:
 
 ```error
 The Bicep server crashed 5 times in the last 3 minutes. The server will not be restarted.
 ```
 
-From VSCode, open the **Output** view in the pane at the bottom of the screen, and then select **Bicep**:
+From VS Code, open the **Output** view in the pane at the bottom of the screen, and then select **Bicep**:
 
   :::image type="content" source="./media/installation-troubleshoot/visual-studio-code-output-pane-bicep.png" alt-text="Visual Studio Code output pane":::
 
-If you see the following output in the pane, and you are using Bicep CLI **version 0.4.1124** or later, check whether you have added the `dotnetAcquisitionExtension.existingDotnetPath` configuration option to VSCode. See [.NET runtime error](#net-runtime-error). If this configuration option is present, remove it and restart VSCode.
+If you see the following output in the pane, and you're using Bicep CLI **version 0.4.1124** or later, check whether you have added the `dotnetAcquisitionExtension.existingDotnetPath` configuration option to VS Code. See [.NET runtime error](#net-runtime-error). If this configuration option is present, remove it and restart VS Code.
 
   ```error
   It was not possible to find any compatible framework version.

articles/azure-resource-manager/bicep/linter-rule-admin-username-should-not-be-literal.md

@@ -1,12 +1,12 @@
 ---
-title: Linter rule - admin user name should not be literal
-description: Linter rule - admin user name should not be a literal
+title: Linter rule - admin user name shouldn't be literal
+description: Linter rule - admin user name shouldn't be a literal
 ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 03/20/2024
 ---
 
-# Linter rule - admin user name should not be literal
+# Linter rule - admin user name shouldn't be literal
 
 This rule finds when an admin user name is set to a literal value.
 

articles/azure-resource-manager/bicep/linter-rule-artifacts-parameters.md

@@ -34,7 +34,7 @@ param _artifactsLocation string = deployment().properties.templateLink.uri
 ...
 ```
 
-The next example fails this test because `_artifactsLocation` must be either `deployment().properties.templateLink.uri` or a raw URL when the default value is provided, and the default value of `_artifactsLocationSasToken` is not an empty string.
+The next example fails this test because `_artifactsLocation` must be either `deployment().properties.templateLink.uri` or a raw URL when the default value is provided, and the default value of `_artifactsLocationSasToken` isn't an empty string.
 
 ```bicep
 @description('The base URI where artifacts required by this template are located including a trailing \'/\'')

articles/azure-resource-manager/bicep/linter-rule-explicit-values-for-loc-params.md

@@ -1,6 +1,6 @@
 ---
 title: Linter rule - use explicit values for module location parameters
-description: Linter rule - use explicit values for module location parameters
+description: Linter rule - use explicit values for module location parameters.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 03/20/2024
@@ -24,7 +24,7 @@ A parameter that defaults to a resource group's or deployment's location is conv
 
 ### Examples
 
-The following example fails this test. Module `m1`'s parameter `location` isn't assigned an explicit value, so it will default to `resourceGroup().location`, as specified in *module1.bicep*. But using the resource group location may not be the intended behavior, since other resources in *main.bicep* might be created in a different location than the resource group's location.
+The following example fails this test. Module `m1`'s parameter `location` isn't assigned an explicit value, so it defaults to `resourceGroup().location`, as specified in *module1.bicep*. But using the resource group location may not be the intended behavior, since other resources in *main.bicep* might be created in a different location than the resource group's location.
 
 *main.bicep*:
 

articles/azure-resource-manager/bicep/linter-rule-max-variables.md

@@ -8,7 +8,7 @@ ms.date: 03/20/2024
 
 # Linter rule - max variables
 
-This rule checks that the number of variables does not exceed the [ARM template limits](../templates/best-practices.md#template-limits).
+This rule checks that the number of variables doesn't exceed the [ARM template limits](../templates/best-practices.md#template-limits).
 
 ## Linter rule code
 

articles/azure-resource-manager/bicep/linter-rule-no-unnecessary-dependson.md

@@ -71,7 +71,7 @@ resource webApplication 'Microsoft.Web/sites@2022-03-01' = {
 
 Use **Quick Fix** to remove the unnecessary dependsOn entry.
 
-:::image type="content" source="./media/linter-rule-no-unnecessary-dependson/linter-rule-no-unnecessary-dependson-quick-fix.png" alt-text="The screenshot of No unnecessary dependson linterfule with quick fix.":::
+:::image type="content" source="./media/linter-rule-no-unnecessary-dependson/linter-rule-no-unnecessary-dependson-quick-fix.png" alt-text="The screenshot of No unnecessary dependson linter rule with quick fix.":::
 
 ## Next steps