diff --git a/blog/2026-01-02-foss-recap-2025.md b/blog/2026-01-02-foss-recap-2025.md
index cffb851..a993cc0 100644
--- a/blog/2026-01-02-foss-recap-2025.md
+++ b/blog/2026-01-02-foss-recap-2025.md
@@ -2,6 +2,8 @@
 
 # FOSS Recap 2025
 
+<hr>
+
 Following many other developpers, here is a recap of all the noticeable FOSS related projects that I have contributed to in 2025.
 
 ## Alpine Linux
diff --git a/guides/gaming-vm-on-qubes-using-bazzite.mdwn b/guides/gaming-vm-on-qubes-using-bazzite.mdwn
index 5eaff00..2d9b684 100644
--- a/guides/gaming-vm-on-qubes-using-bazzite.mdwn
+++ b/guides/gaming-vm-on-qubes-using-bazzite.mdwn
@@ -2,6 +2,8 @@
 
 # Gaming VM on Qubes Using Bazzite
 
+<hr>
+
 My main workstation now uses QubesOS rather than Proxmox. This workstation has two GPUs and two USB controllers. I wanted to be able to assign the more powerful GPU to a Gaming Qubes, but Qubes doesn't support that well. On top of that, the Sapphire Pulse 6700XT GPU that I have has [the AMD reset bug](https://forum.level1techs.com/t/6700xt-reset-bug/181814). To seamlessly be able to shutdown and assign the GPU to another VM (say my video editing environment), I applied a workaround that involved flashing a BIOS from another (working) 6700XT model (the Sapphire Nitro+ 6700XT). This solved the issue, at the cost of having to apply the original romfile on VM start. While this is easy on Proxmox (via `romfile` options), it isn't so easy on Qubes.
 
 I have ressources down at the bottom one can refer to for more information. In any case, lets start the guide.