[TEST] Demo changes for incorporate-pr-feedback skill

[buraizu]

What does this PR do? What is the motivation?

TEST BRANCH — for demonstrating the incorporate-pr-feedback skill. Do not merge.

Updates the Getting Started with AWS integration guide with several changes:

• Rewrites the Overview to be more descriptive
• Expands the Prerequisites section with a note about console access
• Adds guidance on choosing a log forwarding method
• Adds a new Tag filtering section under Configuration

Merge instructions

Merge readiness:

• Ready for merge

Additional notes

This PR is intentionally written with style issues to demonstrate the incorporate-pr-feedback skill's ability to process and apply reviewer comments.

[buraizu]

Thanks for working on this! I've left a few comments on specific lines. Some of these are Vale violations that our linter will catch, and a couple are content/style concerns.

[buraizu]

Vale: 'will walk' uses a temporal word ('will'). Revert to present tense: "This guide walks you through..."

[buraizu]

Vale: 'Once you have completed setup' — use 'After you complete setup' instead. Also, 'easily' should be removed (Vale: words to avoid).

[buraizu]

Left several inline comments covering Vale violations and content concerns. These demonstrate the kinds of issues incorporate-pr-feedback can help apply.

[buraizu]

Vale: 'will walk' uses a temporal word. Switch to present tense: "This guide walks you through..."

Also, 'Once you have completed setup' → 'After you complete setup' (Vale: use 'After' instead of 'Once').

Also, remove 'easily' — it's a filler word per the style guide.

Also, 'to ensure that all your data is collected' — 'ensure' should be avoided or replaced with 'helps ensure'. Consider simplifying: end the sentence at 'configure log forwarding.'

[buraizu]

Vale: 'Note that' should be replaced with 'Note:' per the Datadog style guide.

Also, the additional clause 'and administrative access to your AWS console' is useful context — keep it.

[buraizu]

Content: The 'Tag filtering' section uses several flagged phrases:

• 'leverage' → use 'use'
• 'utilizing' → use 'using'
• 'easily' → remove
• 'fine-tune' → use 'customize'

Suggested rewrite: "Use tag-based filtering to control which AWS resources Datadog monitors. Under the Metric Collection tab, add tag filters to include or exclude specific resources and customize your monitoring scope."

[buraizu]

Vale: 'simplest' — avoid superlatives like 'simplest'. Consider: 'This option requires no additional infrastructure.'

[buraizu]

Vale + Style: Multiple issues in this tip:

• 'currently' is a temporal word — remove it
• 'easier to set up' — avoid comparatives like 'easier'; be specific instead
• The tip format ('Tip:') is non-standard for this doc site — use a 'Note:' callout or incorporate the guidance into the bullet list above instead.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/bryce/incorporate-pr-feedback-demo/getting_started/integrations/aws

[buraizu]

Vale (multiple): Several issues on this line:

1. 'will walk' uses a temporal word ('will'). Revert to present tense: 'This guide walks you through...'
2. 'Once you have completed setup' → 'After you complete setup' ('Once' is flagged; use 'After')
3. Remove 'easily' — filler word per the Datadog style guide
4. 'to ensure that all your data is collected' — remove; it's redundant padding. End the sentence at 'configure log forwarding.'

Suggested rewrite: 'This guide walks you through integrating an Amazon Web Services (AWS) account with Datadog using Datadog's CloudFormation template. After completing setup, you can enable individual AWS service integrations, install the Datadog Agent on EC2 instances for deeper visibility, and configure log forwarding.'

[buraizu]

Vale: 'Note that' should be replaced with 'Note:' — this is a direct Vale violation per the Datadog style guide.

Change to: 'Note: Your AWS user must have the following IAM permissions to run the template:'

[buraizu]

Vale (multiple): The new 'Tag filtering' section has several style guide violations:

1. 'leverage' → 'use'
2. 'utilizing' → 'using'
3. 'easily' → remove
4. 'fine-tune' → 'customize'

Suggested rewrite:

'Use tag-based filtering to control which AWS resources Datadog monitors. Add tag filters under the Metric Collection tab to include or exclude specific resources and customize your monitoring scope.'

[buraizu]

Style: 'simplest' is a superlative that implies ease — avoid these per the style guide. Change to something more factual: 'This option requires no additional infrastructure.'

[buraizu]

Vale + Structure: Several issues with this tip:

1. 'currently' is a temporal word — remove it ('If you are unsure which method to use...')
2. 'easier' is a comparative that implies simplicity — be specific instead (e.g., 'requires less configuration')
3. 'Tip:' is a non-standard callout format for this site. Either use 'Note:' or fold this guidance into the bullet list above as a note on the Firehose option.