Skip to content

Commit 87b8fd4

Browse files
committed
Spelling Fixes
1 parent 47d3bd4 commit 87b8fd4

11 files changed

+11
-11
lines changed

articles/automanage/virtual-machines-custom-profile.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ The `location` value is the region where you would like to store this custom con
157157
The `azureSecurityBaselineAssignmentType` is the audit mode that you can choose for the Azure server security baseline. Your options are
158158

159159
* ApplyAndAutoCorrect : This setting applies the Azure security baseline through the Guest Configuration extension, and if any setting within the baseline drifts, we'll auto-remediate the setting so it stays compliant.
160-
* ApplyAndMonitor : This setting applies the Azure security baseline through the Guest Configuration extention when you first assign this profile to each machine. After it's applied, the Guest Configuration service will monitor the server baseline and report any drift from the desired state. However, it will not auto-remdiate.
160+
* ApplyAndMonitor : This setting applies the Azure security baseline through the Guest Configuration extension when you first assign this profile to each machine. After it's applied, the Guest Configuration service will monitor the server baseline and report any drift from the desired state. However, it will not auto-remediate.
161161
* Audit : This setting installs the Azure security baseline using the Guest Configuration extension. You're able to see where your machine is out of compliance with the baseline, but noncompliance isn't automatically remediated.
162162

163163
The `LogAnalytics/UseAma` value is where you can specify to use Azure Monitor Agent or not.

articles/automation/automation-create-alert-triggered-runbook.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ You can use automation runbooks with three alert types:
3434
> [!NOTE]
3535
> The common alert schema standardizes the consumption experience for alert notifications in Azure. Historically, the three alert types in Azure (metric, log, and activity log) have had their own email templates, webhook schemas, etc. To learn more, see [Common alert schema](/azure/azure-monitor/alerts/alerts-common-schema).
3636
37-
When an alert calls a runbook, the actual call is an HTTP POST request to the webhook. The body of the POST request contains a JSON-formated object that has useful properties that are related to the alert. The following table lists links to the payload schema for each alert type:
37+
When an alert calls a runbook, the actual call is an HTTP POST request to the webhook. The body of the POST request contains a JSON-formatted object that has useful properties that are related to the alert. The following table lists links to the payload schema for each alert type:
3838

3939
|Alert |Description|Payload schema |
4040
|---------|---------|---------|

articles/automation/automation-hrw-run-runbooks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ There are two ways to use the Managed Identities in Hybrid Runbook Worker script
268268
> [!NOTE]
269269
> You can find the client Id of the user-assigned managed identity in the Azure portal.
270270
271-
> :::image type="content" source="./media/automation-hrw-run-runbooks/managed-identities-client-id-inline.png" alt-text="Screenshot of client id in Managed Identites." lightbox="./media/automation-hrw-run-runbooks/managed-identities-client-id-expanded.png":::
271+
> :::image type="content" source="./media/automation-hrw-run-runbooks/managed-identities-client-id-inline.png" alt-text="Screenshot of client id in Managed Identities." lightbox="./media/automation-hrw-run-runbooks/managed-identities-client-id-expanded.png":::
272272
273273
---
274274

articles/automation/automation-webhooks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ Consider the following strategies:
145145
146146
1. Click the copy icon or press <kbd>Ctrl + C</kbd> copy the URL of the webhook. Then save the URL to a secure location.
147147
148-
:::image type="content" source="media/automation-webhooks/create-new-webhook.png" alt-text="Creaye webhook page with URL highlighted.":::
148+
:::image type="content" source="media/automation-webhooks/create-new-webhook.png" alt-text="Create webhook page with URL highlighted.":::
149149
150150
> [!IMPORTANT]
151151
> Once you create the webhook, you cannot retrieve the URL again. Make sure you copy and record it as above.

articles/automation/change-tracking/manage-change-tracking-monitoring-agent.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ To remove change tracking with Azure Monitoring Agent from a virtual machine, fo
162162
1. In the Virtual Machines page, under **Settings**, select **Extensions + applications**.
163163
1. In the **VM |Extensions + applications** page, under **Extensions** tab, select **MicrosoftAzureChangeTrackingAndInventoryChangeTracking-Windows/Linux**.
164164

