Docs: fix documentation in contribute/code page

[qadir1020]

Closes #

What I did

Three small grammar fixes in docs/contribute/code.mdx:

• Line 105: commands accepts → command accepts (subject-verb agreement)
• Line 166: it's testing suite → its testing suite (possessive vs. contraction)
• Line 170: lead to one of the maintainers mark → lead to one of the maintainers marking (gerund form needed)

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

Caution

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

No manual testing is necessary. The change is text-only in docs/contribute/code.mdx. Reviewers can confirm by reading the diff in the "Files changed" tab.

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>

Summary by CodeRabbit

• Documentation
  • Clarified contributor docs: fixed build command wording and added details on supported build arguments; expanded testing guidance to mention snapshot updates and that maintainers may mark PRs as Work in Progress.
  • Clarified "What’s a story?" guidance: explained that stories help verify UI correctness and highlighted checking related stories (e.g., Button variants) to avoid regressions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9109e361-7c5e-46dc-aa2a-d342dae37eea

📥 Commits

Reviewing files that changed from the base of the PR and between bd44e1c and e9dd404.

📒 Files selected for processing (1)

• docs/get-started/whats-a-story.mdx

✅ Files skipped from review due to trivial changes (1)

• docs/get-started/whats-a-story.mdx

---

📝 Walkthrough

Walkthrough

Small documentation edits: clarify that yarn build accepts arguments, document re-running Vitest with -u for snapshot updates, note maintainers may mark PRs as Work in Progress if tests fail, and add a sentence about checking related Button stories for regressions.

Changes

Documentation Updates

Layer / File(s)	Summary
Build arguments docs/contribute/code.mdx	Adds sentence that the yarn build command accepts arguments to speed development.
Vitest snapshot guidance docs/contribute/code.mdx	Explains rerunning tests with -u to update Vitest snapshots when they fail.
Work in Progress label docs/contribute/code.mdx	Adds note that maintainers may mark PRs as Work in Progress until tests pass.
Story regression-checking docs/get-started/whats-a-story.mdx	Inserts sentence directing readers to check the Button component’s other stories to verify changes to Primary don’t cause regressions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[kylegach]

Thanks, @qadir1020! Go ahead and throw the change from #34728 in here too and I'd be glad to approve & merge.

[qadir1020]

Thanks, @qadir1020! Go ahead and throw the change from #34728 in here too and I'd be glad to approve & merge.

Thanks @kylegach! I've pushed the change from #34728 into this PR — please take another look.

[kylegach]

Thanks for the fixes, @qadir1020!