A few additional subjective improvements to readability

Signed-off-by: Alec Scott <alec@llnl.gov>

Author: alecbcs

tutorial_environments.rst

@@ -19,8 +19,8 @@ So far in this tutorial, we've covered the basic commands for managing individua
 .. Customizing Spack's installation with configuration files, like
    `packages.yaml <https://spack.readthedocs.io/en/latest/build_settings.html#build-settings>`_, was also discussed.
 
-Now we'll explore Spack Environments, a powerful feature that lets us manage collections of packages together in a documented and reproducible way.
-Spack environments are similar to *virtual environments* in other package managers (e.g., `Python venv <https://docs.python.org/3/library/venv.html>`_, `Conda Environments <https://docs.conda.io/projects/conda/en/stable/user-guide/getting-started.html>`_, or `nix-env <https://nix.dev/manual/nix/2.24/command-ref/nix-env>`_).
+Now we'll explore Spack environments, a powerful feature that lets us manage collections of packages together in a documented and reproducible way.
+Spack environments are similar to *virtual environments* in other package managers (e.g., `Python venv <https://docs.python.org/3/library/venv.html>`_, `Conda environments <https://docs.conda.io/projects/conda/en/stable/user-guide/getting-started.html>`_, or `nix-env <https://nix.dev/manual/nix/2.24/command-ref/nix-env>`_).
 
 Managing a software stack with many packages and varying configuration can quickly become hard to track by hand.
 An environment lets you:

tutorial_packaging.rst

@@ -182,7 +182,7 @@ Let's make the following changes:
 
 Now make the changes and additions to your ``package.py`` file.
 
-The resulting package should contain -- sans the copyright and license -- the following information:
+The resulting package should contain the following information, omitting the copyright and license:
 
 .. literalinclude:: tutorial/examples/packaging/1.package.py
    :caption: tutorial-mpileaks/package.py (from tutorial/examples/packaging/1.package.py)

tutorial_stacks.rst

@@ -20,6 +20,7 @@ Our goal is to install ``netlib-scalapack`` compiled with ``gcc@16``, which is n
 
 - two MPI libraries (``openmpi`` and ``mpich``)
 - two LAPACK providers (``openblas`` and ``netlib-lapack``)
+
 We'll also install ``py-scipy`` linked against ``openblas``.
 
 We'll first focus on how to configure and install the software correctly.
@@ -79,7 +80,7 @@ Spec groups offer a better tool: the ``override`` block, which scopes any Spack
    :language: yaml
    :emphasize-lines: 11-18,23-30
 
-Here we used it to set compiler preferences at the language level, once for each group:
+Here we used the ``override`` block to set compiler preferences at the language level, once for each group:
 
 1. The ``compiler`` group prefers ``gcc@15``
 2. The ``stack`` group prefers ``gcc@16``
@@ -282,7 +283,7 @@ Alternatively, to create a buildcache you can:
    $ spack gpg create <name> <e-mail>
    $ spack buildcache push ./mirror
 
-Don't forget to set an appropriate value for the padding of the install tree, see `how to setup relocation <https://spack.readthedocs.io/en/latest/binary_caches.html#relocation>`_ in our documentation.
+Don't forget to set an appropriate value for the padding of the install tree; see `how to set up relocation <https://spack.readthedocs.io/en/latest/binary_caches.html#relocation>`_ in our documentation.
 
 --------------------------
 Multiple Filesystem Views
@@ -372,7 +373,7 @@ Let's check the generated module files:
    :language: console
 
 The set of modules is already usable, and the hierarchy already works.
-For instance, we can load the ``gcc`` compiler and check that we have ``gcc`` in our path and a lot of modules available, all compiled with ``gcc@16``:
+For instance, we can load the ``gcc`` compiler and check that ``gcc`` is in our path and that many modules are available, all compiled with ``gcc@16``:
 
 .. literalinclude:: outputs/stacks/modules-3.out
    :language: console