updates

Author: georgewallace

articles/automation/automation-runbook-gallery.md

@@ -6,15 +6,15 @@ ms.service: automation
 ms.subservice: process-automation
 author: georgewallace
 ms.author: gwallace
-ms.date: 03/11/2019
+ms.date: 03/12/2019
 ms.topic: conceptual
 manager: carmonm
 ---
 # Runbook and module galleries for Azure Automation
 
 Rather than creating your own runbooks and modules in Azure Automation, you can access scenarios that have already been built by Microsoft and the community.
 
-You can get runbooks from the [Runbook Gallery](#runbooks-in-runbook-gallery) and modules from the [PowerShell Gallery](#modules-in-powerShell-gallery).  You can also contribute to the community by sharing scenarios that you develop, see [Adding a runbook to the gallery](automation-runbook-gallery.md#adding-a-runbook-to-the-runbook-gallery)
+You can get [PowerShell runbooks](#runbooks-in-runbook-gallery) and [modules](#modules-in-powerShell-gallery) from the PowerShell Gallery and [Python runbooks](#python-runbooks) from the Script Center Gallery. You can also contribute to the community by sharing scenarios that you develop, see [Adding a runbook to the gallery](#adding-a-runbook-to-the-runbook-gallery)
 
 ## Runbooks in PowerShell Gallery
 
@@ -25,7 +25,7 @@ You can only import directly from the PowerShell Gallery using the Azure portal.
 > [!NOTE]
 > You should validate the contents of any runbooks that you get from the PowerShell Gallery and use extreme caution in installing and running them in a production environment.
 
-### To import a runbook from the Runbook Gallery with the Azure portal
+### To import a PowerShell runbook from the Runbook Gallery with the Azure portal
 
 1. In the Azure portal, open your Automation account.
 2. Under **Process Automation**, click on **Runbooks gallery**
@@ -42,30 +42,12 @@ You can only import directly from the PowerShell Gallery using the Azure portal.
 7. Optionally, change the name of the runbook and then click **OK** to import the runbook.
 8. The runbook appears on the **Runbooks** tab for the Automation Account.
 
-### Adding a runbook to the runbook gallery
-
-Microsoft encourages you to add runbooks to the PowerShell Gallery that you think would be useful to other customers.  You can add a runbook by [uploading it to the PowerShell Gallery](/powershell/gallery/how-to/publishing-packages/publishing-a-package) taking into account the following details.
-
-* You must specify *Windows Azure* for the **Category** and *Automation* for the **Subcategory** for the runbook to be displayed in the wizard.  
-* The upload must be a single `.ps1` or `.graphrunbook` file.  If the runbook requires any modules, child runbooks, or assets, then you should list those items in the description of the submission and in the comments section of the runbook.  If you have a scenario requiring multiple runbooks, then upload each separately and list the names of the related runbooks in each of their descriptions. Make sure that you use the same tags so that they show up in the same category. A user will have to read the description to know that other runbooks are required the scenario to work.
-* Add the tag "GraphicalPS" if you're publishing a **Graphical runbook** (not a Graphical Workflow).
-* Insert either a PowerShell or PowerShell Workflow code snippet into the description using **Insert code section** icon.
-* The Summary for the upload is displayed in the Runbook Gallery results so you should provide detailed information that helps a user identify the functionality of the runbook.
-* You should assign one to three of the following Tags to the upload.  The runbook is listed in the wizard under the categories that match its tags.  Any tags not on this list are ignored by the wizard. If you don’t specify any matching tags, the runbook is listed under the Other category.
-  
-  * Backup
-  * Capacity Management
-  * Change Control
-  * Compliance
-  * Dev / Test Environments
-  * Disaster Recovery
-  * Monitoring
-  * Patching
-  * Provisioning
-  * Remediation
-  * VM Lifecycle Management
-
-* Automation updates the Gallery once an hour, so you won’t see your contributions immediately.
+### Adding a PowerShell runbook to the gallery
+
+Microsoft encourages you to add runbooks to the PowerShell Gallery that you think would be useful to other customers. The PowerShell Gallery accepts PowerShell modules and PowerShell scripts. You can add a runbook by [uploading it to the PowerShell Gallery](/powershell/gallery/how-to/publishing-packages/publishing-a-package).
+
+> [!NOTE]
+> Graphical runbooks are not supported in PowerShell Gallery.
 
 ## Modules in PowerShell Gallery
 
@@ -95,7 +77,7 @@ PowerShell modules contain cmdlets that you can use in your runbooks, and existi
 6. To install the module directly into Azure Automation, click the **Import** button.
 7. When you click the Import button, on the **Import** pane, you see the module name that you're about to import. If all the dependencies are installed, the **OK** button is activated. If you're missing dependencies, you need to import those dependencies before you can import this module.
 8. On the **Import** page, click **OK** to import the module. While Azure Automation imports a module to your account, it extracts metadata about the module and the cmdlets. This action may take a couple of minutes since each activity needs to be extracted.
-9.  You receive an initial notification that the module is being deployed and another notification when it has completed.
+9. You receive an initial notification that the module is being deployed and another notification when it has completed.
 10. After the module is imported, you can see the available activities. You can use its resources in your runbooks and Desired State Configuration.
 
 > [!NOTE]