Start new sentences on a new line in markdown

docs/using/running.md

@@ -116,7 +116,8 @@ docker rm notebook
 
 ## Using the Podman CLI
 
-An alternative to using the Docker CLI is to use the Podman CLI. Podman is mostly compatible with Docker.
+An alternative to using the Docker CLI is to use the Podman CLI.
+Podman is mostly compatible with Docker.
 
 ### Podman example
 

docs/using/selecting.md

@@ -249,7 +249,8 @@ Whenever a docker image is pushed to the container registry, it is tagged with:
 - a set of software version tags like `python-3.10.8` and `lab-3.5.3`
 
 ```{warning}
-- Tags before `2022-07-05` were sometimes incorrect. Please, do not rely on them.
+- Tags before `2022-07-05` were sometimes incorrect.
+  Please, do not rely on them.
 - Single-platform images have either `aarch64` or `x86_64` tag prefixes, for example, `jupyter/base-notebook:aarch64-python-3.10.5`
 ```
 

tagging/README.md

@@ -12,10 +12,12 @@ For example, we dump all the `conda` packages, including their versions.
 
 ## Main principles
 
-- All the images are located in a hierarchical tree. More info on [image relationships](../docs/using/selecting.md#image-relationships).
+- All the images are located in a hierarchical tree.
+  More info on [image relationships](../docs/using/selecting.md#image-relationships).
 - We have `tagger` and `manifest` classes, which can be run inside docker containers to obtain tags and build manifest pieces.
 - These classes are inherited from the parent image to all the children images.
-- Because manifests and tags might change from parent to children, `taggers` and `manifests` are reevaluated on each image. So, the values are not inherited.
+- Because manifests and tags might change from parent to children, `taggers` and `manifests` are reevaluated on each image.
+  So, the values are not inherited.
 - To tag an image and create a manifest, run `make hook/base-notebook` (or another image of your choice).
 
 ## Source code description