edits

Author: GitHubber17

articles/virtual-machines/extensions/dsc-overview.md

@@ -26,19 +26,19 @@ The Azure Linux Agent for Azure virtual machines (VM) and the associated extensi
 The primary use for the Azure Desired State Configuration (DSC) extension for Windows PowerShell is to bootstrap a VM to the
 [Azure Automation State Configuration (DSC) service](../../automation/automation-dsc-overview.md). This service provides [benefits](/powershell/dsc/managing-nodes/metaConfig#pull-service) that include ongoing management of the VM configuration and integration with other operational tools, such as Azure Monitor. You can use the extension to register your VMs to the service and gain a flexible solution that works across Azure subscriptions.
 
-You can run the Azure DSC extension independently of the Automation DSC service, but this method only pushes a configuration to the VM. No ongoing reporting is available, other than locally in the VM. Before you enable the Azure DSC extension, [choose the DSC version](#dsc-versions) that best supports your configuration and implementation goals.
+You can run the Azure DSC extension independently of the Automation DSC service, but this method only pushes a configuration to the VM. No ongoing reporting is available, other than locally in the VM. Before you enable the Azure DSC extension, [review the available DSC versions](#desired-state-configuration-versions), and choose the version that supports your configuration requirements.
 
 This article describes how to use the Azure DSC extension for Automation onboarding, or use it as a tool to assign configurations to VMs with the Azure SDK.
 
 ## Desired State Configuration versions
 
 There are several versions of DSC available for implementation. Before you enable the Azure DSC extension, choose the DSC version that best supports your configuration and business goals.
 
-| **DSC version** | Availability | Description |
+| DSC version | Availability | Description |
 | --- | --- | --- |
-| **DSC 2.0** | General availability | [DSC 2.0](/powershell/azure/dsc/overview?view=dsc-2.0) is supported for use with the Azure Automanage [Machine Configuration](../../governance/machine-configuration/overview.md) feature. The machine configuration feature combines features of the Azure DSC extension handler, Azure Automation State Configuration, and the most commonly requested features from customer feedback. Machine configuration also includes hybrid machine support through [Arc-enabled servers](../../azure-arc/servers/overview.md). |
-| **DSC 1.1** | General availability | If your implementation doesn't use the Azure Automanage machine configuration feature, you should choose DSC 1.1. For more information, see [PSDesiredStateConfiguration v1.1](/powershell/azure/dsc/overview?view=dsc-1.1). |
-| **DSC 3.0** | Public preview | [DSC 3.0 is available in public beta](/powershell/azure/dsc/overview?view=dsc-3.0). This version should be used only with Azure machine configuration, or for nonproduction environments to test migrating away from DSC 1.1. |
+| **DSC 2.0** | General availability | [Desired State Configuration 2.0](/powershell/dsc/overview?view=dsc-2.0&preserve-view=true) is supported for use with the Azure Automanage [Machine Configuration](../../governance/machine-configuration/overview.md) feature. The machine configuration feature combines features of the Azure DSC extension handler, Azure Automation State Configuration, and the most commonly requested features from customer feedback. Machine configuration also includes hybrid machine support through [Arc-enabled servers](../../azure-arc/servers/overview.md). |
+| **DSC 1.1** | General availability | If your implementation doesn't use the Azure Automanage machine configuration feature, you should choose Desired State Configuration 1.1. For more information, see [PSDesiredStateConfiguration v1.1](/powershell/dsc/overview?view=dsc-1.1&preserve-view=true). |
+| **DSC 3.0** | Public preview | [Desired State Configuration 3.0 is available in public beta](/powershell/dsc/overview?view=dsc-3.0&preserve-view=true). This version should be used only with Azure machine configuration, or for nonproduction environments to test migrating away from Desired State Configuration 1.1. |
 
 ## Prerequisites
 
@@ -204,7 +204,7 @@ To set up the Azure DSC extension in the Azure portal, follow these steps:
 
 1. Select **Create** at the bottom of the extension information page.
 
-1. In the Azure portal, configure the following settings for the Azure DSC extension:
+1. Configure the following settings for the Azure DSC extension:
 
    - **Configuration Modules or Script**: This setting is mandatory. (The form isn't updated for the [default configuration script](#default-configuration-script).) Configuration modules and scripts require a .ps1 file that has a configuration script or a .zip file with a .ps1 configuration script at the root. If you use a .zip file, all dependent resources must be included in module folders in the .zip file. You can create the .zip file by using the **Publish-AzureVMDscConfiguration -OutputArchivePath** cmdlet that's included in the Azure PowerShell SDK. The .zip file is uploaded to your user Blob Storage and secured by an SAS token.