rollback

Author: mumian

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

@@ -10,7 +10,7 @@ ms.custom: devx-track-bicep
 
 A `using` or a `using none` declaration must be present in all Bicep parameters files.
 
-A Bicep parameter file typically uses a `using` statement to tie the file to a [Bicep file](./file.md), a [JSON Azure Resource Manager template (ARM template)](../templates/syntax.md), a [Bicep module](./modules.md), or a [template spec](./template-specs.md). This linkage allows the Bicep language server and compiler to validate the parameter file-checking for correct names, types, and required values based on the template’s inputs.
+A Bicep parameter file typically uses a `using` statement to tie the file to a [Bicep file](./file.md), a [JSON Azure Resource Manager template (ARM template)](../templates/syntax.md), a [Bicep module](./modules.md), or a [template spec](./template-specs.md). This linkage allows the Bicep language server and compiler to validate the parameter file-checking for correct names, types, and required values based on the template's inputs.
 
 In contrast, the `using none` statement explicitly indicates that the parameter file isn't tied to any particular template at compile time. This means the parameters aren't validated against a specific template and are instead intended for more general use-such as being consumed by external tools or serving as shared, reusable parameter sets.
 

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

@@ -17,7 +17,7 @@ Once you're ready to see how Bicep can help simplify and accelerate your deploym
 
 ## Get started
 
-Learn provides free access to resources that can help you apply concepts in Azure. If you're new to Bicep, one way to get started is by reviewing the following Learn modules. You'll learn how Bicep makes it easier to define how your Azure resources should be configured and deployed in a way that's automated and repeatable. You’ll deploy several Azure resources to see how Bicep works.
+Learn provides free access to resources that can help you apply concepts in Azure. If you're new to Bicep, one way to get started is by reviewing the following Learn modules. You'll learn how Bicep makes it easier to define how your Azure resources should be configured and deployed in a way that's automated and repeatable. You'll deploy several Azure resources to see how Bicep works.
 
 [<img src="media/learn-bicep/build-first-bicep-file.svg" width="101" height="120" alt="The badge for the Build your first Bicep file module." role="presentation"></img>](/training/modules/build-first-bicep-template/)
 

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

@@ -102,7 +102,7 @@ Markdown-formatted text can be used for the description text.
 
 ### onlyIfNotExists
 
-By default, when a Bicep deployment runs, Azure Resource Manager (ARM) creates the resource if it doesn’t exist or updates it if it does. If an existing resource has properties that differ from your template, ARM might attempt to update it-or fail if updates aren’t permitted.
+By default, when a Bicep deployment runs, Azure Resource Manager (ARM) creates the resource if it doesn't exist or updates it if it does. If an existing resource has properties that differ from your template, ARM might attempt to update it-or fail if updates aren't permitted.
 
 Starting with Bicep version v0.38.3, the `@onlyIfNotExists()` decorator instructs ARM to create the resource only if it does not already exist. If a resource with the resource ID is found, ARM skips creation and leaves the existing resource unchanged.
 

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

@@ -14,7 +14,7 @@ Resource Manager resolves variables before starting the deployment operations. W
 
 ## Define variables
 
-A variable can't have the same name as a parameter, module, or resource. You can add one or more decorators for each variable. For more information, see Use [decorators](#use-decorators). 
+A variable can't have the same name as a parameter, module, or resource. You can add one or more decorators for each variable. For more information, see Use [decorators](#use-decorators).
 
 ### Untyped variables
 
