Update defender-for-cloud-planning-and-operations-guide.md

[Sbiz85]

• Fixed typos and grammar according to Microsoft Writing Style Guide
• Restructured Roles section: condensed into one table
• Slightly edited alt text
• Included comments with rationale behind decisions as well as further questions that I'd ask for clarification
• Will attach corrected graphic via email

[learn-build-service-prod]

Learn Build status updates of commit f514d66:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/defender-for-cloud/defender-for-cloud-planning-and-operations-guide.md	✅Succeeded

For more details, please refer to the build report.

[v-regandowner]

@Sbiz85 - Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks!

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[batamig]

Copying comments and image from email for convenience

I have made the following changes:

1. Corrected typos and grammar according to the Microsoft Writing Style Guide
2. Ensured consistent content hierarchy (headers)
3. Restructured the security roles section by condensing the content into one table
4. Slightly edited some of the alt text to make the images more accessible to screen readers
5. Included comments using that illustrates further questions as well as rationale behind my decisions

Two notes:

1. The changes I made to the section regarding Azure roles was quite extensive: I restructured the entire thing, created a new subheader, and inserted a table. Coming from a UX background, it could be worthwhile to AB test how these changes could impact KPIs.

2. One of my recommendations included fixing the typos and formatting in the graphic below. My main preference, however, would be to sit with the project lead and discuss possibly re-working the graphic to be less content-heavy and redundant, since the content is also spelled out below it in the article.

[Sbiz85]

@microsoft-github-policy-service agree [company="{your company}"]

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

[Sbiz85]

@microsoft-github-policy-service agree

[prmerger-automator]

@Sbiz85 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[v-regandowner]

@dcurwin - Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.