diff --git a/.woodpecker/build.yaml b/.woodpecker/build.yaml
index b66dce6..bfdebe1 100644
--- a/.woodpecker/build.yaml
+++ b/.woodpecker/build.yaml
@@ -1,10 +1,10 @@
 when:
-  - event: push
-    branch: main
+    - event: push
+      branch: main
 
 steps:
-  - name: build
-    image: node:23-alpine3.20
-    commands:
-      - npm install
-      - npm run build
+    - name: build
+      image: node:23-alpine3.20
+      commands:
+          - npm install
+          - npm run build
diff --git a/src/content/posts/2024_11_07-umami.mdx b/src/content/posts/2024_11_07-umami.mdx
index 1e50847..5b215d4 100644
--- a/src/content/posts/2024_11_07-umami.mdx
+++ b/src/content/posts/2024_11_07-umami.mdx
@@ -17,8 +17,8 @@ import Note from "../../components/Note.astro";
 This little blog post thang will be about umami, and why I went with it over fixing my Plausible install. While the
 reason is pretty simple, really and can be summed up in two points.
 
-- Its resource usage is low
- - Has (nearly) all the features I used in Plausible
+-   Its resource usage is low
+-   Has (nearly) all the features I used in Plausible
 
 I want to talk a bit about how I got to the point where I chosen it, and the steps I've taken to actually install and
 setup an Alpine CT with itttt
@@ -60,7 +60,7 @@ Maybe I could pick it up in the future, and bring it back to life again
 <Note text="Blank sections are due to me not being able to find information on the feature" />
 
 |                               | Matomo | PostHog                    | umami                       | Fathom lite                  | Plausible                  |
-|-------------------------------|--------|----------------------------|-----------------------------|------------------------------|----------------------------|
+| ----------------------------- | ------ | -------------------------- | --------------------------- | ---------------------------- | -------------------------- |
 | Self-Hostable                 | Yes    | Yes                        | Yes                         | Yes [^fathom-self-host]      | Yes                        |
 | Hosting method                | PHP    | Docker                     | Node or Docker              | Go [^fathom-language]        | Docker                     |
 | GDPR compliant                | Yes    | Yes                        | Yes                         | No [^fathom-gdpr-compliance] | Yes                        |
@@ -118,6 +118,7 @@ apk add vim git
 
 I didn't reaaaaaly need caddy for this, as it would mean the service would be behind two proxies, but I wanted to setup
 caddy anyway. It was quite simple really
+
 ```bash
 apk add caddy
 rc-update add caddy
@@ -129,10 +130,12 @@ mkdir /var/www/html
 
 Then, in `/etc/caddy`, we edit the `Caddyfile`, use your favorite editor for this, but I like vim, so for me I would run
 `vim Caddyfile`. Then set the contents to the following
+
 ```caddyfile
 :8080
 reverse_proxy localhost:3000
 ```
+
 <Note text="3000 is the default port for yarn, but adjust for your needs" />
 
 And finally we just need to reload the service, still within `/etc/caddy`, with `caddy reload`!