Merge pull request #106191 from BethWilke/task106

Fixing alphabetization of word 'graphical'.

Author: v-albemi

articles/automation/automation-child-runbooks.md

@@ -27,15 +27,15 @@ The parameters of a child runbook called inline can be of any data type, includi
 
 Which runbook types can call each other?
 
-* A [PowerShell runbook](automation-runbook-types.md#powershell-runbooks) and a [Graphical runbook](automation-runbook-types.md#graphical-runbooks) can call each other inline, as both are PowerShell-based.
-* A [PowerShell Workflow runbook](automation-runbook-types.md#powershell-workflow-runbooks) and a Graphical PowerShell Workflow runbook can call each other inline, as both are PowerShell Workflow-based.
+* A [PowerShell runbook](automation-runbook-types.md#powershell-runbooks) and a [graphical runbook](automation-runbook-types.md#graphical-runbooks) can call each other inline, as both are PowerShell-based.
+* A [PowerShell Workflow runbook](automation-runbook-types.md#powershell-workflow-runbooks) and a graphical PowerShell Workflow runbook can call each other inline, as both are PowerShell Workflow-based.
 * The PowerShell types and the PowerShell Workflow types can’t call each other inline, and must use **Start-AzAutomationRunbook**.
 
 When does publish order matter?
 
-The publish order of runbooks only matters for PowerShell Workflow and Graphical PowerShell Workflow runbooks.
+The publish order of runbooks only matters for PowerShell Workflow and graphical PowerShell Workflow runbooks.
 
-When your runbook calls a Graphical or PowerShell Workflow child runbook using inline execution, it uses the name of the runbook. The name must start with **.\\** to specify that the script is located in the local directory.
+When your runbook calls a graphical or PowerShell Workflow child runbook using inline execution, it uses the name of the runbook. The name must start with **.\\** to specify that the script is located in the local directory.
 
 ### Example
 

articles/automation/automation-edit-textual-runbook.md

@@ -18,7 +18,7 @@ The textual editor includes a feature to insert code for cmdlets, assets, and ch
 
 Each runbook in Azure Automation has two versions, Draft and Published. You edit the Draft version of the runbook and then publish it so it can be executed. The Published version cannot be edited. For more information, see [Publishing a runbook](manage-runbooks.md#publish-a-runbook).
 
-This article provides detailed steps for performing different functions with this editor. These are not applicable to [Graphical Runbooks](automation-runbook-types.md#graphical-runbooks). To work with these runbooks, see [Graphical authoring in Azure Automation](automation-graphical-authoring-intro.md).
+This article provides detailed steps for performing different functions with this editor. These are not applicable to [graphical runbooks](automation-runbook-types.md#graphical-runbooks). To work with these runbooks, see [Graphical authoring in Azure Automation](automation-graphical-authoring-intro.md).
 
 >[!NOTE]
 >This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](automation-update-azure-modules.md).

articles/automation/automation-first-runbook-graphical.md

@@ -7,7 +7,7 @@ ms.subservice: process-automation
 ms.date: 04/13/2018
 ms.topic: conceptual
 ---
-# My first Graphical runbook
+# My first graphical runbook
 
 > [!div class="op_single_selector"]
 > * [Graphical](automation-first-runbook-graphical.md)
@@ -16,7 +16,7 @@ ms.topic: conceptual
 > * [Python](automation-first-runbook-textual-python2.md)
 > 
 
-This tutorial walks you through the creation of a [Graphical runbook](automation-runbook-types.md#graphical-runbooks) in Azure Automation. Start with a simple runbook that tests and publishes, while learning how to track the status of the runbook job. Then modify the runbook to actually manage Azure resources, in this case starting an Azure virtual machine. Complete the tutorial to make the runbook more robust by adding runbook parameters and conditional links.
+This tutorial walks you through the creation of a [graphical runbook](automation-runbook-types.md#graphical-runbooks) in Azure Automation. Start with a simple runbook that tests and publishes, while learning how to track the status of the runbook job. Then modify the runbook to actually manage Azure resources, in this case starting an Azure virtual machine. Complete the tutorial to make the runbook more robust by adding runbook parameters and conditional links.
 
 >[!NOTE]
 >This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](automation-update-azure-modules.md).
@@ -39,7 +39,7 @@ Start by creating a simple runbook that outputs the text "Hello World".
 2. Select **Runbooks** under **Process Automation** to open the list of runbooks.
 3. Create a new runbook by selecting **Create a runbook**.
 4. Give the runbook the name **MyFirstRunbook-Graphical**.
-5. In this case, you're going to create a [Graphical runbook](automation-graphical-authoring-intro.md). Select **Graphical** for **Runbook type**.<br> ![New runbook](media/automation-first-runbook-graphical/create-new-runbook.png)<br>
+5. In this case, you're going to create a [graphical runbook](automation-graphical-authoring-intro.md). Select **Graphical** for **Runbook type**.<br> ![New runbook](media/automation-first-runbook-graphical/create-new-runbook.png)<br>
 6. Click **Create** to create the runbook and open the graphical editor.
 
 ## Step 2 - Add activities

articles/automation/automation-first-runbook-textual.md

@@ -207,7 +207,7 @@ Your runbook currently starts the VM that you have hardcoded in the runbook. It
 ## Next steps
 
 * For more information on PowerShell, including language reference and learning modules, refer to the [PowerShell Docs](https://docs.microsoft.com/powershell/scripting/overview).
-* To get started with Graphical runbooks, see [My first graphical runbook](automation-first-runbook-graphical.md).
+* To get started with graphical runbooks, see [My first graphical runbook](automation-first-runbook-graphical.md).
 * To get started with PowerShell runbooks, see [My first PowerShell runbook](automation-first-runbook-textual-powershell.md).
 * To learn more about runbook types and their advantages and limitations, see [Azure Automation runbook types](automation-runbook-types.md).
 * For more information on PowerShell script support features, see [Native PowerShell script support in Azure Automation](https://azure.microsoft.com/blog/announcing-powershell-script-support-azure-automation-2/).