Acrolynx review fixes.

Stephen Tramer · Stephen Tramer · commit 1425a5f2a8b5 · 2018-11-07T13:51:04.000-08:00
diff --git a/docs-conceptual/azurermps-6.12.0/install-az-ps.md b/docs-conceptual/azurermps-6.12.0/install-az-ps.md
@@ -11,8 +11,7 @@ ms.date: 10/29/2018
 
 # Install Azure PowerShell with PowerShellGet
 
-This article explains the steps to install the Azure PowerShell modules using PowerShellGet. For the preview release of Az,
-no other install methods are supported. 
+This article tells you how to install the Azure PowerShell modules using PowerShellGet. For the preview release of Az, no other install methods are supported. 
 
 ## Requirements
 
@@ -23,8 +22,8 @@ on your machine, run the following command:
 $PSVersionTable.PSVersion
 ```
 
-If you have an outdated version or need to install PowerShell, see [Installing various versions of PowerShell](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell?view=powershell-6) and click on the link for
-your platform.
+If you have an outdated version or need to install PowerShell, see [Installing various versions of PowerShell](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell?view=powershell-6). Install
+information for your platform is linked from that page.
 
 ## Install the Azure PowerShell module
 
@@ -34,8 +33,7 @@ your platform.
 > the `Az` module, `AzureRM` must be uninstalled. For instructions on how to do that, see
 > [Uninstall the Azure PowerShell module (AzureRM)](uninstall-azurerm-ps.md).
 
-To install modules at a global scope, you need elevated privileges to install modules from the PowerShell Gallery. To install Azure PowerShell,
-run the following command in an elevated session ("Run as Administrator" on Windows, or with superuser privileges on macOS or Linux):
+To install modules at a global scope, you need elevated privileges to install modules from the PowerShell Gallery. To install Azure PowerShell, run the following command in an elevated session ("Run as Administrator" on Windows, or with superuser privileges on macOS or Linux):
 
 ```powershell-interactive
 Install-Module -Name Az -AllowClobber
@@ -103,7 +101,7 @@ Get-Module -Name Az -List | select Name,Version
 
 To remove a version of Azure PowerShell, see [Uninstall the Azure PowerShell module](uninstall-azurerm-ps.md).
 
