Merge pull request #269 from altheaden/omega/update-dev-env-instructions

Add `pre-commit install` instructions and fix minor issues with Quick Start

The quick start was missing a line to explain how to initialize pre-commit the first time a newly-created dev environment is used, so I've added that.

During the process, I also noticed some spelling errors and inconsistent line lengths. I've fixed those as I noticed them.

Author: xylar

components/omega/doc/devGuide/QuickStart.md

@@ -8,7 +8,7 @@
 
 We ask developers to make their own fork of the E3SM to use for development
 branches.  To do this, go to the page for the
-[E3SM-Project/E3SM](https://github.com/E3SM-Project/E3SM) respository and
+[E3SM-Project/E3SM](https://github.com/E3SM-Project/E3SM) repository and
 click on the `fork` button near the upper right corner.  Set "owner" to your
 GitHub username (this should be the default) and click "Create fork".
 
@@ -60,7 +60,14 @@ conda create -n omega_dev --file dev-conda.txt
 conda activate omega_dev
 ```
 (You can reuse `omega_dev` for other branches as long as `dev-conda.txt` has
-not changed between branchs.)
+not changed between branches.)
+
+The first time you set up the environment, you need to initiate `pre-commit`:
+```sh
+pre-commit install
+```
+This needs to be done once per environment, so re-run it as necessary if you
+re-create the development environment.
 
 Please activate this environment each time you commit code.  This will ensure
 that `pre-commit` and the associated linting utilities are available and that
@@ -133,8 +140,10 @@ script that you can run to build Omega:
 (omega-dev-quick-start-getting-meshes)=
 ### Getting test meshes
 
-Some tests require a valid Omega mesh file. Different tests require different meshes. At the moment, mesh files need
-to be copied or linked to specifically named files under the `test` directory. Appropriate mesh files can be downloaded from:
+Some tests require a valid Omega mesh file. Different tests require different
+meshes. At the moment, mesh files need to be copied or linked to specifically
+named files under the `test` directory. Appropriate mesh files can be
+downloaded from:
 - [Ocean Mesh](https://web.lcrc.anl.gov/public/e3sm/inputdata/ocn/mpas-o/oQU240/ocean.QU.240km.151209.nc)
 - [Global Mesh](https://web.lcrc.anl.gov/public/e3sm/polaris/ocean/polaris_cache/global_convergence/icos/cosine_bell/Icos480/init/initial_state.230220.nc)
 - [Planar Mesh](https://gist.github.com/mwarusz/f8caf260398dbe140d2102ec46a41268/raw/e3c29afbadc835797604369114321d93fd69886d/PlanarPeriodic48x48.nc)
@@ -151,7 +160,8 @@ cd ..
 
 ### Running CTests
 
-Omega includes several unit tests that run through CTest. The unit tests need to be run on a compute node.
+Omega includes several unit tests that run through CTest. The unit tests need
+to be run on a compute node.
 
 To run the tests:
 ```sh
@@ -189,7 +199,7 @@ Total Test time (real) =   8.91 sec
 
 If Omega CTests are failing or simulations are crashing, setting
 `OMEGA_BUILD_TYPE` to `Debug` can be helpful for debugging purposes. If you
-need to identify which test has failed, it may be useful to examin the CMake
+need to identify which test has failed, it may be useful to examine the CMake
 ctest log file located at `$BUILD_DIR/Testing/Temporary/LastTest.log`.
 
 (omega-dev-parmetis-libs)=
@@ -246,7 +256,7 @@ used to but the hope is that it leads to a coherent code style in Omega.
 
 ### VS Code
 
-You may wish to condier using an integrated development environment (IDE) to
+You may wish to consider using an integrated development environment (IDE) to
 develop your code.  A convenient option for developing on HPC is
 [Visual Studio Code (VS Code)](https://code.visualstudio.com/).  It has plugins
 for [c++](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools),