Update

Author: mumian

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

@@ -20,16 +20,16 @@ Similar authoring experience is also supported in Visual Studio Code. See [Quick
 - 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).
 
-> [!INFO]
-> To make all diagnostics generated by Bicep (Errors, Warnings, and Informational messages) are correctly surfaced as native MSBuild diagnostics, configure `BicepTreatInfoAsWarnings` in your project file. For example: 
+> [!NOTE]
+> To make all diagnostics generated by Bicep (Errors, Warnings, and Informational messages) are correctly surfaced as native MSBuild diagnostics, configure `BicepTreatInfoAsWarnings` in your project file. For example:
 > 
 > ```xml
-><Project Sdk="Microsoft.Build.NoTargets">
->  <PropertyGroup>
->    <TargetFramework>net472</TargetFramework>
->    <BicepTreatInfoAsWarnings>true</BicepTreatInfoAsWarnings>
->  </PropertyGroup>
-></Project>
+> <Project Sdk="Microsoft.Build.NoTargets">
+>   <PropertyGroup>
+>     <TargetFramework>net472</TargetFramework>
+>     <BicepTreatInfoAsWarnings>true</BicepTreatInfoAsWarnings>
+>   </PropertyGroup>
+> </Project>
 > ```
 
 ## Add resource snippet