acrolinx

Author: mumian

articles/azure-resource-manager/bicep/linter-rule-prefer-unquoted-property-names.md

@@ -14,13 +14,13 @@ In Bicep, quotes are optionally allowed when the object property keys contain nu
 
 ## Linter rule code
 
-Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings:
+To customize rule settings, use the following value in the [Bicep configuration file](bicep-config-linter.md).
 
 `prefer-unquoted-property-names`
 
 ## Solution
 
-Quotes are not required in following code:
+Quotes aren't required in following code:
 
 ```bicep
 var obj = {
@@ -55,8 +55,6 @@ var x3 = obj.myProp
 
 Optionally, you can use **Quick Fix** to fix the issues:
 
-linter-rule-prefer-unquoted-property-names-quick-fix
-
 :::image type="content" source="./media/linter-rule-prefer-unquoted-property-names/linter-rule-prefer-unquoted-property-names-quick-fix.png" alt-text="The screenshot of Prefer unquoted property names quick fix.":::
 
 ## Next steps

articles/azure-resource-manager/bicep/linter-rule-use-stable-vm-image.md

@@ -16,7 +16,7 @@ Virtual machines shouldn't use preview images. This rule checks the following pr
 
 ## Linter rule code
 
-Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings:
+To customize rule settings, use the following value in the [Bicep configuration file](bicep-config-linter.md)
 
 `use-stable-vm-image`
 
@@ -42,7 +42,7 @@ resource vm 'Microsoft.Compute/virtualMachines@2024-03-01' = {
 }
 ```
 
-You can fix it by using an image that does not contain the string `preview` in the imageReference.
+You can fix it by using an image that doesn't contain the string `preview` in the imageReference.
 
 ```bicep
 param location string = resourceGroup().location

articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md

@@ -9,29 +9,29 @@ ms.custom: devx-track-bicep
 
 # Quickstart: Create Bicep files with Visual Studio
 
-This quickstart guides you through the steps to create a [Bicep file](overview.md) with Visual Studio. You'll create a storage account and a virtual network. You'll also learn how the Bicep extension simplifies development by providing type safety, syntax validation, and autocompletion.
+This quickstart guides you through the steps to create a [Bicep file](overview.md) with Visual Studio. You create a storage account and a virtual network. You also learn how the Bicep extension simplifies development by providing type safety, syntax validation, and autocompletion.
 
-Similar authoring experience is also supported in Visual Studio Code.  See [Quickstart: Create Bicep files with Visual Studio Code](./quickstart-create-bicep-use-visual-studio-code.md).
+Similar authoring experience is also supported in Visual Studio Code. See [Quickstart: Create Bicep files with Visual Studio Code](./quickstart-create-bicep-use-visual-studio-code.md).
 
 ## Prerequisites
 
 - Azure Subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn) before you begin.
-- Visual Studio version 17.3.0 preview 3 or newer.  See [Visual Studio Preview](https://visualstudio.microsoft.com/vs/preview/).
-- Visual Studio Bicep extension.  See [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
+- Visual Studio version 17.3.0 preview 3 or newer. See [Visual Studio Preview](https://visualstudio.microsoft.com/vs/preview/).
+- Visual Studio Bicep extension. See [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
 - Bicep file deployment requires either the latest [Azure CLI](/cli/azure/) or the latest [Azure PowerShell module](/powershell/azure/new-azureps-module-az).
 
 ## Add resource snippet
 
 Launch Visual Studio and create a new file named **main.bicep**.
 
-Visual Studio with the Bicep extension simplifies development by providing pre-defined snippets. In this quickstart, you'll add a snippet that creates a virtual network.
+Visual Studio with the Bicep extension simplifies development by providing predefined snippets. In this quickstart, you add a snippet that creates a virtual network.
 
 In *main.bicep*, type **vnet**. Select **res-vnet** from the list, and then press **[TAB]** or **[ENTER]**.
 
 :::image type="content" source="./media/quickstart-create-bicep-use-visual-studio/add-snippet.png" alt-text="Screenshot of adding snippet for virtual network.":::
 
 > [!TIP]
-> If you don't see those intellisense options in Visual Studio, make sure you've installed the Bicep extension as specified in [Prerequisites](#prerequisites). If you have installed the extension, give the Bicep language service some time to start after opening your Bicep file. It usually starts quickly, but you will not have intellisense options until it starts.
+> If you don't see those intellisense options in Visual Studio, make sure you've installed the Bicep extension as specified in [Prerequisites](#prerequisites). If you have installed the extension, give the Bicep language service some time to start after opening your Bicep file. It usually starts quickly, but you won't have intellisense options until it starts.
 
 Your Bicep file now contains the following code:
 
@@ -73,7 +73,7 @@ Notice **location** has a red curly underline. This indicates a problem. Hover y
 
 ## Add parameters
 
-Now, we'll add two parameters for the storage account name and the location. At the top of file, add:
+Now, we add two parameters for the storage account name and the location. At the top of file, add:
 
 ```bicep
 param storageName
@@ -89,7 +89,7 @@ You have the following parameter:
 param storageName string
 ```
 
-This parameter works fine, but storage accounts have limits on the length of the name. The name must have at least 3 characters and no more than 24 characters. You can specify those requirements by adding decorators to the parameter.
+This parameter works fine, but storage accounts have limits on the length of the name. The name must have at least three characters and no more than 24 characters. You can specify those requirements by adding decorators to the parameter.
 
 Add a line above the parameter, and type **@**. You see the available decorators. Notice there are decorators for both **minLength** and **maxLength**.
 
@@ -122,9 +122,9 @@ param location string = resourceGroup().location
 
 ## Add resource
 
-Instead of using a snippet to define the storage account, we'll use intellisense to set the values. Intellisense makes this step much easier than having to manually type the values.
+Instead of using a snippet to define the storage account, we use intellisense to set the values. Intellisense makes this step easier than having to manually type the values.
 
-To define a resource, use the `resource` keyword.  Below your virtual network, type **resource exampleStorage**:
+To define a resource, use the `resource` keyword. Below your virtual network, type **resource exampleStorage**:
 
 ```bicep
 resource exampleStorage
@@ -208,7 +208,7 @@ For more information about the Bicep syntax, see [Bicep structure](./file.md).
 
 ## Deploy the Bicep file
 
-Bicep file deployment can't be done from Visual Studio yet.  You can deploy the Bicep file by using Azure CLI or Azure PowerShell:
+Bicep file deployment can't be done from Visual Studio yet. You can deploy the Bicep file by using Azure CLI or Azure PowerShell:
 
 # [CLI](#tab/CLI)