165-
:::image type="content" source="media/manage-change-tracking-monitoring-agent/uninstall-extensions-inline.png" alt-text="Screenshort of selecting the extension for a VM that is already disassociated from the DCR." lightbox="media/manage-change-tracking-monitoring-agent/uninstall-extensions-expanded.png":::
165+
:::image type="content" source="media/manage-change-tracking-monitoring-agent/uninstall-extensions-inline.png" alt-text="Screenshot of selecting the extension for a VM that is already disassociated from the DCR." lightbox="media/manage-change-tracking-monitoring-agent/uninstall-extensions-expanded.png":::
166166

167167
1. Select **Uninstall**.
168168

articles/automation/context-switching.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ While you may not come across an issue if you don't follow these recommendations
5757
`The subscription named <subscription name> cannot be found.`
5858

5959
```error
60-
Get-AzVM : The client '<clientid>' with object id '<objectid>' does not have authorization to perform action 'Microsoft.Compute/virtualMachines/read' over scope '/subscriptions/<subcriptionIdOfSubscriptionWichDoesntContainTheVM>/resourceGroups/REsourceGroupName/providers/Microsoft.Compute/virtualMachines/VMName '.
60+
Get-AzVM : The client '<clientid>' with object id '<objectid>' does not have authorization to perform action 'Microsoft.Compute/virtualMachines/read' over scope '/subscriptions/<subscriptionIdOfSubscriptionWhichDoesntContainTheVM>/resourceGroups/REsourceGroupName/providers/Microsoft.Compute/virtualMachines/VMName '.
6161
ErrorCode: AuthorizationFailed
6262
StatusCode: 403
6363
ReasonPhrase: Forbidden Operation

articles/automation/migrate-run-as-accounts-managed-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,7 @@ foreach ($ResourceGroup in $ResourceGroups)
186186

187187
:::image type="content" source="./media/migrate-run-as-account-managed-identity/activity-parameter-configuration.png" alt-text="Screenshot that shows examining the parameters used by a cmdlet.":::
188188

189-
For use with the Run As account, the cmdlet uses the `ServicePrinicipalCertificate` parameter set to `ApplicationId`. `CertificateThumbprint` will be from `RunAsAccountConnection`.
189+
For use with the Run As account, the cmdlet uses the `ServicePrincipalCertificate` parameter set to `ApplicationId`. `CertificateThumbprint` will be from `RunAsAccountConnection`.
190190

191191
:::image type="content" source="./media/migrate-run-as-account-managed-identity/parameter-sets-inline.png" alt-text="Screenshot that shows parameter sets." lightbox="./media/migrate-run-as-account-managed-identity/parameter-sets-expanded.png":::
192192

articles/automation/python-3-packages.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ def make_temp_dir():
167167
return destdir
168168

169169
def import_package_with_dependencies (packagename):
170-
# download package with all depeendencies
170+
# download package with all dependencies
171171
download_dir = make_temp_dir()
172172
pip.main(['download', '-d', download_dir, packagename])
173173
for file in os.listdir(download_dir):

articles/automation/troubleshoot/runbooks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -290,7 +290,7 @@ The runbook isn't using the correct context when running. This may be because th
290290
You may see errors like this one:
291291

292292
```error
293-
Get-AzVM : The client '<client-id>' with object id '<object-id> does not have authorization to perform action 'Microsoft.Compute/virtualMachines/read' over scope '/subscriptions/<subcriptionIdOfSubscriptionWichDoesntContainTheVM>/resourceGroups/REsourceGroupName/providers/Microsoft.Compute/virtualMachines/VMName '.
293+
Get-AzVM : The client '<client-id>' with object id '<object-id> does not have authorization to perform action 'Microsoft.Compute/virtualMachines/read' over scope '/subscriptions/<subscriptionIdOfSubscriptionWhichDoesntContainTheVM>/resourceGroups/REsourceGroupName/providers/Microsoft.Compute/virtualMachines/VMName '.
294294
ErrorCode: AuthorizationFailed
295295
StatusCode: 403
296296
ReasonPhrase: Forbidden Operation

articles/automation/tutorial-configure-servers-desired-state.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ $importAzAutomationDscConfigurationSplat = @{
9393
SourcePath = 'C:\DscConfigs\TestConfig.ps1'
9494
ResourceGroupName = 'MyResourceGroup'
9595
AutomationAccountName = 'myAutomationAccount'
96-
Published = $ture
96+
Published = $true
9797
}
9898
Import-AzAutomationDscConfiguration @importAzAutomationDscConfigurationSplat
9999
```

0 commit comments

Comments
 (0)