Merge pull request #106029 from BethWilke/task107

Fixing formatting

Author: Jak-MS

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)

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

@@ -30,23 +30,23 @@ To complete this tutorial, you need:
 
 ## Step 1 - Create new runbook
 
-Start by creating a simple runbook that outputs the text "Hello World".
+Start by creating a simple runbook that outputs the text **Hello World**.
 
 1. In the Azure portal, open your Automation account.
 
    The Automation account page gives you a quick view of the resources in this account. You should already have some assets. Most of those assets are the modules automatically included in a new Automation account. You should also have the Credential asset associated with your subscription.
 
 1. Select **Runbooks** under **Process Automation** to open the list of runbooks.
-1. Create a new runbook by selecting **+ Create a runbook**.
-1. Give the runbook the name "MyFirstRunbook-Workflow".
+1. Create a new runbook by selecting **Create a runbook**.
+1. Give the runbook the name **MyFirstRunbook-Workflow**.
 1. In this case, you're going to create a [PowerShell Workflow runbook](automation-runbook-types.md#powershell-workflow-runbooks). So select **Powershell Workflow** for **Runbook type**.
 1. Click **Create** to create the runbook and open the textual editor.
 
 ## Step 2 - Add code to the runbook
 
-You can either type code directly into the runbook, or you can select cmdlets, runbooks, and assets from the Library control and add them to the runbook with any related parameters. For this walkthrough, type code directly into the runbook.
+You can either type code directly into the runbook, or you can select cmdlets, runbooks, and assets from the Library control and add them to the runbook with any related parameters. For this tutorial, you type code directly into the runbook.
 
-1. Your runbook is currently empty with only the required **workflow** keyword, the name of the runbook, and the braces that encase the entire workflow.
+1. Your runbook is currently empty with only the required **Workflow** keyword, the name of the runbook, and the braces that encase the entire workflow.
 
    ```powershell-interactive
    Workflow MyFirstRunbook-Workflow
@@ -73,9 +73,9 @@ Before you publish the runbook to make it available in production, you should te
 1. Click **Start** to start the test, with testing the only enabled option.
 1. Note that a [runbook job](automation-runbook-execution.md) is created and its status is displayed in the pane.
 
-   The job status starts as Queued, indicating that the job is waiting for a runbook worker in the cloud to become available. The status changes to Starting when a worker claims the job. Finally, the status becomes Running when the runbook actually starts to run.
+   The job status starts as **Queued**, indicating that the job is waiting for a runbook worker in the cloud to become available. The status changes to **Starting** when a worker claims the job. Finally, the status becomes **Running** when the runbook actually starts to run.
 
-1. When the runbook job completes, the Test pane displays its output. In this case, you see "Hello World".
+1. When the runbook job completes, the Test pane displays its output. In this case, you see **Hello World**.
 
    ![Hello World](media/automation-first-runbook-textual/test-output-hello-world.png)
 
@@ -86,8 +86,8 @@ Before you publish the runbook to make it available in production, you should te
 The runbook that you've created is still in Draft mode. You must publish it before you can run it in production. When you publish a runbook, you overwrite the existing Published version with the Draft version. In this case, you don't have a Published version yet because you just created the runbook.
 
 1. Click **Publish** to publish the runbook and then **Yes** when prompted.
-1. Scroll left to view the runbook in the **Runbooks** pane and note that the **Authoring Status** value is set to Published.
-1. Scroll back to the right to view the pane for MyFirstRunbook-Workflow.
+1. Scroll left to view the runbook in the **Runbooks** page and note that the **Authoring Status** field is set to **Published**.
+1. Scroll back to the right to view the page for **MyFirstRunbook-Workflow**.
 
    The options across the top allow you to start the runbook now, schedule a future start time, or create a [webhook](automation-webhooks.md) so that the runbook can be started through an HTTP call.
 
@@ -101,18 +101,18 @@ The runbook that you've created is still in Draft mode. You must publish it befo
 
    ![Job Summary](media/automation-first-runbook-textual/job-pane-status-blade-jobsummary.png)
 
-1. Once the runbook status shows Completed, click **Output**. The Output page is opened, where can see your "Hello World" message.
+1. Once the runbook status shows **Completed**, click **Output**. The Output page is opened, where you can see your **Hello World** message.
 
    ![Job Summary](media/automation-first-runbook-textual/job-pane-status-blade-outputtile.png)
 
 1. Close the Output page.
 
-1. Click **All Logs** to open the Streams pane for the runbook job. you should only see "Hello World" in the output stream. Note that the Streams pane can show other streams for a runbook job, such as verbose and error streams, if the runbook writes to them.
+1. Click **All Logs** to open the Streams pane for the runbook job. You should only see **Hello World** in the output stream. Note that the Streams pane can show other streams for a runbook job, such as verbose and error streams, if the runbook writes to them.
 
    ![Job Summary](media/automation-first-runbook-textual/job-pane-status-blade-alllogstile.png)
 
-1. Close the Streams pane and the Job pane to return to the MyFirstRunbook page.
-1. Click **Jobs** under **Resources** to open the Jobs page for this runbook. This page lists all the jobs created by your runbook. You should only see one job listed, since you have only run the job once.
+1. Close the Streams pane and the Job pane to return to the **MyFirstRunbook** page.
+1. Click **Jobs** under **Resources** to open the Jobs page for this runbook. This page lists all the jobs created by your runbook. You should only see one job listed, since you have run the job only once.
 
    ![Jobs](media/automation-first-runbook-textual/runbook-control-job-tile.png)
 
@@ -125,10 +125,10 @@ You've tested and published your runbook, but so far it doesn't do anything usef
 >[!NOTE]
 >For PowerShell runbooks, **Add-AzAccount** and **Add-AzureRMAccount** are aliases for **Connect-AzAccount**. You can use these cmdlets or you can [update your modules](automation-update-azure-modules.md) in your Automation account to the latest versions. You might need to update your modules even if you have just created a new Automation account.
 
-1. Navigate to the MyFirstRunbook-Workflow page and open the textual editor by clicking **Edit**.
-2. Delete the **Write-Output** line.
+1. Navigate to the **MyFirstRunbook-Workflow** page and open the textual editor by clicking **Edit**.
+2. Delete the `Write-Output` line.
 3. Position the cursor on a blank line between the braces.
-4. Type or copy and paste the following code that handles the authentication with your Automation Run As account.
+4. Type or copy and paste the following code, which handles the authentication with your Automation Run As account.
 
    ```powershell-interactive
    # Ensures you do not inherit an AzContext in your runbook
