message: Some additional changes
diff: @@ -389,10 +389,10 @@ Before a PR can be merged, it should satisfy the following:
  - [ ] Does `make` or `cmake` have a new target?
  - [ ] Did the requirements or the installation process change? *(rare)*
  - [ ] Update `.gitignore`:
  - - [ ] Check if `make distclean; git status` shows any files that are generated from the source but we don't want to track in the repository.
  + - [ ] Check if `make distclean; git status` shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
  - [ ] Add new patterns (just for the new files above) and re-run the above test.
  - [ ] New examples:
  - - [ ] All sample runs at the top of the example work.
  + - [ ] Add sample runs at the top of the example and make sure they work.
  - [ ] Update `examples/makefile`:
  - [ ] Add the example code to the appropriate `SEQ_EXAMPLES` and `PAR_EXAMPLES` variables.
  - [ ] Add any files generated by it to the `clean` target.
  @@ -408,7 +408,7 @@ Before a PR can be merged, it should satisfy the following:
  - [ ] In `examples.md`, list the example under the appropriate categories, add new categories if necessary.
  - [ ] Add a short description of the example in the "Extensive Examples" section of `features.md`.
  - [ ] New miniapps:
  - - [ ] All sample runs at the top of the miniapp work.
  + - [ ] All sample runs at the top of the miniapp source file(s) work.
  - [ ] Update top-level `makefile` and `makefile` in corresponding miniapp directory.
  - [ ] Add the miniapp binary and any files generated by it to the top-level `.gitignore` file.
  - [ ] Update CMake build system:
  @@ -426,10 +426,10 @@ Before a PR can be merged, it should satisfy the following:
  - [ ] All significant new classes, methods and functions have Doxygen-style documentation in source comments.
  - [ ] Consider adding new sample runs in existing examples to highlight the new capability.
  - [ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the `mfem/web` repo.
  - - [ ] If this is a major new feature, consider mentioning in the short summary inside `README` *(rare)*.
  + - [ ] If this is a major new feature, consider mentioning it in the short summary inside `README` *(rare)*.
  - [ ] List major new classes in `doc/CodeDocumentation.dox` *(rare)*.
  - [ ] Update this checklist, if the new pull request affects it.
  -- [ ] Run the unit tests and make sure they all pass `make unittest`.
  +- [ ] Run `make unittest` to make sure all unit tests pass.
  - [ ] Run the tests in `tests/scripts`.
  - [ ] (LLNL only) After merging:
  - [ ] Regenerate `README.html` files from companion documentation pull requests.
  @@ -492,7 +492,7 @@ MFEM uses a `master`/`next`-branch workflow as described below:
  (replace `3.3.2` with current release):
  - Rename the current `next` branch to `next-pre-v3.3.2`.
  - Create a new `next` branch starting from the `v3.3.2` release.
  - - Local copies of `next` can then be updated with `git checkout -B next origin/next`.
  + - Local copies of `next` can then be updated with `git fetch origin next && git checkout -B next origin/next`.
  ### Release Checklist
  