From 36ef94c83ab2bfb2182ead0a84422f4fb24176fe Mon Sep 17 00:00:00 2001
From: Crizomb <crizomb@noreply.localhost>
Date: Thu, 25 Dec 2025 01:27:22 +0100
Subject: [PATCH] Update VMs/ForgejoRunner/README.md

---
 VMs/ForgejoRunner/README.md | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/VMs/ForgejoRunner/README.md b/VMs/ForgejoRunner/README.md
index 6db7b5b..c16c688 100644
--- a/VMs/ForgejoRunner/README.md
+++ b/VMs/ForgejoRunner/README.md
@@ -1,13 +1,12 @@
 # Forgejo runner setup
-Run forgejo runners instance inside a VM to do very dirty things but securely <br>
-The "dirty things" is just having forgejo running in priviliged container, with direct access to the host (VM) docker socket <br>
-Runners can easily get full access to host, but the host is a VM so it's ok <br>
-I use [incus](https://linuxcontainers.org/incus/) to create the VM. I love it, very simple, docker like interface <br>
-See launch_forgejo_runner_vm.sh for more information about the VM setup. <br>
+
+Run forgejo runners instance inside a VM to do very dirty things but securely. <br><br>
+The "dirty things" is just having forgejo running in priviliged container, with direct access to the host (VM) docker socket. <br><br>
+Runners can easily get full access to host, but the host is a VM so it's ok <br><br>
+I use [incus](https://linuxcontainers.org/incus/) to create the VM. I love it, very simple, docker like interface <br><br>
+See launch_forgejo_runner_vm.sh for more information about the VM setup. <br><br>
 
 
-
-
-To setup, you still need to enter VM, and follow forgejo [runner instalation guide](https://forgejo.org/docs/next/admin/actions/runner-installation/) <br>
+To setup, you still need to enter VM, and follow forgejo [runner instalation guide](https://forgejo.org/docs/next/admin/actions/runner-installation/) <br><br>
 It's still a little bit manual, but it's done in 30s
  
\ No newline at end of file