AWS systems-manager documentation change
Summary
Modified link text to 'using a Quick Setup patch policy' to align with other documentation references
Security assessment
The change improves consistency in documentation phrasing. It does not introduce or modify security-related content, nor does it address a specific security issue.
Diff
diff --git a/systems-manager/latest/userguide/patch-manager.md b/systems-manager/latest/userguide/patch-manager.md index 258f9e320..b3d8bba41 100644 --- a//systems-manager/latest/userguide/patch-manager.md +++ b//systems-manager/latest/userguide/patch-manager.md @@ -66 +66 @@ Patch Manager currently offers four methods for running `Scan` and `Scan and ins - * **(Recommended) A patch policy configured in Quick Setup** – Based on integration with AWS Organizations, a single patch policy can define patching schedules and patch baselines for an entire organization, including multiple AWS accounts and all AWS Regions those accounts operate in. A patch policy can also target only some organizational units (OUs) in an organization. You can use a single patch policy to scan and install on different schedules. For more information, see [Configure patching for instances in an organization using Quick Setup](./quick-setup-patch-manager.html) and [Patch policy configurations in Quick Setup](./patch-manager-policies.html). + * **(Recommended) A patch policy configured in Quick Setup** – Based on integration with AWS Organizations, a single patch policy can define patching schedules and patch baselines for an entire organization, including multiple AWS accounts and all AWS Regions those accounts operate in. A patch policy can also target only some organizational units (OUs) in an organization. You can use a single patch policy to scan and install on different schedules. For more information, see [Configure patching for instances in an organization using a Quick Setup patch policy](./quick-setup-patch-manager.html) and [Patch policy configurations in Quick Setup](./patch-manager-policies.html).