message: Update package publishing instructions
diff: @@ -6,32 +6,22 @@ This document is for project maintainers who are doing versioning, releases, and
  The versions of all packages in the mono-repo are updated at the same time, to the same version number.
  -1. Get the latest code on master and create a branch. `git checkout master`, `git pull origin master`, `git checkout -b release-vX.Y.Z`
  -2. Look at the `git log` since the last release, and list anything significant in the `CHANGELOG.md`.
  +1. Get the latest code on master: `git checkout master`, `git pull origin master`
  +2. Make sure your history is clean with `git status`
  +3. Look at the `git log` since the last release, and list anything significant in the `CHANGELOG.md`.
  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.
  -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 (in Linting Tests)
  -7. Check to see that the new version is on GitHub
  -8. Check out master and pull again. `git checkout master`, `git pull origin master`
  -9. `lerna publish from-git` will update all packages that don't yet have the new version published. You can safely re-run this command if publishing is interrupted.
  -10. Make sure all the packages made it up to npm
  +For breaking releases, include upgrade instructions in the changelog. Commit your changes.
  +4. Update all package versions, publish to npm, and push to GitHub with this command: `npx lerna publish --force-publish="*" --exact`
  +7. Check to see that the new version is on GitHub and on npm
  ## Updating packages yolo-style
  -If you are very confident in what you are doing, you can accomplish all of the above by running this command from an up-to-date version of `master`. It is recommended to pair this, since it skips over safety checks.
  +If you are very confident in what you are doing, you can accomplish all of the above by running this command from an up-to-date version of `master`.
  ```sh
  npx lerna publish --force-publish="*" --exact
  ```
  -Remember to do the Changelog and create tags.
  -
  ## Pitfalls to look out for
  - Always make sure you are publishing from an up-to-date copy of `master`. You don't want to publish stale code!
  