update

Author: mumian

articles/azure-resource-manager/bicep/migrate-blueprint.md

@@ -1,28 +1,30 @@
 ---
-title: Migrate blueprint to deployment stack
-description: Learn how to migrate blueprint to deployment stack
+title: Migrate blueprints to deployment stacks
+description: Learn how to migrate blueprints to deployment stacks.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 10/24/2024
 ---
 
-# Migrate blueprint to deployment stack
+# Migrate blueprints to deployment stacks
 
-This document outlines the steps to re-author your Blueprint definitions and assignments as deployment stacks. Deplomyment stacks are new platform primitives within the `Microsoft.Resources` namespace, bringing Azure Blueprint capabilities into this space. Deployment stacks enable you to deploy ARM templates/Bicep files to a specified target scope.
+This article explains how to convert your Blueprint definitions and assignments into deployment stacks. Deployment stacks are new tools within the `Microsoft.Resources` namespace, bringing Azure Blueprint features into this area. 
 
 ## Migration steps
 
-1. Export the blueprint definitions into the blueprint definition JSON files which include the artifacts of Azure policies, Azure role assignments, and templates. For more information see [Export your blueprint defintion](../../governance/blueprints/how-to/import-export-ps.md#export-your-blueprint-definition).
-2. Convert the blueprint definitio JSON files into a single ARM template or Bicep file to be deployed via deployment stacks with the following considerations:
+1. Export the blueprint definitions into the blueprint definition JSON files which include the artifacts of Azure policies, Azure role assignments, and templates. For more information, see [Export your blueprint definition](../../governance/blueprints/how-to/import-export-ps.md#export-your-blueprint-definition).
+2. Convert the blueprint definition JSON files into a single ARM template or Bicep file to be deployed via deployment stacks with the following considerations:
 
-    - **Role assingments**: Convert any [role assignments](/azure/templates/microsoft.authorization/policyassignments).
-    - **Policies**: Convert any [policy assignments](/azure/templates/microsoft.authorization/policyassignments) into the Bicep (or ARM JSON template) syntax, and then add them to your main template. You can also embedd the [`policyDefinitions`](/azure/templates/microsoft.authorization/policydefinitions) into the JSON template.
-    - **Templates**: Convert any templates into a main template for submission to a deployment stack. You can use [modules](./modules.md) in Bicep, embed templates as nested templates or template links, and optionally use [template specs](./template-specs.md) to store your templates in Azure. Template Specs are not required to leverage deployment stacks.
-    - **Locks**: Deployment stack [DenySettingsMode](./deployment-stacks.md#protect-managed-resources) gives you the ability to block unwanted changes via `DenySettingsMode` (similar to [Blueprint locks](../../governance/blueprints/concepts/resource-locking.md)). You can configure these via Azure CLI or Azure PowerShell. In order to leverage this, you need to corresponding roles to be able to set deny settings. For more information, see [Deployment stacks](./deployment-stacks.md).
+    - **Role assignments**: Convert any [role assignments](/azure/templates/microsoft.authorization/policyassignments).
+    - **Policies**: Convert any [policy assignments](/azure/templates/microsoft.authorization/policyassignments) into the Bicep (or ARM JSON template) syntax, and then add them to your main template. You can also embedded the [`policyDefinitions`](/azure/templates/microsoft.authorization/policydefinitions) into the JSON template.
+    - **Templates**: Convert any templates into a main template for submission to a deployment stack. You can use [modules](./modules.md) in Bicep, embed templates as nested templates or template links, and optionally use [template specs](./template-specs.md) to store your templates in Azure. Template Specs aren't required to use deployment stacks.
+    - **Locks**: Deployment stack [DenySettingsMode](./deployment-stacks.md#protect-managed-resources) gives you the ability to block unwanted changes via `DenySettingsMode` (similar to [Blueprint locks](../../governance/blueprints/concepts/resource-locking.md)). You can configure these via Azure CLI or Azure PowerShell. In order to do this, you need corresponding roles to be able to set deny settings. For more information, see [Deployment stacks](./deployment-stacks.md).
+
+3. You can optionally create template specs for the converted ARM templates or Bicep files. Template specs allow you to store templates and their versions in your Azure environment, simplifying the sharing of the templates across your organization. Deployment stacks enable you to deploy template spec definitions, or ARM templates/Bicep files, to a specified target scope.
 
 ## Sample
 
-The folloing Bicep files is a sample migration file.
+The following Bicep file is a sample migration file.
 
 ```bicep
 targetScope = 'subscription'