Fixing build errors

Author: BethWilke

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

@@ -112,7 +112,7 @@ The runbook that you have created is still in Draft mode. It needs to be publish
 
 You've tested and published your runbook, but so far it doesn't do anything useful. You want to have it manage Azure resources. To do this, the runbook must be able to authenticate using the Run As account that was automatically created when you created your Automation account.
 
-As shown in the example below, the Run As connection is made with the [Connect-AzAccount](https://docs.microsoft.com/en-us/powershell/module/az.accounts/connect-azaccount?view=azps-3.5.0) cmdlet. If you are managing resources across multiple subscriptions, you need to use the *AzContext* parameter along with [Get-AzContext](https://docs.microsoft.com/powershell/module/Az.Accounts/Get-AzContext?view=azps-3.5.0).
+As shown in the example below, the Run As connection is made with the [Connect-AzAccount](https://docs.microsoft.com/powershell/module/az.accounts/connect-azaccount?view=azps-3.5.0) cmdlet. If you are managing resources across multiple subscriptions, you need to use the *AzContext* parameter along with [Get-AzContext](https://docs.microsoft.com/powershell/module/Az.Accounts/Get-AzContext?view=azps-3.5.0).
 
 > [!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.

articles/automation/automation-webhooks.md

@@ -52,7 +52,7 @@ There's no configuration of the webhook required to support the *WebhookData* pa
 
 If you specify a value for *WebhookData* at webhook creation, it is overridden when the webhook starts the runbook with the data from the client POST request. This happens even if the application does not include any data in the request body. 
 
-If you start a runbook that defines *WebhookData* using a mechanism other than a webhook, you can provide a value for *WebhookData* that the runbook recognizes. This value should be an object with the same [properties](#details-of-a-webhook) as the *WebhookData* parameter so that the runbook can work with it just as it works with actual *WebhookData* objects passed by a webhook.
+If you start a runbook that defines *WebhookData* using a mechanism other than a webhook, you can provide a value for *WebhookData* that the runbook recognizes. This value should be an object with the same [properties](#webhook-properties) as the *WebhookData* parameter so that the runbook can work with it just as it works with actual *WebhookData* objects passed by a webhook.
 
 For example, if you are starting the following runbook from the Azure portal and want to pass some sample webhook data for testing, you must pass the data in JSON in the user interface.
 

articles/automation/runbook-input-parameters.md

@@ -266,7 +266,7 @@ You can create a [webhook](automation-webhooks.md) for your runbook and configur
 
 ![Create webhook and assign parameters](media/automation-runbook-input-parameters/automation-08-createwebhookandassignparameters.png)
 
-When you execute a runbook by using a webhook, the predefined input parameter *[WebhookData](automation-webhooks.md#details-of-a-webhook)* is sent, along with the input parameters that you define. 
+When you execute a runbook by using a webhook, the predefined input parameter *[WebhookData](automation-webhooks.md)* is sent, along with the input parameters that you define. 
 
 ![WebhookData parameter](media/automation-runbook-input-parameters/automation-09-webhook-data-parameters.png)