Fix wrong npm start command

[rilwis]

This PR just fix the wrong npm start command in the docs. Currently, it's npm run start where it should be npm start.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: rilwis <[email protected]>
Co-authored-by: ndiego <[email protected]>
Co-authored-by: juanmaguitar <[email protected]>
Co-authored-by: gziolo <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @rilwis! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[ndiego]

npm start does technically work, but for consistency with npm run build, I do think npm run start is better for new users.

[juanmaguitar]

As this is meant to be an introductory guide for using JavaScript in WordPress, I think we should reference both npm run start and npm start.
What about something like?

• **Development Mode (npm run start or just npm start)

[ndiego]

As this is meant to be an introductory guide for using JavaScript in WordPress, I think we should reference both npm run start and npm start.
What about something like?

**Development Mode (npm run start or just npm start)

➕ Good call

[gziolo]

npm start is the first thing you learn when interacting with JavaScript projects so I guess it's better to use that form as proposed in this PR.