RTD update: Move "which kpp" to end of "Build the KPP executable" section

docs/source/getting-started/01_installation.rst
- @lizziel pointed out that the installation instructions ask the user
  to type "which kpp" before the KPP executable is built.  We have now
  moved the "which kpp" command to the end of the "Build the KPP
  executable" section"

Signed-off-by: Bob Yantosca <[email protected]>

Author: yantosca

CHANGELOG.md

@@ -19,6 +19,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 - Updated ReadTheDocs documentation to reflect that C-I tests are now done as a GitHub Action
 
+## Fixed
+- Moved the `which kpp` instruction to the end of the "Build the KPP executable" section in the installation guide on ReadTheDocs
+
 ### Removed
 - Removed C-I tests on Microsoft Azure Dev Pipelines
 

docs/source/getting_started/01_installation.rst

@@ -56,15 +56,6 @@ and then apply the settings with:
 
    $ source $HOME/.bashrc
 
-Now if you type:
-
-.. code-block:: console
-
-   $ which kpp
-
-the path to the executable file (:file:`kpp`) will be displayed. This
-path should match the path specified by :file:`$KPP_HOME/bin/kpp`.
-
 .. _test-for-dependencies:
 
 =====================================================
@@ -248,6 +239,15 @@ You should see output similar to:
 
 This will create the executable file :file:`$KPP_HOME/bin/kpp`.
 
+Now if you type:
+
+.. code-block:: console
+
+   $ which kpp
+
+the path to the executable file (:file:`kpp`) will be displayed. This
+path should match the path specified by :file:`$KPP_HOME/bin/kpp`.
+
 .. _additional-steps-macosx:
 
 ==============================