-You can load a specific version of the `Az` module by providing the `-RequiredVersion` argument to `Install-Module` or `Import-Module`:
+You can load a specific version of the `Az` module by using the `-RequiredVersion` argument with `Install-Module` or `Import-Module`:
 
 ```powershell-interactive
 Install-Module -Name Az -RequiredVersion 0.4.0
diff --git a/docs-conceptual/azurermps-6.12.0/migrate-from-azurerm-to-az.md b/docs-conceptual/azurermps-6.12.0/migrate-from-azurerm-to-az.md
@@ -6,32 +6,28 @@ ms.author: sttramer
 manager: carmonm
 ms.devlang: powershell
 ms.topic: conceptual
-ms.date: 11/01/2018
+ms.date: 11/07/2018
 ---
 
 # Migrate from AzureRM to Azure PowerShell Az
 
 The Az module has feature parity with AzureRM, but uses shorter and more consistent cmdlet names.
-This means that scripts written for the AzureRM cmdlets won't automatically work with the new
+Scripts written for the AzureRM cmdlets won't automatically work with the new
 module. To make the transition easier, Az offers tools to allow you to run your existing scripts
 using AzureRM. No migration to a new command set is ever convenient, but this article will help
-you get started on transitioning to Az while minimizing the cost of upgrading so that you can
-take advantage of the features offered in this new module.
-
-Each section of this article outlines a step in the process, and it's recommended that you follow
-them in order unless you've already completed the process outlined in a single step.
+you get started on transitioning to the new module.
 
 ## Ensure your existing scripts work with the latest AzureRM release
 
 This is the most important step! Run your existing scripts, and make sure that they work with the
-_latest_ release of AzureRM (__6.12.0__). If your scripts do not work, make sure to read
+_latest_ release of AzureRM (__6.12.0__). If your scripts don't work, make sure to read
 the [AzureRM migration guide](migration-guide.6.0.0.md).
 
 ## Install the Azure PowerShell Az module
 
-The first step is to install the Az module on your platform. This _does_ require uninstalling
-the AzureRM module. In the following steps you'll learn how to keep running your existing scripts
-and enable compatibility for old cmdlet names.
+The first step is to install the Az module on your platform. To install Az, you need to uninstall AzureRM.
+In the following steps, you'll learn how to keep running your existing scripts and enable compatibility
+for old cmdlet names.
 
 To install the Azure PowerShell Az module, follow these steps:
 
@@ -41,13 +37,13 @@ To install the Azure PowerShell Az module, follow these steps:
 ## <a name="aliases"/>Enable AzureRM alias mode
 
 With AzureRM uninstalled and your scripts working with the latest AzureRM version, now is the time to
-enable the compatibility mode for the Az module. This is done with the command
+enable the compatibility mode for the Az module. Compatibility is enabled with the command:
 
 ```powershell-interactive
 Enable-AzureRmAlias -Scope CurrentUser
 ```
 
-This enables the ability to use old cmdlet names with the `Az` module installed, through aliases. These
+Aliases enable the ability to use old cmdlet names with the `Az` module installed. These
 aliases are written to the user profile for the selected scope. If no user profile exists, one is created.
 
 > [!WARNING]
@@ -60,24 +56,19 @@ Once the alias mode is enabled, run your scripts again to confirm that they stil
 
 ## Change module imports and cmdlet names
 
-In general, the module names have been changed so that `AzureRM` becomes `Az`, and the same for cmdlets.
-For example, the `AzureRM.Compute` module has been renamed to `Az.Compute`. `New-AzureRmVM` has become `New-AzVM`.
-There are some exceptions to this naming change that you should be aware of before doing any renaming:
+In general, the module names have been changed so that `AzureRM` and `Azure` become `Az`, and the same for cmdlets.
+For example, the `AzureRM.Compute` module has been renamed to `Az.Compute`. `New-AzureRmVM` has become `New-AzVM`,
+and `Get-AzureStorageBlob` is now `Get-AzStorageBlob`.
+
+There are exceptions to this naming change that you should be aware of before doing any renaming:
 
 | AzureRM module | Az module |
 |----------------|-----------|
-| Azure.Storage | Az.Storage |
-| Azure.AnalysisServices | Az.AnalysisServices |
 | AzureRM.DataFactories | Az.DataFactory |
 | AzureRM.DataFactoryV2 | Az.DataFactory |
 | AzureRM.RecoveryServices.Backup | Az.RecoveryServices |
 | AzureRM.RecoveryServices.SiteRecovery | Az.RecoveryServices |
 
-In the case of `Azure.Storage` and `Azure.AnalysisServices`, the associated cmdlets have also been renamed
-so that `Azure` is replaced with `Az`. For example, `Get-AzureStorageBlob` has been renamed to `Get-AzStorageBlob`.
-
 ## Summary
 
-By following these steps, you can update all of your existing scripts to use the new module without a lot of pain or difficulty.
-If you have any questions or encountered problems with these steps that made your migration difficult, please comment on this article
-so that we can improve the instructions.
+By following these steps, you can update all of your existing scripts to use the new module. If you have any questions or problems with these steps that made your migration difficult, please comment on this article so that we can improve the instructions.
diff --git a/docs-conceptual/azurermps-6.12.0/new-azureps-module-az.md b/docs-conceptual/azurermps-6.12.0/new-azureps-module-az.md
@@ -1,7 +1,7 @@
 ---
 title: Introducing the Azure PowerShell Az module
 description: Introducing the new Azure PowerShell module Az, the replacement for the AzureRM module.
-ms.date: 10/22/2018
+ms.date: 11/07/2018
 author: sptramer
 ms.author: sttramer
 ms.manager: carmonm
@@ -14,11 +14,12 @@ Starting in November 2018, the Azure PowerShell `Az` module is available for ful
 Az offers shorter commands, improved stability, and supports Windows, macOS, and Linux. Az also offers
 feature parity and an easy migration path from AzureRM.
 
-Az is built on the .NET Standard library, which means that it runs under both PowerShell 5.x on
-Windows and PowerShell Core on any platform. Using .NET Standard allows us to unify the code base of Azure
-PowerShell with minimal impact on users.
+Az uses the .NET Standard library, which means it runs on PowerShell 5.x and PowerShell 6.x.
+Since PowerShell 6.x can run on Linux, macOS, and Windows, that means Az is available for all platforms.
+Using .NET Standard allows us to unify the code base of Azure PowerShell with minimal impact on users.
 
-This is a new module, so the version has been reset. The first stable release will be 1.0.
+Az is a new module, so the version has been reset. The first stable release will be 1.0, but the module
+has feature parity with AzureRm as of November 2018.
 
 ## Upgrade to Az
 
@@ -30,19 +31,17 @@ It's recommended that users upgrade to the new `Az` module. To do so:
 
 ## Migrate existing scripts to Az
 
-Major updates like this can be inconvenient. However, the `Az` module has a compatibility mode to
+Major updates can be inconvenient. However, the `Az` module has a compatibility mode to
 help you use existing scripts while you work on updates to the new syntax. Use the
 `Enable-AzureRmAlias` cmdlet to enable the `AzureRM` compatibility mode. This cmdlet defines
 `AzureRM` cmdlet names as aliases for the new `Az` cmdlet names.
 
-The new cmdlet names have also been designed to be easy to learn. Instead of using `AzureRm` or `Azure` in cmdlet names,
-use `Az`. For most cmdlets, this should be the only change required. For example, the old command `New-AzureRmVm`
-has become `New-AzVm`.
+The new cmdlet names have been designed to be easy to learn. Instead of using `AzureRm` or `Azure`
+in cmdlet names, use `Az`. For example, the old command `New-AzureRmVm` has become `New-AzVm`.
 
 For a full description of the migration process, see [Migrate from AzureRM to Az](migrate-from-azurerm-to-az.md).
 
 ## The future of support for AzureRM
 
-The existing `AzureRM` module will no longer recieve new cmdlets or features when `Az` version 1.0 is released
-in December 2018. However, `AzureRM` is still officially maintained and will get bug fixes. To keep up with the latest
-Azure services and features, you should switch to the `Az` module as soon as possible.
+The existing `AzureRM` module will no longer receive new cmdlets or features when `Az` version 1.0 is released
+in December 2018. However, `AzureRM` is still officially maintained and will get bug fixes. To keep up with the latest Azure services and features, you should switch to the `Az` module.
