Revert "Improve Infrastructure as Code page for SEO"

[asafashirov]

Reverts #15941 because the change to What is Iac? page had a negative effect on "infrastructure as code" searches:

• Google SERP Impressions dropped: 4.54K Sep 9 to Sep 23 (2 weeks) vs 7.53K Aug 25 to Sep 8 (2 weeks before that)
• Google AIO "right rail" dropped from ~5th place to ~8th position

[claude]

Pull Request Review

This PR reverts changes to the Infrastructure as Code page due to negative SEO impact. While the business justification is clear and valid, I've identified several issues that should be addressed:

Issues Found

Content and Structure:

1. Line 11: "examing" should be "examining" - typo in the introductory paragraph.

2. Line 17: "Let's start with examing why infrastructure as code is important" - another instance of the same typo.

3. Missing newline at end of file: The markdown file should end with a newline character as per repository requirements in AGENTS.md.

Style Guide Compliance:

4. Line 11: Bold text usage - "infrastructure as code is about bringing software engineering principles" - this bold formatting appears inconsistent with the overall document structure and may not be necessary for emphasis here.

Content Flow and Clarity:

5. Lines 13-18: The transition from the opening paragraph to the four key questions feels abrupt. Consider adding a smoother transition sentence.

6. Line 17: The phrase "Let's start with examing" is too casual for technical documentation. Consider "We'll begin by examining" or similar.

Ordered List Formatting:

7. Lines 54-57: The ordered list uses actual numbers (1., 2., 3., 4.) instead of the required format where all items should begin with "1." as specified in STYLE-GUIDE.md line 73. This should use "1." for all items instead of sequential numbering.

Missing Elements:

8. The reverted version removes the code example that was present in the SEO-optimized version. While this aligns with the revert goal, consider if a simpler code example might be beneficial for reader understanding without negatively impacting SEO.

Recommendations

1. Fix the spelling errors ("examing" → "examining")
2. Correct the ordered list formatting to follow repository standards
3. Add a newline at the end of the file
4. Consider refining the transition language for better flow
5. Review the bold text usage for consistency

The revert is justified from a business perspective, but these technical issues should be addressed to maintain content quality standards.

[pulumi-bot]

Your site preview for commit 60cdfdb is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16062-60cdfdb5.s3-website.us-west-2.amazonaws.com.