[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

docs/source/use/community-image.md

@@ -6,6 +6,7 @@ In this case, you won't have to maintain anything -- you'll simply use a communi
 Here are some steps to follow.
 
 ## First, find a community-maintained image for your workflow
+
 Many communities define their own user envionment images for re-use. Here are a few to look into:
 
 1. [jupyter Docker-stacks](https://jupyter-docker-stacks.readthedocs.io/) has a number of user images for general data science workflows.

docs/source/use/extend-community-image.md

@@ -30,7 +30,7 @@ A local `Dockerfile` does the following things:
 - Copies your local `environment.yml` file into a directory in the image.
 - Updates the `conda` environment with it to install the extra packages.
 
- For example, the following inherits the `scipy-notebook` image with the `2023-05-01` tag and takes the above steps. (you could follow a similar workflow with other package managers).
+For example, the following inherits the `scipy-notebook` image with the `2023-05-01` tag and takes the above steps. (you could follow a similar workflow with other package managers).
 
 ```{code-block} Dockerfile
 :caption: Dockerfile

docs/source/use/pathways.md

@@ -3,6 +3,7 @@
 Many users of `repo2docker` primarily wish to define the environment for a Binder or a JupyterHub. Here are four ways to accomplish this, from least-to-most work.
 
 % TO EDIT THIS FIGURE: Load the linked SVG into excalidraw.com, make edits, and re-export.
+
 ```{figure} ../_static/images/whentouse.svg
 A decision tree for the recommended way to get your reproducible user environment using `repo2docker` or a community image built with `repo2docker`.
 ```