Revise AWS content for Neo branding and features

[isaac-pulumi]

Updated headings and descriptions to reflect new branding and features for Neo on AWS in addition to correcting inaccuracies in the original copy.

Proposed changes

The original version was not accurate and was missing key points.

[claude]

Documentation Review

I've reviewed the changes to update the AWS partner page for Neo branding and features. Overall, the changes improve accuracy and align with the new branding. However, there are a few issues to address:

Issues Found

1. Missing trailing newline (line 366)

The file should end with a newline character. The current last line is:

{{ end }}

{{ end }}

2. Grammatical issue - "End-to-end Compliance" heading (line 142)

The heading "End-to-end Compliance" should follow sentence case for H2+ headings per the style guide. However, this is actually correct as-is since "end-to-end" is a compound modifier.

3. Inconsistent product naming - "Neo" vs "Pulumi Neo" (lines 127, 145, 157, 172, 178)

The changes refer to "Neo" without the "Pulumi" prefix in most places. According to STYLE-GUIDE.md, product names should be capitalized correctly and expanded at first mention. Consider whether the first mention should be "Pulumi Neo" with subsequent references as "Neo".

Specifically:

• Line 127: "Automate AWS Operations with Neo" (first mention on page)
• Line 145: "Audit your infrastructure with built-in policy packs..." (no Neo mention)
• Line 163: "Developers provision infrastructure..." (no Neo mention)
• Line 172: "Deliver AI Projects Faster"
• Line 178: "Neo deploys training and inference workloads..."

4. Technical accuracy check needed - AWS Bedrock AgentCore (line 130)

The description states "Built on AWS Bedrock AgentCore". Please verify this is the correct AWS product name. AWS typically uses "Amazon Bedrock" and I'm not familiar with "AgentCore" as a specific Bedrock component. This may need fact-checking.

5. Hyphenation - "policy-as-code" (line 164)

Line 164 uses "Policy-as-code" (capitalized) which is correct for the start of a sentence, but it should be consistently hyphenated throughout.

Strengths

• Improved clarity and conciseness in all descriptions
• Removed vague qualifiers and unnecessary filler
• Specific features mentioned (CIS, NIST, PCI-DSS, HITRUST)
• Better alignment with actual product capabilities
• Fixed trailing space issue that existed in the original

Recommendations

1. Add the missing trailing newline
2. Verify the correct AWS product name for Bedrock/AgentCore
3. Consider using "Pulumi Neo" for the first mention on the page
4. Ensure consistent hyphenation for compound terms

---

If you'd like me to review additional changes or help implement any fixes, mention @claude and I'll assist.

[pulumi-bot]

Your site preview for commit 8483b3e is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16658-8483b3ed.s3-website.us-west-2.amazonaws.com.

[pulumi-bot]

Your site preview for commit e1c9632 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16658-e1c9632e.s3-website.us-west-2.amazonaws.com.

[pulumi-bot]

Your site preview for commit c9818d6 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16658-c9818d64.s3-website.us-west-2.amazonaws.com.

[pulumi-bot]

Your site preview for commit 7c7c273 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16658-7c7c2731.s3-website.us-west-2.amazonaws.com.

[isaac-pulumi]

edit for brevity

[pulumi-bot]

Your site preview for commit 3a0af56 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16658-3a0af565.s3-website.us-west-2.amazonaws.com.