@@ -84,7 +84,7 @@ Starting with [Bicep CLI version 0.36.X](https://github.com/Azure/bicep/releases
 - **Error detection**: The Bicep compiler validates that assigned values match the declared type, catching errors early.
 - **Code clarity**: Explicit types make it clear what kind of data a variable holds.
 - **Intellisense support**: Tools like Visual Studio Code provide better autocompletion and validation for typed variables.
-- **Refactoring safety**: Ensures that changes to variable assignments don’t inadvertently break type expectations.
+- **Refactoring safety**: Ensures that changes to variable assignments don't inadvertently break type expectations.
 
 To define a typed variable, use the `var` keyword followed by the variable name, the type, and the assigned value:
 
@@ -246,4 +246,3 @@ output instanceCount int = environmentSettings[environmentName].instanceCount
 
 - To learn about the available properties for variables, see [Understand the structure and syntax of Bicep files](file.md).
 - To learn about using loop syntax, see [Iterative loops in Bicep](loops.md).
-

articles/azure-resource-manager/management/relocate-initiate.md

@@ -43,7 +43,7 @@ You should create a relocation plan that addresses service capacity and high-lev
 
 - *Know cost factors.* Relocation has a cost. Moving data and using services isn't free. To minimize cost, you should move data once and avoid duplicating services or environments for extended periods of time. A hidden cost you might not consider comes from suppliers, partners, or third-party technical support. You might need their help to relocate a workload, and they typically charge a fee.
 
-    The pricing for certain Azure services can differ based on the region. Therefore, it’s crucial to review the costs associated with each region before initiating a relocation project. If you’re currently utilizing Azure Reservations in your source region, consider [transferring them to your destination region](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations). Also, don’t forget to account for the [Azure network bandwidth costs](https://azure.microsoft.com/pricing/details/bandwidth) associated with data transfers between regions during the relocation process.
+    The pricing for certain Azure services can differ based on the region. Therefore, it's crucial to review the costs associated with each region before initiating a relocation project. If you're currently utilizing Azure Reservations in your source region, consider [transferring them to your destination region](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations). Also, don't forget to account for the [Azure network bandwidth costs](https://azure.microsoft.com/pricing/details/bandwidth) associated with data transfers between regions during the relocation process.
 
 ## Next step
 

articles/azure-resource-manager/management/relocate-migrate.md

@@ -31,7 +31,7 @@ Before starting the workload relocation, you need to prepare the target region.
 
 **Create new SSL/TLS certificates if needed.** You need to create new SSL/TLS certificates (X.509) for any new domain name. These certificates enable public-private key encryption and secure network communication (HTTPS). Use Azure Key Vault to create or import X.509 certificates. For more information, see [Azure Key Vault certificates](/azure/key-vault/certificates/about-certificates) and [Certificate creation methods](/azure/key-vault/certificates/create-certificate)
 
-**Relocate Azure Key Vault.** You should relocate Azure Key Vault before moving your workload. You should have one key vault per application environment, and your key vault shouldn’t share secrets across regions to ensure confidentiality. You might need to create a new key vault in the new target region to align with this guidance.
+**Relocate Azure Key Vault.** You should relocate Azure Key Vault before moving your workload. You should have one key vault per application environment, and your key vault shouldn't share secrets across regions to ensure confidentiality. You might need to create a new key vault in the new target region to align with this guidance.
 
 **Create a new Log Analytics workspace.** You should have a separate Log Analytics workspace for each region. Create a new workspace in the target region. Since can't move a Log Analytics Workspace to another region, you need to create a new Log Analytics workspace in the target region. There are two options to preserve the data in the original workspace. You can keep the current workspace until you don't need the data, treating the data as read-only. You can also export the workspace data to a storage account in the new target Azure region.
 

articles/azure-resource-manager/management/resource-name-rules.md

@@ -87,8 +87,8 @@ In the following tables, the term alphanumeric refers to:
 > [!div class="mx-tableFixed"]
 > | Entity | Scope | Length | Valid Characters |
 > | --- | --- | --- | --- |
-> | configurationStores\* | global | 5-50 | Alphanumerics and hyphens<br><br>Can’t contain a sequence of more than two hyphens.<br><br>Can’t start with or end with a hyphen. |
-> | configurationStores / replicas | configurationStore | 1-50<br><br>The combined length of the configurationStore name and the replica name can’t exceed 60 characters.| Only alphanumerics are valid. |
+> | configurationStores\* | global | 5-50 | Alphanumerics and hyphens<br><br>Can't contain a sequence of more than two hyphens.<br><br>Can't start with or end with a hyphen. |
+> | configurationStores / replicas | configurationStore | 1-50<br><br>The combined length of the configurationStore name and the replica name can't exceed 60 characters.| Only alphanumerics are valid. |
 
 \* {storeName}-{replicaName} needs to be globally unique.
 

articles/azure-resource-manager/templates/definitions.md

@@ -119,7 +119,7 @@ The following example would accept `{"foo": "string", "bar": 1}`, but reject `{"
 }
 ```
 
-All properties are required unless the property’s type definition has the ["nullable": true](#nullable-constraint) constraint. To make both properties in the preceding example optional, it would look like:
+All properties are required unless the property's type definition has the ["nullable": true](#nullable-constraint) constraint. To make both properties in the preceding example optional, it would look like:
 
 ```json
 "definitions": {

articles/azure-resource-manager/templates/parameters.md

@@ -208,7 +208,7 @@ The following example would accept `{"foo": "string", "bar": 1}`, but reject `{"
 }
 ```
 
-All properties are required unless the property’s [type definition](./definitions.md) has the ["nullable": true](#nullable-constraint) constraint. To make both properties in the preceding example optional, it would look like:
+All properties are required unless the property's [type definition](./definitions.md) has the ["nullable": true](#nullable-constraint) constraint. To make both properties in the preceding example optional, it would look like:
 
 ```json
 "parameters": {