fixing broken bookmarks

Author: paulth1

articles/automation/automation-solution-vm-management-config.md

@@ -120,7 +120,7 @@ When you run the **AutoStop_CreateAlert_Parent** runbook, it verifies that the t
 
 ### To target the autostop action to a list of VMs
 
-1. Create a new [Schedule](shared-resources/schedules.md#creating-a-schedule) and link it to the **AutoStop_CreateAlert_Parent** runbook, adding a comma-separated list of VM names to the `VMList` parameter.
+1. Create a new [Schedule](shared-resources/schedules.md#create-a-schedule) and link it to the **AutoStop_CreateAlert_Parent** runbook, adding a comma-separated list of VM names to the `VMList` parameter.
 
 2. Optionally, if you want to exclude some VMs from the auto shutdown, you can add a comma-separated list of VM names to the `External_ExcludeVMNames` variable.
 

articles/automation/shared-resources/schedules.md

@@ -46,7 +46,7 @@ You can create a new schedule for runbooks in the Azure portal or with PowerShel
 
 1. In the Azure portal, from your Automation account, select **Schedules** under the section **Shared Resources** on the left.
 1. Select **Add a schedule** at the top of the page.
-1. On the New schedule pane, enter a name and optionally enter a description for the new schedule.
+1. On the **New schedule** pane, enter a name and optionally enter a description for the new schedule.
 1. Select whether the schedule runs one time or on a reoccurring schedule by selecting **Once** or **Recurring**. If you select **Once**, specify a start time and then select **Create**. If you select **Recurring**, specify a start time. For **Recur every**, select how often you want the runbook to repeat. Select by hour, day, week, or month.
     1. If you select **Week**, the days of the week are presented for you to choose from. Select as many days as you want. The first run of your schedule will happen on the first day selected after the start time. For example, to choose a weekend schedule, select Saturday and Sunday.
 
@@ -119,7 +119,7 @@ A runbook can be linked to multiple schedules, and a schedule can have multiple
 1. In the Azure portal, from your automation account, select **Runbooks** under **Process Automation**.
 1. Select the name of the runbook to schedule.
 1. If the runbook isn't currently linked to a schedule, you're offered the option to create a new schedule or link to an existing schedule.
-1. If the runbook has parameters, you can select the option **Modify run settings (Default:Azure)** and the Parameters pane appears. You can enter parameter information here.
+1. If the runbook has parameters, you can select the option **Modify run settings (Default:Azure)** and the **Parameters** pane appears. You can enter parameter information here.
 
 ### Link a schedule to a runbook with PowerShell
 

articles/data-factory/how-to-schedule-azure-ssis-integration-runtime.md

@@ -348,7 +348,7 @@ The following section provides steps for creating a PowerShell runbook. The scri
 
 ## Create schedules for your runbook to start/stop Azure-SSIS IR
 
-In the previous section, you have created your Azure Automation runbook that can either start or stop Azure-SSIS IR. In this section, you will create two schedules for your runbook. When configuring the first schedule, you specify **START** for **OPERATION**. Similarly, when configuring the second one, you specify **STOP** for **OPERATION**. For detailed steps to create schedules, see [Create a schedule](../automation/shared-resources/schedules.md#creating-a-schedule) article.
+In the previous section, you have created your Azure Automation runbook that can either start or stop Azure-SSIS IR. In this section, you will create two schedules for your runbook. When configuring the first schedule, you specify **START** for **OPERATION**. Similarly, when configuring the second one, you specify **STOP** for **OPERATION**. For detailed steps to create schedules, see [Create a schedule](../automation/shared-resources/schedules.md#create-a-schedule) article.
 
 1. In **Runbook** window, select **Schedules**, and select **+ Add a schedule** on the toolbar. 
 

articles/lab-services/start-machines-use-automation-runbooks.md

@@ -130,7 +130,7 @@ While ($current -le 10) {
 ```
 
 ## Create a schedule
-To have this script execute daily, [create a schedule](../automation/shared-resources/schedules.md#creating-a-schedule) in the automation account. Once the schedule is created, [link it to the runbook](../automation/shared-resources/schedules.md#linking-a-schedule-to-a-runbook). 
+To have this script execute daily, [create a schedule](../automation/shared-resources/schedules.md#create-a-schedule) in the automation account. Once the schedule is created, [link it to the runbook](../automation/shared-resources/schedules.md#link-a-schedule-to-a-runbook). 
 
 In a large-scale situation where there are multiple subscriptions with multiple labs, store the parameter information in a file for different labs and pass the file to the script instead of the individual parameters. The script would need to be modified but the core execution would be the same. While this sample uses the Azure Automation to execute the PowerShell script, there are other options like using a task in a Build/Release pipeline.