@@ -148,7 +148,7 @@ You've tested and published your runbook, but so far it doesn't do anything usef
 
 ## Step 6 - Add code to start a virtual machine
 
-Now that your runbook is authenticating to your Azure subscription, you can manage resources. Let's add a command to start a virtual machine. You can pick any VM in your Azure subscription, and for now you're hardcoding that name in the runbook. If you're managing resources across multiple subscriptions, you need to use the *AzContext* parameter with the [Get-AzContext](/powershell/module/az.accounts/get-azcontext) cmdlet.
+Now that your runbook is authenticating to the Azure subscription, you can manage resources. Let's add a command to start a virtual machine. You can pick any VM in your Azure subscription, and for now you're hardcoding that name in the runbook. If you're managing resources across multiple subscriptions, you need to use the *AzContext* parameter with the [Get-AzContext](/powershell/module/az.accounts/get-azcontext) cmdlet.
 
 1. Provide the name and resource group name of the VM to start by entering a call to the [Start-AzVM](https://docs.microsoft.com/powershell/module/Az.Compute/Start-AzVM?view=azps-3.5.0
 ) cmdlet as shown below. 
@@ -173,7 +173,7 @@ Now that your runbook is authenticating to your Azure subscription, you can mana
 
 ## Step 7 - Add an input parameter to the runbook
 
-Your runbook currently starts the VM that you have hardcoded in the runbook. It will be more useful if you can specify the VM when the runbook is started. Add input parameters to the runbook to provide that functionality.
+Your runbook currently starts the VM that you have hardcoded in the runbook. It will be more useful if you can specify the VM when the runbook is started. Let's add input parameters to the runbook to provide that functionality.
 
 1. Add values for *VMName* and *ResourceGroupName* to the runbook, and use the associated variables with the **Start-AzVM** cmdlet as shown below.
 
@@ -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/).