AWS devopsagent documentation change
Summary
Fixed markdown formatting (escaped dash) and corrected grammar ('the each providers' to 'each provider's') in feature descriptions for Splunk integration.
Security assessment
The changes are purely cosmetic and grammatical, correcting markdown syntax and possessive form. No security implications are mentioned or implied.
Diff
diff --git a/devopsagent/latest/userguide/connecting-telemetry-sources-connecting-splunk.md b/devopsagent/latest/userguide/connecting-telemetry-sources-connecting-splunk.md index 1edffaf30..76d5e235f 100644 --- a//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-splunk.md +++ b//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-splunk.md @@ -13 +13 @@ Currently, AWS DevOps Agent supports Splunk users with built-in, 1 way integrati - * **Automated Investigation triggering -** Splunk events can be configured to trigger AWS DevOps Agent incident resolution Investigations via AWS DevOps Agent webhooks. + * **Automated Investigation triggering** \- Splunk events can be configured to trigger AWS DevOps Agent incident resolution Investigations via AWS DevOps Agent webhooks. @@ -15 +15 @@ Currently, AWS DevOps Agent supports Splunk users with built-in, 1 way integrati - * **Telemetry introspection** \- AWS DevOps Agent can introspect Splunk telemetry as it investigates an issue via the each providers remote MCP server. + * **Telemetry introspection** \- AWS DevOps Agent can introspect Splunk telemetry as it investigates an issue via each provider's remote MCP server.