docs: fix docutils related bug (spack#50941)

Author: haampie

lib/spack/docs/containers.rst

@@ -755,9 +755,9 @@ to customize the generation of container recipes:
 Best Practices
 ~~~~~~~~~~~~~~
 
-"""
+""""""
 MPI
-"""
+""""""
 Due to the dependency on Fortran for OpenMPI, which is the Spack default
 implementation, consider adding ``gfortran`` to the ``apt-get install`` list.
 
@@ -768,9 +768,9 @@ For execution on HPC clusters, it can be helpful to import the Docker
 image into Singularity in order to start a program with an *external*
 MPI. Otherwise, also add ``openssh-server`` to the ``apt-get install`` list.
 
-""""
+""""""
 CUDA
-""""
+""""""
 Starting from CUDA 9.0, NVIDIA provides minimal CUDA images based on
 Ubuntu. Please see `their instructions <https://hub.docker.com/r/nvidia/cuda/>`_.
 Avoid double-installing CUDA by adding, e.g.:

lib/spack/docs/getting_started.rst

@@ -659,9 +659,9 @@ compilers:
 Intel compilers may therefore be configured in one of two ways with
 Spack: using modules, or using compiler flags.
 
-^^^
+^^^^^^
 NAG
-^^^
+^^^^^^
 
 The Numerical Algorithms Group provides a licensed Fortran compiler.
 It is recommended to use GCC for your C/C++ compilers.
@@ -769,9 +769,9 @@ For example, to use an OpenMPI installed in /opt/local, you would use:
 In general, *Spack is easier to use and more reliable if it builds all of its own dependencies*.
 However, there are several packages for which one commonly needs to use system versions:
 
-^^^
+^^^^^^
 MPI
-^^^
+^^^^^^
 
 On supercomputers, sysadmins have already built MPI versions that take
 into account the specifics of that computer's hardware.  Unless you
@@ -862,9 +862,9 @@ to add the following to ``packages.yaml``:
    from other dependencies. This ensures that binaries in Spack dependencies
    are preferred over system binaries.
 
-^^^
+^^^^^^
 Git
-^^^
+^^^^^^
 
 Some Spack packages use ``git`` to download, which might not work on
 some computers.  For example, the following error was
@@ -1279,9 +1279,9 @@ to your ``PATH`` in this case.
 .. note::
    Spack currently supports Python versions later than 3.2 inclusive.
 
-"""
+""""""
 Git
-"""
+""""""
 
 A bash console and GUI can be downloaded from https://git-scm.com/downloads.
 If you are unfamiliar with Git, there are a myriad of resources online to help
@@ -1296,9 +1296,9 @@ as the project providing Git support on Windows. This is additionally the recomm
 for installing Git on Windows, a link to which can be found above. Spack requires the
 utilities vendored by this project.
 
-"""
+""""""
 7zip
-"""
+""""""
 
 A tool for extracting ``.xz`` files is required for extracting source tarballs. The latest 7-Zip
 can be located at https://sourceforge.net/projects/sevenzip/.

lib/spack/docs/pipelines.rst

@@ -760,9 +760,9 @@ informing the user what broken specs were encountered. This allows the pipeline
 to fail early and avoid wasting compute resources attempting to build packages
 that will not succeed.
 
-^^^^^
+^^^^^^
 CDash
-^^^^^
+^^^^^^
 
 The optional ``cdash`` section provides information that will be used by the
 ``spack ci generate`` command (invoked by ``spack ci start``) for reporting

lib/spack/docs/replace_conda_homebrew.rst

@@ -14,9 +14,9 @@ installed packages are symlinked to a single central location like ``/usr/local`
 In this section, we will show you how to emulate the behavior of Homebrew/Conda
 using :ref:`environments`!
 
------
+------
 Setup
------
+------
 
 First, let's create a new environment. We'll assume that Spack is already set up
 correctly, and that you've already sourced the setup script for your shell.