message: clarify wording about lerna versioning
  [skip ci]
diff: @@ -11,8 +11,9 @@ The versions of all packages in the mono-repo are updated at the same time, to t
  Determine whether the release should be a major (breaking), minor, or patch.
  For breaking releases, include upgrade instructions in the changelog.
  3. Commit the changes, make sure your working tree is clean, and push your branch to GitHub.
  -4. To update versions in the `package.json` for all packages, use `npx lerna version --force-publish="*" --exact`. `npx` will use the version of `lerna` that is installed as a `devDependency` of the mono-repo. `--force-publish` will update interdependencies as well as the version numbers of the packages themselves.
  -5. Open a pull request with your updates
  +4. To update versions in the `package.json` for all packages, use `npx lerna version --force-publish="*" --exact`.
  +`npx` will use the version of `lerna` that is installed as a `devDependency` of the mono-repo. `--force-publish` will update interdependencies as well as the version numbers of the packages themselves. Before the version updating happens, `lerna` will ask what you want the version to be.
  +5. Open a pull request with your version updates
  6. Merge the pull request after version-checking tests finish
  7. Create a tag on GitHub for the version
  8. Check out master and pull again. `git checkout master`, `git pull origin master`
  