Clarify release process (#1202)

src/docs/sphinx/dev_guide/release.rst

@@ -88,7 +88,9 @@ release changes can be reviewed. Such changes include:
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Merge the release candidate branch into the main branch once it is ready and
-approved. At this point, the release candidate branch can be deleted.
+approved. Do not "squash merge:" that will make the histories of main and
+release branches disagree, and we want to preserve the history. After
+merging, the release candidate branch can be deleted.
 
 
 4: Draft a Github Release
@@ -120,8 +122,9 @@ approved. At this point, the release candidate branch can be deleted.
 ^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 * Checkout the main branch locally and run ``axom/scripts/make_release_tarball.sh --with-data``
-  This will generate a two tarballs of the form ``Axom-v0.3.1.tar.gz`` and ``AxomData-v0.3.1.tar.gz``
-  each consistsing of the axom source and data respectively.
+  Run this script from the top level ``axom`` subdirectory. This will
+  generate a two tarballs of the form ``Axom-v0.3.1.tar.gz`` and ``AxomData-v0.3.1.tar.gz``
+  consisting of the axom source and data respectively.
 
 * Upload the tarballs for the corresponding release, by going to the
   `Github Releases section <https://github.com/LLNL/axom/releases>`_ and ``Edit``