Updated line spacing in rst files.

doc/changes/DM-28653.feature.rst

@@ -32,10 +32,13 @@
 
 * With the above defaults one can more easily append options to the
   pipetask command lines as variables in submit yaml:
+
   * extraQgraphOptions: Adds given string to end of command line for
     creating QuantumGraph (e.g., for specifying a task wit -t)
+
   * extraInitOptions: Adds given string to end of pipetaskInit
     command line
+
   * extraRunQuantumOptions: Adds given string to end of the pipetask
     command line for running a Quantum (e.g., "--no-versions")
 
@@ -67,22 +70,25 @@
   defaults and submit yaml (<run>_config.yaml).
 
 * If pipetask starts reporting errors about database connections
-(e.g., remaining connection slots are reserved for non-replication
-superuser connections) ask on #dm-middleware-support about
-using execution butler in bps.  This greatly reduces the number of
-connections to the central database per run.  It is not yet the default
-behavior of bps, but one can modify the submit yaml to use it.  See
-${CTRL_BPS_DIR}/doc/lsst.ctrl.bps/pipelines_check_execution_butler.yaml
+  (e.g., remaining connection slots are reserved for non-replication
+  superuser connections) ask on #dm-middleware-support about
+  using execution butler in bps.  This greatly reduces the number of
+  connections to the central database per run.  It is not yet the default
+  behavior of bps, but one can modify the submit yaml to use it.  See
+  ${CTRL_BPS_DIR}/doc/lsst.ctrl.bps/pipelines_check_execution_butler.yaml
 
 The major differences visible to users are:
+
 * bps report shows new job called mergeExecutionButler in detailed view.
   This is what saves the run info into the central butler repository.
   As with any job, it can succeed or fail.  Different from other jobs, it
   will execute at the end of a run regardless of whether a job failed or
   not.  It will even execute if the run is cancelled unless the cancellation
   is while the merge is running.  Its output will go where other jobs go (at
   NCSA in jobs/mergeExecutionButler directory).
+
 * See new files in submit directory:
+
   * EXEC_REPO-<run>:  Execution butler (yaml + initial sqlite file)
   * execution_butler_creation.out: output of command to create execution butler
   * final_job.bash:  Script that is executed to do the merging of the run info into the central repo.

doc/changes/DM-29893.feature.rst

@@ -1,6 +1,8 @@
 * bps report
+
   * Columns now are as wide as the widest value/heading
     and some other minor formatting changes.
+
   * Detailed report (--id) now has an Expected column
     that shows expected counts per PipelineTask label
     from the QuantumGraph.