chore(deps): update dependency prettier to v3.6.2 (#686)

Co-authored-by: woodpecker-bot <woodpecker-bot@obermui.de>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/686
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>

.woodpecker/lint.yaml

@@ -21,7 +21,7 @@ steps:
     depends_on: []
     settings:
       # renovate: datasource=npm depName=prettier
-      version: 3.2.5
+      version: 3.6.2
 
   links:
     image: lycheeverse/lychee:0.15.1

content/ci/agents.md

@@ -24,10 +24,8 @@ Before deploying the agent, you need to obtain an agent token from Codeberg's Wo
 To do so, please follow the instructions immediately below for users, and follow the instructions below that for organizations.
 
 1. Go to the agents page
-
    1. For users, go to the [Codeberg Woodpecker CI User Agent settings](https://ci.codeberg.org/user/agents)
    2. For organizations:
-
       1. Go to the [Codeberg Woodpecker CI Repos Page](https://ci.codeberg.org/)
       2. Click on a repository in the organization you're adding the agent to.
       3. Click on the organization name in the top left.

content/codeberg-pages/using-custom-domain.md

@@ -22,7 +22,6 @@ For custom domains, two things are required:
 - a `.domains` file in the repository and branch where your files reside which you want to publish via Codeberg Pages.
   The file should contain a list of _all_ domains that shall be usable to access that repository,
   according to the following rules:
-
   - One domain per line, you can leave lines empty and comment out lines with `#`.
   - The first domain is the main domain, all other domains in the file will be redirected to the first one.
   - The rest of the list includes all relevant `*.codeberg.page` domains for the specific repository.
@@ -246,11 +245,9 @@ pages.pages.frida.codeberg.page
 For the DNS configuration:
 
 - if CNAME can be used, one single DNS record will suffice:
-
   - name `myself.example.com`, type `CNAME`, data `frida.codeberg.page`
 
 - otherwise, if ALIAS can be used, two DNS records will be needed:
-
   - name `myself.example.com`, type `ALIAS`, data `codeberg.page`
   - name `myself.example.com`, type `TXT`, data `frida.codeberg.page`
 
@@ -275,7 +272,6 @@ pages.pages.frida.codeberg.page
 For the DNS configuration, the CNAME SHOULD NOT be used, so:
 
 - if ALIAS can be used, two DNS records will be needed:
-
   - name `example.com`, type `ALIAS`, data `codeberg.page`
   - name `example.com`, type `TXT`, data `frida.codeberg.page`
 
@@ -299,11 +295,9 @@ pages.colormix.frida.codeberg.page
 For the DNS configuration:
 
 - if CNAME can be used, one single DNS record will suffice:
-
   - name `colormix-app.example.com`, type `CNAME`, data `colormix.frida.codeberg.page`
 
 - otherwise, if ALIAS can be used, two DNS records will be needed:
-
   - name `colormix-app.example.com`, type `ALIAS`, data `codeberg.page`
   - name `colormix-app.example.com`, type `TXT`, data `colormix.frida.codeberg.page`
 
@@ -334,7 +328,6 @@ pages.colormix.frida.codeberg.page
 For the DNS configuration, CNAME SHOULD NOT be used:
 
 - if ALIAS can be used, two DNS records will be needed:
-
   - name `example.com`, type `ALIAS`, data `codeberg.page`
   - name `example.com`, type `TXT`, data `colormix.frida.codeberg.page`
 

content/integrations/matrix.md

@@ -45,7 +45,6 @@ Now we will connect the Matrix bot to your Codeberg repository. You will need ad
 2. Navigate to the `Webhooks` settings tab.
 3. Click on the `Add Webhook` button and select `Matrix`.
 4. Here are explanations for some key fields:
-
    - Homeserver URL: for example `https://matrix.org`
    - Room ID: for example `!VTjWrzxSWgLJnHgDUd:matrix.org`.
      You can find this on Element in the `Advanced` tab for the room settings.

content/security/ssh-key.md

@@ -34,7 +34,6 @@ your laptop and your office PC you should generate separate keys for each machin
    ```
 
    If you see that `/home/knut/.ssh/id_ed25519 already exists`, follow these steps:
-
    1. When prompted to overwrite the existing file, type <kbd>n</kbd> to choose not to overwrite.
 
    2. Afterward, re-run the same command: