[Thodorr]

What I did

• Removed the outdated 7.0.0-alpha.47 prerelease example.
• Changed "a inDevelopment flag" to "an inDevelopment flag".

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

No runtime testing is necessary. The changes are text-only in docs/contribute/code.mdx and can be verified by reviewing the rendered Markdown.

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

• Declare whether manual QA will be needed for this PR during the next release, through qa:needed or qa:skip

• 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>

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 571d796e-948a-49a4-8a8e-47f7753fee7a

📥 Commits

Reviewing files that changed from the base of the PR and between c9689e2 and 4456694.

📒 Files selected for processing (1)

• docs/contribute/code.mdx

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

Walkthrough

The contributor documentation removes a prerelease version example from the next branch description and corrects the article before the inDevelopment flag.

Changes

Storybook documentation

Layer / File(s)	Summary
Contributor documentation wording docs/contribute/code.mdx	The next branch description no longer includes a prerelease version example. The sandbox instructions use “an inDevelopment flag.”

Merge Risk: ⚪ Minimal · up to 44566

This PR makes two localized documentation corrections with no runtime or product behavior impact, so no actionable merge-blocking risk remains.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

---

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

[storybook-contribution-review]

🤖 I am the Storybook contribution review bot; a human maintainer approved this message before it was posted.
Review phase: Final verdict - documentation-only diff; architecture, code quality, and runtime verification stages skipped as trivial

Hi @Thodorr,

Thank you for this. Both changes are correct, and the first one is the kind of documentation rot that is very easy to read straight past.

The e.g., 7.0.0-alpha.47 example dated from the 7.0 alpha line. The latest prerelease today is 10.6.0-beta.2, so anyone following this page was being shown a version three majors behind the branch that same paragraph tells them to target. Deleting the example rather than bumping it is the right call: the sentence already says "the latest prerelease version", and any hardcoded number here would just go stale again. That is a small edit that stops a recurring problem, which is the better kind of docs fix.

The a inDevelopment → an inDevelopment correction is right as well.

I reviewed this as a documentation-only change. It touches one .mdx file with no code, so it skipped the architecture and code-quality stages, and there is no runtime behaviour to verify.

The red checks are not yours to fix

The PR currently shows a failing Danger run. None of it is caused by your change:

PR is not labeled with one of: ["ci:normal","ci:merged","ci:daily","ci:docs"]
PR is not labeled with one of: ["qa:needed","qa:skip","qa:success"]
This PR needs an approving review from a Storybook Core or Developer Experience team member before it can be merged.

Those label groups are applied by maintainers, and the approving review has to come from a human on the core team. There is genuinely nothing for you to do here, so please don't push extra commits trying to turn CI green.

From a content review perspective this is ready. Handing it over to a maintainer for the labels and the approving review.

[jonniebigodes]

@Thodorr, thanks for taking the time to put this pull request together and help us improve the documentation. We appreciate it 🙏

I've checked, and all is good on my end; I'll gladly merge this once the checklist clears.

Hope you have a fantastic day.

Stay safe