Fixing tasks 170689, 1707369

Author: BethWilke

articles/automation/python-packages.md

@@ -26,11 +26,11 @@ Once a package has been imported, it's listed on the Python 2 packages page in y
 
 ## Import packages with dependencies
 
-Azure automation doesn't resolve dependencies for python packages during the import process. There are two ways to import a package with all its dependencies. Only one of the following steps needs to be used to import the packages into your Automation account.
+Azure automation doesn't resolve dependencies for Python packages during the import process. There are two ways to import a package with all its dependencies. Only one of the following steps needs to be used to import the packages into your Automation account.
 
 ### Manually download
 
-On a Windows 64-bit machine with [python2.7](https://www.python.org/downloads/release/latest/python2) and [pip](https://pip.pypa.io/en/stable/) installed, run the following command to download a package and all its dependencies:
+On a Windows 64-bit machine with [Python2.7](https://www.python.org/downloads/release/latest/python2) and [pip](https://pip.pypa.io/en/stable/) installed, run the following command to download a package and all its dependencies:
 
 ```cmd
 C:\Python27\Scripts\pip2.7.exe download -d <output dir> <package name>
@@ -40,7 +40,7 @@ Once the packages are downloaded, you can import them into your automation accou
 
 ### Runbook
 
-Import the python runbook [Import Python 2 packages from pypi into Azure Automation account](https://gallery.technet.microsoft.com/scriptcenter/Import-Python-2-packages-57f7d509) from the gallery into your Automation account. Make sure the Run Settings are set to **Azure** and start the runbook with the parameters. The runbook requires a Run As account for the Automation account to work. For each parameter make sure you start it with the switch as seen in the following list and image:
+ To obtain a runbook, [import Python 2 packages from pypi into Azure Automation account](https://gallery.technet.microsoft.com/scriptcenter/Import-Python-2-packages-57f7d509) from the gallery into your Automation account. Make sure the Run Settings are set to **Azure** and start the runbook with the parameters. The runbook requires a Run As account for the Automation account to work. For each parameter make sure you start it with the switch as seen in the following list and image:
 
 * -s \<subscriptionId\>
 * -g \<resourceGroup\>
@@ -79,7 +79,7 @@ for group in groups:
 
 ## Develop and test runbooks offline
 
-To develop and test your Python 2 runbooks offline, you can use the [Azure Automation python emulated assets](https://github.com/azureautomation/python_emulated_assets) module on GitHub. This module allows you to reference your shared resources such as credentials, variables, connections, and certificates.
+To develop and test your Python 2 runbooks offline, you can use the [Azure Automation Python emulated assets](https://github.com/azureautomation/python_emulated_assets) module on GitHub. This module allows you to reference your shared resources such as credentials, variables, connections, and certificates.
 
 ## Next steps
 

articles/automation/shared-resources/modules.md

@@ -16,8 +16,9 @@ Azure Automation allows you to import PowerShell modules to enable cmdlets in ru
 
 * [Azure PowerShell Az.Automation](/powershell/azure/new-azureps-module-az?view=azps-1.1.0)
 * [Azure PowerShell AzureRM.Automation](https://docs.microsoft.com/powershell/module/azurerm.automation/?view=azurermps-6.13.0)
-* Internal `Orchestrator.AssetManagement.Cmdlets` module for the Log Analytics agent for Windows
 * Other PowerShell modules
+* Internal `Orchestrator.AssetManagement.Cmdlets` module
+* Python 2 modules
 * Custom modules that you create 
 
 When you create an Automation account, Azure Automation imports some modules by default. See [Default modules](#default-modules).
@@ -91,9 +92,13 @@ Note that the internal cmdlets differ in naming from the Az and AzureRM cmdlets.
 
 We recommend that you use Az or AzureRM cmdlets for manipulating Azure Automation resources outside the context of a runbook. 
 
-## Module supporting Get-AutomationPSCredential
+## Orchestrator.AssetManagement.Cmdlets module
 
-The `Get-AutomationPSCredential` cmdlet is part of the module `Orchestrator.AssetManagement.Cmdlets`. This cmdlet returns a `PSCredential` object, which is expected by most PowerShell cmdlets that work with credentials. To find out more about the use of credentials in Azure Automation, see [Credential assets in Azure Automation](credentials.md).
+Azure Automation supports the internal `Orchestrator.AssetManagement.Cmdlets` module for the Log Analytics agent for Windows, installed by default. The `Get-AutomationPSCredential` cmdlet in this module is commonly used in runbooks to retrieve a `PSCredential` object, which is expected by most PowerShell cmdlets that work with credentials. To find out more about the use of credentials in Azure Automation, see [Credential assets in Azure Automation](credentials.md).
+
+## Python modules
+
+You can create Python 2 runbooks in Azure Automation. For Python module information, see [Manage Python 2 packages in Azure Automation](../python-packages.md).
 
 ## Migrating to Az modules
 
@@ -112,7 +117,7 @@ Importing an Az module into your Automation account doesn't automatically import
 * When a runbook invokes a cmdlet from a module
 * When a runbook imports the module explicitly with the [Import-Module](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/import-module?view=powershell-7) cmdlet
 * When a runbook imports another dependent module
-    
+
 #### Testing for your runbooks and DSC configurations prior to module migration
 
 Be sure to test all runbooks and DSC configurations carefully in a separate Automation account before migrating to the Az modules.