AWS eks documentation change
Summary
Grammar improvements and clarity enhancements
Security assessment
Changes involve grammatical fixes (e.g. 'aren't' to 'are not') and removal of redundant text. No security implications or security documentation additions.
Diff
diff --git a/eks/latest/userguide/capabilities-troubleshooting.md b/eks/latest/userguide/capabilities-troubleshooting.md index 26510885b..02e2349d6 100644 --- a//eks/latest/userguide/capabilities-troubleshooting.md +++ b//eks/latest/userguide/capabilities-troubleshooting.md @@ -15,2 +14,0 @@ To contribute to this user guide, choose the **Edit this page on GitHub** link t -This topic provides general troubleshooting guidance for EKS Capabilities, including capability health checks, common issues, and links to capability-specific troubleshooting. - @@ -19 +17 @@ This topic provides general troubleshooting guidance for EKS Capabilities, inclu -EKS Capabilities are fully managed and run outside your cluster. You don’t have access to controller logs or controller namespaces. Troubleshooting focuses on capability health, resource status, and configuration. +EKS Capabilities are fully managed and run outside your cluster. You do not have access to controller logs or controller namespaces. Troubleshooting focuses on capability health, resource status, and configuration. @@ -87 +86 @@ The response includes: -**ACTIVE** : Capability is running and ready to use. If resources aren’t working as expected, check resource status and IAM permissions. +**ACTIVE** : Capability is running and ready to use. If resources are not working as expected, check resource status and IAM permissions. @@ -95 +94 @@ The response includes: - * IAM role doesn’t exist or isn’t accessible + * IAM role does not exist or is not accessible @@ -258 +257 @@ If a capability remains in `CREATING` state for longer than expected: -If the capability is `ACTIVE` but resources aren’t being created or updated: +If the capability is `ACTIVE` but resources are not being created or updated: