Skip to content

Commit 1947f79

Browse files
authored
Merge pull request #79700 from georgewallace/gw_typo#1
fixing typo
2 parents 3aa08e5 + a66fa3f commit 1947f79

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/automation/automation-update-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The following diagram shows a conceptual view of the behavior and data flow with
3333

3434
Update Management can be used to natively onboard machines in multiple subscriptions in the same tenant.
3535

36-
Once a CVE is release, it takes 2-3 hours for the patch to show up for Linux machines for assessment. For Windows machines, it takes 12-15 hours for the patch to show up for assessment after it has been released.
36+
Once a CVE is released, it takes 2-3 hours for the patch to show up for Linux machines for assessment. For Windows machines, it takes 12-15 hours for the patch to show up for assessment after it has been released.
3737

3838
After a computer completes a scan for update compliance, the agent forwards the information in bulk to Azure Monitor logs. On a Windows computer, the compliance scan is run every 12 hours by default.
3939

0 commit comments

Comments
 (0)