message: Update rush change instructions
diff: @@ -89,8 +89,9 @@ Note that it is a good idea to `rush install` after each `git pull` as dependenc
  5. Add changelog entry (which could potentially cover several commits): `rush change`
  6. Follow prompts to enter a change description or press ENTER if the change does not warrant a changelog entry. If multiple packages have changed, multiple sets of prompts will be presented. If the changes are only to non-published packages (like **testbed**), then `rush change` will indicate that a changelog entry is not needed.
  7. Completing the `rush change` prompts will cause new changelog entry JSON files to be created.
  -8. In order to keep the Git history clean, amend the prior commit using the **Commit All (Amend)** menu item in Visual Studio Code or use the command line: `git commit --amend --no-edit`
  -9. Push changes
  +8. Add/stage this new file or files using the "+" in VS Code or from the command line using `git add <name of file>` (can use `git status` to get name of file)
  +9. In order to keep the Git history clean, amend the prior commit using the **Commit Staged (Amend)** menu item in Visual Studio Code or use the command line: `git commit --amend --no-edit`
  +10. Push changes
  > Note: The CI build will break if changes are pushed without running `rush change`. The fix will be to run `rush change` (as above) and push those changes as a separate commit.
  