AWS wellarchitected documentation change
Summary
Fixed typos and clarified responsibility assignment processes
Security assessment
Grammatical improvements and process clarifications with no security-specific content changes
Diff
diff --git a/wellarchitected/latest/framework/ops_ops_model_def_responsibilities_ownership.md b/wellarchitected/latest/framework/ops_ops_model_def_responsibilities_ownership.md index ce4505b04..a4ec5a54d 100644 --- a//wellarchitected/latest/framework/ops_ops_model_def_responsibilities_ownership.md +++ b//wellarchitected/latest/framework/ops_ops_model_def_responsibilities_ownership.md @@ -11 +11 @@ Understand the responsibilities of your role and how you contribute to business -Occasionally, a responsibility might not have a clear owner. In these situations, design a mechanism resolve this gap. Create a well-defined escalation path to someone with the authority to assign ownership or plan to address the need. +Occasionally, a responsibility might not have a clear owner. In these situations, design a mechanism to resolve this gap. Create a well-defined escalation path to someone with the authority to assign ownership or plan to address the need. @@ -91 +91 @@ While they identified, addressed, and documented the majority of responsibilitie - 1. Identify frequently-requested, resource-intensive request, which are typically strong candidates for improvement. + 1. Identify frequently-requested, resource-intensive requests, which are typically strong candidates for improvement. @@ -93 +93 @@ While they identified, addressed, and documented the majority of responsibilitie - 2. Look for best practices, patterns. and prescriptive guidance, and simplify and standardize improvements with this guidance. + 2. Look for best practices, understand patterns, follow prescriptive guidance, and simplify and standardize improvements.