apply prettier

docs/docs/20-usage/15-terminiology/index.md

@@ -41,11 +41,12 @@ Sometimes there are multiple terms that can be used to describe something. This
 - Use the term **steps** instead of the previous **jobs**
 
 <!-- References -->
-[Pipeline]:  ../20-workflow-syntax.md
-[Workflow]:  ../25-workflows.md
-[Forge]:     ../../30-administration/11-forges/10-overview.md
-[Plugin]:    ../51-plugins/10-plugins.md
+
+[Pipeline]: ../20-workflow-syntax.md
+[Workflow]: ../25-workflows.md
+[Forge]: ../../30-administration/11-forges/10-overview.md
+[Plugin]: ../51-plugins/10-plugins.md
 [Workspace]: ../20-workflow-syntax.md#workspace
-[Matrix]:    ../30-matrix-workflows.md
-[Docker]:    ../../30-administration/22-backends/10-docker.md
-[Local]:     ../../30-administration/22-backends/20-local.md
+[Matrix]: ../30-matrix-workflows.md
+[Docker]: ../../30-administration/22-backends/10-docker.md
+[Local]: ../../30-administration/22-backends/20-local.md

docs/docs/20-usage/41-registries.md

@@ -67,5 +67,3 @@ steps:
     commands:
       - ./build.sh
 ```
-
-

docs/docs/20-usage/90-advanced-usage.md

@@ -108,8 +108,8 @@ steps:
   init:
     image: bash
     commands:
-      echo "FOO=hello" >> envvars
-      echo "BAR=world" >> envvars
+      - echo "FOO=hello" >> envvars
+      - echo "BAR=world" >> envvars
 
   debug:
     image: bash

docs/docs/30-administration/00-deployment/00-overview.md

@@ -24,7 +24,7 @@ Below are minimal resources requirements for Woodpecker components itself:
 | Component | Memory | CPU |
 | --------- | ------ | --- |
 | Server    | 200 MB | 1   |
-| Agent     |  32 MB | 1   |
+| Agent     | 32 MB  | 1   |
 
 Note, that those values do not include the operating system or workload (pipelines execution) resources consumption.
 

docs/docs/30-administration/00-deployment/10-docker-compose.md

@@ -139,7 +139,7 @@ Image variants:
 - The `vX.X` images are based on the current release branch (e.g. `release/v1.0`) and can be used to get bugfixes asap
 - The `next` images are based on the current `main` branch and should not be used for production environments
 
-``` bash
+```bash
 # server
 docker pull woodpeckerci/woodpecker-server:latest
 docker pull woodpeckerci/woodpecker-server:latest-alpine

docs/docs/30-administration/00-deployment/20-kubernetes.md

@@ -7,4 +7,3 @@ The chart contains two subcharts, `server` and `agent` which are automatically c
 The chart started off with two independent charts but was merged into one to simplify the deployment at start of 2023.
 
 A couple of backend-specific config env vars exists which are described in the [kubernetes backend docs](../22-backends/40-kubernetes.md).
-

docs/docs/30-administration/11-forges/10-overview.md

@@ -2,11 +2,11 @@
 
 ## Supported features
 
-| Feature | [GitHub](github/) | [Gitea / Forgejo](gitea/) | [Gitlab](gitlab/) | [Bitbucket](bitbucket/) |
-| --- | :---: | :---: | :---: | :---: |
-| Event: Push | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
-| Event: Tag | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
-| Event: Pull-Request | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
-| Event: Deploy | :white_check_mark: | :x: | :x: | :x: |
-| [Multiple workflows](../../20-usage/25-workflows.md) | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
-| [when.path filter](../../20-usage/20-workflow-syntax.md#path) | :white_check_mark: | :white_check_mark: | :white_check_mark: | :x: |
+| Feature                                                       | [GitHub](github/)  | [Gitea / Forgejo](gitea/) | [Gitlab](gitlab/)  | [Bitbucket](bitbucket/) |
+| ------------------------------------------------------------- | :----------------: | :-----------------------: | :----------------: | :---------------------: |
+| Event: Push                                                   | :white_check_mark: |    :white_check_mark:     | :white_check_mark: |   :white_check_mark:    |
+| Event: Tag                                                    | :white_check_mark: |    :white_check_mark:     | :white_check_mark: |   :white_check_mark:    |
+| Event: Pull-Request                                           | :white_check_mark: |    :white_check_mark:     | :white_check_mark: |   :white_check_mark:    |
+| Event: Deploy                                                 | :white_check_mark: |            :x:            |        :x:         |           :x:           |
+| [Multiple workflows](../../20-usage/25-workflows.md)          | :white_check_mark: |    :white_check_mark:     | :white_check_mark: |   :white_check_mark:    |
+| [when.path filter](../../20-usage/20-workflow-syntax.md#path) | :white_check_mark: |    :white_check_mark:     | :white_check_mark: |           :x:           |

docs/docs/30-administration/40-encryption.md

@@ -4,10 +4,11 @@
 Secrets encryption is currently broken and therefore disabled by default. It will be fixed in an upcoming release.
 
 Check:
+
 - https://github.com/woodpecker-ci/woodpecker/issues/1541 and
 - https://github.com/woodpecker-ci/woodpecker/pull/2300
-:::
 
+:::
 
 By default, Woodpecker does not encrypt secrets in its database. You can enable encryption
 using simple AES key or more advanced [Google TINK](https://developers.google.com/tink) encryption.