ending with developer

Author: enriqueartal

src/doc/en/developer/downstream.rst

@@ -5,10 +5,6 @@ Packaging SageMath Downstream
 This document is intended for downstream maintainers (e.g., Linux distribution
 package maintainers) who wish to create redistributable builds of Sage.
 
-.. contents::
-   :local:
-   :depth: 2
-
 Dependencies
 ============
 
@@ -44,29 +40,27 @@ Build Procedure
         $ git clone https://github.com/sagemath/sage.git
 
     Alternatively, download the sdist tarball from the
-    `SageMath PyPI project<https://pypi.org/project/sagemath/>`_ or from the
+    `SageMath PyPI project <https://pypi.org/project/sagemath/>`_ or from the
     `GitHub releases <https://github.com/sagemath/sage/releases>`_.
 
 2. **Prepare the Build Environment**:
     Ensure a clean and consistent build environment with access to all
     required system libraries and Python packages.
 
 3. **Build**:
-
     Create a wheel using the ``build`` module:
 
     .. code-block:: console
 
         $ python -m build --wheel --no-isolation
 
     If you are sure that all dependencies are available, you may also add the
-    `--skip-dependency-check` option.
+    ``--skip-dependency-check`` option.
     Moreover, if you care about reproducible builds, it is recommended to
-    use `-Cbuild-dir=build` to specify a build directory, see this
+    use ``-Cbuild-dir=build`` to specify a build directory, see this
     `Meson-Python issue <https://github.com/mesonbuild/meson-python/issues/671>`_.
 
 4. **Install**:
-
     The resulting wheel can be installed using
 
     .. code-block:: console
@@ -77,7 +71,6 @@ Build Procedure
     (usually a temporary directory for packaging).
 
 4. **Test the Build**:
-
     Run the Sage tests to ensure functionality:
 
     .. code-block:: console

src/doc/en/developer/git_advanced.rst

@@ -253,8 +253,7 @@ top of that, deleted a file and committed that
     $ git commit -m "I shot myself into my foot"
 
 Now we cannot just checkout the repository from before the reset,
-because it is no longer in the history. However, here is the reflog::
-
+because it is no longer in the history. However, here is the reflog
 
 .. code-block:: console
 

src/doc/en/developer/packaging_sage_library.rst

@@ -143,17 +143,17 @@ The source directory of a distribution package, such as
   source files.  Sage provides a tool ``sage --fixdistributions``
   that assists with this task. For example
 
-.. code-block:: console
+  .. code-block:: console
 
-    $ ./sage --fixdistributions --set sagemath-polyhedra \
-         src/sage/geometry/polyhedron/base*.py
+      $ ./sage --fixdistributions --set sagemath-polyhedra \
+          src/sage/geometry/polyhedron/base*.py
 
   adds or updates the directives in the specified files; and
 
-.. code-block:: console
+  .. code-block:: console
 
-    $ ./sage --fixdistributions --add sagemath-polyhedra \
-         src/sage/geometry/polyhedron
+      $ ./sage --fixdistributions --add sagemath-polyhedra \
+          src/sage/geometry/polyhedron
 
   adds the directive to all files in the given directory that do not
   include a directive yet.

src/doc/en/developer/portability_testing.rst

@@ -388,7 +388,7 @@ this is slightly simplified
     # Automatically generated by write-dockerfile.sh
     # the :comments: separate the generated file into sections
     # to simplify writing scripts that customize this file
-  ...
+    ...
 
 First, it instructs ``docker build`` to start from an existing base
 image...::

src/doc/en/developer/walkthrough.rst

@@ -38,7 +38,7 @@ If you are in a hurry, you can skip the details and just follow these steps:
        $ conda env create --file environment-3.12-linux.yml --name sage-dev
        $ conda activate sage-dev
 
-    Replace ``environment-3.12-linux.yml`` with the appropriate file for your system.
+   Replace ``environment-3.12-linux.yml`` with the appropriate file for your system.
 
 5. Build and install Sage