:ormatting

Author: jmlarson1

docs/dev_guide/release_management/release_platforms/rel_spack.rst

@@ -5,7 +5,7 @@ A workflow for updating libEnsemble on Spack
 
 This assumes you have already:
 
- - made a PyPI package for new version of libEnsemble and
+ - made a PyPI package for the new libEnsemble version and
  - made a GitHub fork of Spack and cloned it to your local system.
 
 Details on how to create forks can be found at https://help.github.com/articles/fork-a-repo.
@@ -32,7 +32,7 @@ To set upstream repo::
     git remote set-url --push upstream no_push
     git remote -v # Check for line: `upstream no_push (push)`
 
-Updating (the main develop branch)
+Updating (the develop branch)
 ----------------------------------
 
 You will now update your local machine from the upstream repo (if in doubt,
@@ -53,12 +53,12 @@ Fetch from the upstream repo::
 To update your local machine, you may wish to rebase or overwrite your local files.
 Select from the following:
 
-Now make your local machine identical to upstream repo (**WARNING:** Any local changes will be lost!)::
+Now make your local machine identical to the upstream repo (**WARNING:** Any local changes will be lost!)::
 
     git reset --hard upstream/develop
 
-Alternativvely, if you have existing local changes to go "on top" of latest code (usually we will
-make our release updates after this)::
+Alternatively, if you have existing local changes to go "on top" of the latest
+code (usually we will make our release updates after this)::
 
     git rebase upstream/develop
 
@@ -84,11 +84,11 @@ Quick example to update libEnsemble
 This will open the libEnsemble ``package.py`` file in your editor (given by
 environment variable ``EDITOR``)::
 
-    spack edit py-libensemble  # SPACK_ROOT must be set (see above) (python packages use "py-" prefix)
+    spack edit py-libensemble  # SPACK_ROOT must be set (see above) (Python packages use "py-" prefix)
 
 Or just open it manually: ``var/spack/repos/builtin/packages/py-libensemble/package.py``.
 
-Now get checksum for new lines:
+Now get the checksum for new lines:
 
 Get the tarball (see PyPI instructions), for the new release and use::
 
@@ -102,7 +102,7 @@ Check package::
 
      spack style
 
-This will install a few python spack packages and run style checks on just
+This will install a few Python Spack packages and run style checks on just
 your changes. Make adjustments if needed, until this passes.
 
 If okay - add, commit, and push to origin (forked repo). For example, if your version
@@ -117,7 +117,7 @@ branch on the fork to the develop branch on the upstream.
 Express Summary: Make Fork Identical to Upstream
 ------------------------------------------------
 
-Quick summary for bringing develop branch on forked repo up to speed with upstream
+Quick summary for bringing the develop branch on a forked repo up to speed with upstream
 (YOU WILL LOSE ANY CHANGES)::
 
     git remote add upstream https://github.com/spack/spack.git

docs/platforms/platforms_index.rst

@@ -42,7 +42,7 @@ On systems with a job scheduler, libEnsemble is typically run within a single
 :doc:`job submission<example_scripts>`. All user simulations will run on
 the nodes within that allocation.
 
-*How does libensemble know where to run tasks (user applications)?*
+*How does libEnsemble know where to run tasks (user applications)?*
 
 The libEnsemble :doc:`Executor<../executor/ex_index>` can be initialized from the user calling
 script, and then used by workers to run tasks. The Executor will automatically detect the nodes