Fix more block quotes

Author: alecbcs

tutorial_binary_cache.rst

@@ -116,9 +116,9 @@ look very similar to a container image --- we will get to that in a bit.
    You can change the visibility to ``public`` by going to GitHub Packages from your GitHub account, selecting the ``buildcache`` package, go to ``package settings``, and change the visibility to ``public`` in the ``Danger Zone`` section.
    This page can also be directly accessed by going to
 
-      .. code-block:: text
+   .. code-block:: text
 
-         https://github.com/users/<user>/packages/container/buildcache/settings
+      https://github.com/users/<user>/packages/container/buildcache/settings
 
 
 -------------------------------

tutorial_buildsystems.rst

@@ -163,9 +163,9 @@ These packages are handled by the ``MakefilePackage`` subclass which provides co
 
 A ``MakefilePackage`` build has three phases that can be overridden by the packager:
 
-    1. ``edit()``
-    2. ``build()``
-    3. ``install()``
+1. ``edit()``
+2. ``build()``
+3. ``install()``
 
 Packagers then have the ability to control how a ``Makefile`` is edited, and what targets to include for the build phase or install phase.
 

tutorial_developer_workflows.rst

@@ -285,22 +285,22 @@ This command is particularly useful in developer environments—it allows develo
 The additional features of the install command are unnecessary when tightly iterating between building and testing a particular package.
 For example, the workflow modifying ``scr`` that we just went through can be simplified to:
 
- .. code-block:: console
-
-    $ spack build-env scr -- bash
-    # Shell wrappers didn't propagate to the subshell
-    $ source $SPACK_ROOT/share/spack/setup-env.sh
-    # Lets look at navigation features
-    $ spack cd --help
-    $ spack cd -c scr
-    $ touch src/scr_copy.c
-    $ spack cd -b scr
-    # Lets look at whats here
-    $ ls
-    # Build and run tests
-    $ make -j2
-    $ make test
-    $ exit
+.. code-block:: console
+
+   $ spack build-env scr -- bash
+   # Shell wrappers didn't propagate to the subshell
+   $ source $SPACK_ROOT/share/spack/setup-env.sh
+   # Lets look at navigation features
+   $ spack cd --help
+   $ spack cd -c scr
+   $ touch src/scr_copy.c
+   $ spack cd -b scr
+   # Lets look at whats here
+   $ ls
+   # Build and run tests
+   $ make -j2
+   $ make test
+   $ exit
 
 Working with the build environment and along with Spack navigation features provides a nice way to iterate quickly and navigate through the hash-heavy Spack directory structures.
 
@@ -314,13 +314,13 @@ Developers can achieve builds of both cases from a single ``spack install`` as l
 
 .. code-block:: console
 
-   # First we have to allow repeat specs in the environment
-   $ spack config add concretizer:unify:false
-   # Next we need to specify the specs we want ('==' propagates the variant to deps)
-   $ spack change macsio build_type==Release
-   $ spack add macsio+scr build_type==Debug
-   # Inspect the graph for multiple dev_path=
-   $ spack concretize -f
+  # First we have to allow repeat specs in the environment
+  $ spack config add concretizer:unify:false
+  # Next we need to specify the specs we want ('==' propagates the variant to deps)
+  $ spack change macsio build_type==Release
+  $ spack add macsio+scr build_type==Debug
+  # Inspect the graph for multiple dev_path=
+  $ spack concretize -f
 
 While we won't build out this example it illustrates how the ``dev_path`` for ``build_type=Release`` and ``build_type=Debug`` points to the same source code.
 

tutorial_modules.rst

@@ -15,10 +15,10 @@ Both hierarchical and non-hierarchical deployments will be discussed in detail a
 
 At the end of the tutorial readers should have a clear understanding of:
 
-  * What module files are and how they are used on HPC clusters
-  * How Spack generates module files for the software it installs
-  * Which Spack commands can be used to manage module files
-  * How module files generated by Spack can be customized
+* What module files are and how they are used on HPC clusters
+* How Spack generates module files for the software it installs
+* Which Spack commands can be used to manage module files
+* How module files generated by Spack can be customized
 
 and be confident that Spack can deal with all of the common use cases that occur when maintaining software installations on HPC clusters.