Fix text quality issues in key docs entry points

[szepeviktor]

Summary

• fixed several clear typos and wording issues in published docs
• renamed editting_diff.png to editing_diff.png and updated its reference
• corrected changelog and command-corrections text issues
• rewrote the refund-policy caution in plans-pricing-refunds.mdx so the requirements are grammatical and explicit
• removed non-executable narrative lines from the oz agent run example in reference/cli/index.mdx
• fixed the Generate link target in known-issues.mdx
• corrected first-person/internal wording in troubleshooting examples from our to your
• fixed heading hierarchy in sending-us-feedback.mdx
• refactored cloud-agents/quickstart.mdx:
  • removed the embedded TODO comment
  • replaced the inline mini-guide in Next steps with links to dedicated docs
  • removed the duplicated What to explore next section

Follow-ups

@dannyneira Tools used: https://github.com/crate-ci/typos and RoboViktor 🤖

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @szepeviktor on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

[vercel]

@szepeviktor is attempting to deploy a commit to the warpdotdev Team on Vercel.

A member of the Team first needs to authorize it.

[oz-for-oss]

@szepeviktor

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

[oz-for-oss]

@szepeviktor

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @szepeviktor on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @szepeviktor on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

[szepeviktor]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!