Fix markdown format with autoformatter (#1284)

1 files changed, 16 insertions, 16 deletions

diff --git a/doc/buildWithDocker.md b/doc/buildWithDocker.md
index 1bea8380..20bf85d4 100644
--- a/doc/buildWithDocker.md
+++ b/doc/buildWithDocker.md
@@ -1,24 +1,24 @@
 # Build the project using Docker
 
-A [Docker image (Dockerfile)](../docker) containing all the build environment is available for X86_64 and AMD64 architectures. 
+A [Docker image (Dockerfile)](../docker) containing all the build environment is available for X86_64 and AMD64 architectures.
 These images make the build of the firmware and the generation of the DFU file for OTA quite easy, as well as preventing clashes with any other toolchains or development environments you may have installed.
 
 Based on Ubuntu 22.04 with the following build dependencies:
 
-* ARM GCC Toolchain
-* nRF SDK
-* MCUBoot
-* adafruit-nrfutil
-* lv_font_conv
+- ARM GCC Toolchain
+- nRF SDK
+- MCUBoot
+- adafruit-nrfutil
+- lv_font_conv
 
 ## Run a container to build the project
 
-The `infinitime-build` image contains all the dependencies you need. 
+The `infinitime-build` image contains all the dependencies you need.
 The default `CMD` will compile sources found in `/sources`, so you need only mount your code.
 
 Before continuing, make sure you first build the image as indicated in the [Build the image](#build-the-image) section, or check the [Using the image from Docker Hub](#using-the-image-from-docker-hub) section if you prefer to use a pre-made image.
 
-This example will build the firmware, generate the MCUBoot image and generate the DFU file. 
+This example will build the firmware, generate the MCUBoot image and generate the DFU file.
 For cloning the repo, see [these instructions](../doc/buildAndProgram.md#clone-the-repo). Outputs will be written to **<project_root>/build/output**:
 
 ```bash
@@ -26,12 +26,12 @@ cd <project_root> # e.g. cd ./work/Pinetime
 docker run --rm -it -v ${PWD}:/sources --user $(id -u):$(id -g) infinitime-build
 ```
 
-By default, the container runs as `root`, which is not convenient as all the files generated by the build will also belong to `root`. 
-The parameter `--user` overrides that default behavior. 
-The command above will run as your current user. 
+By default, the container runs as `root`, which is not convenient as all the files generated by the build will also belong to `root`.
+The parameter `--user` overrides that default behavior.
+The command above will run as your current user.
 
-If you only want to build a single CMake target, you can pass it in as the first parameter to the build script. 
-This means calling the script explicitly as it will override the `CMD`. 
+If you only want to build a single CMake target, you can pass it in as the first parameter to the build script.
+This means calling the script explicitly as it will override the `CMD`.
 Here's an example for `pinetime-app`:
 
 ```bash
@@ -50,9 +50,9 @@ docker run --rm -it -v ${PWD}:/sources --user $(id -u):$(id -g) infinitime/infin
 
 The default `latest` tag *should* automatically identify the correct image architecture, but if for some reason Docker does not, you can specify it manually:
 
-* For AMD64 (x86_64) systems: `docker pull --platform linux/amd64 infinitime/infinitime-build`
+- For AMD64 (x86_64) systems: `docker pull --platform linux/amd64 infinitime/infinitime-build`
 
-* For ARM64v8 (ARM64/aarch64) systems: `docker pull --platform linux/arm64 infinitime/infinitime-build`
+- For ARM64v8 (ARM64/aarch64) systems: `docker pull --platform linux/arm64 infinitime/infinitime-build`
 
 ## Build the image
 
@@ -62,4 +62,4 @@ The following commands must be run from the root of the project. This operation
 
 ```bash
 docker build -t infinitime-build ./docker
-```
\ No newline at end of file
+```