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!

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jun 30, 2026 8:25pm

[rachaelrenk]

Thanks for these, @szepeviktor! A lot of this is solid cleanup. The typo fixes, file rename, Generate link now pointing to its own page, our → your corrections, and the heading-hierarchy fix are all clear wins. 🙏

@hongyi-chen — on the copy changes you flagged, here's where I landed. I pushed a few tweaks directly to the branch rather than block on them:

Cloud agents quickstart
Linking out from "Next steps" matches a TODO we'd left in that section, so I kept that direction, with three adjustments:

• Reworded the intro to "try these next steps", which is the copy we want to stick with.
• The refactor had ended up linking the same Scheduled Agents and Integrations quickstarts twice on the page, and pointed to two different skills pages. I de-duplicated so each lands once.
• Restored the oz schedule create example and the note that integrations require a Build, Max, or Business plan. That useful context was otherwise a click away.

Refund policy (plans-pricing-refunds.mdx)
The original was genuinely awkward (faulty parallelism), so the grammar fix is fair and I kept it, along with the new "how to enable" link. I did restore the original requirement strength though as the rewrite had softened "we require … before we can provide refunds or credits" into a suggestion. cc @hongyi-chen 👀 do we need a pricing official to confirm this line?

Feedback doc
Kept the heading-level fix; just recapitalized "Enterprise" since it's one of our plan names.

One process note: this still needs a linked same-repo issue before it can merge (the bot flagged this up top). II'll open a quick issue describing the cleanup and link it, so we can get this moving.

Thanks again for the contribution!

[rachaelrenk]

branch is now clean!