docs: fix docs typos and example issues for issue 725

[vaquarkhan]

Correct broken snippets and grammar, fix RST formatting issues, and remove decorative emoji from documentation headers for consistency with project standards.

[Short description explaining the high-level reason for the pull request]

Changes

How I tested this

Notes

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

fixed #725

[vaquarkhan]

Hi @skrawcz PR is ready for review

[skrawcz]

why remove the emoji?

[vaquarkhan]

Here is a quick summary of why we removed decorative emojis from the documentation:

• ASF & Accessibility Standards: Decorative emojis in section headers disrupt screen readers (which read the literal emoji name aloud) and break document navigation. Removing them aligns with W3C/WCAG accessibility guidelines and Apache Software Foundation (ASF) project standards.

• Markdown Accessibility Guidelines: https://accessibility.github.com/documentation/guide/getting-started-with-agents/ (Explicitly warns against decorative emojis in headers)
  If you can still see issue I will.add back emoji and will give new pr to only broken fix .plz advice

[skrawcz]

TIL - thanks!

[skrawcz]

I'd leave the emoji in -- otherwise looks good

[skrawcz]

@vaquarkhan can you rebase? can't seem to merge because of the validation...

[vaquarkhan]

@skrawcz done