diff --git a/projects/proxmox/index.md b/projects/proxmox/index.md
index 7c9029d..e87f506 100644
--- a/projects/proxmox/index.md
+++ b/projects/proxmox/index.md
@@ -8,29 +8,15 @@ lastmod: '2026-04-11'
 tags: ['virtualization', 'self-hosted', 'linux', 'kvm', 'lxc']
 ---
 
-## What is Proxmox VE?
+## What is Proxmox?
 
 Proxmox Virtual Environment (VE) is a powerful, open-source Bare-metal Hypervisor / virtualization management platform. It integrates two virtualization technologies—Kernel-based Virtual Machine (KVM) for virtual machines and Linux Containers (LXC) for lightweight container-based virtualization—into a single, easy-to-manage solution with a web-based interface.
 
-### Pros and Cons
+> [!NOTE] I actually set this up a while ago, just now getting around to document things. I have run a few itterations of proxmox, the current is my main compute note in my setup hosting most of my docker containers, game-servers, dns resolver / sink etc.
 
-#### Pros
-
--   **Open-Source and Free:** Proxmox VE is completely free to download and use, making it a cost-effective solution for both home labs and enterprise environments.
--   **Integrated Solution:** It combines KVM and LXC, offering the flexibility to run full virtual machines or lightweight containers on the same host.
--   **Web-Based Management:** The intuitive web interface allows for easy management of VMs, containers, storage, and networking without needing to use the command line for most tasks.
--   **Rich Feature Set:** It includes enterprise-grade features like high availability (HA) clustering, live migration, software-defined storage (like Ceph and ZFS), and robust backup/restore capabilities out of the box.
-
-#### Cons
-
--   **Learning Curve:** For beginners, the initial setup and understanding of its advanced networking and storage options can have a steeper learning curve compared to some commercial alternatives.
--   **Community-Based Support:** While the community support is strong, professional, enterprise-level support requires a paid subscription.
--   **Hardware Compatibility:** While it supports a wide range of hardware, specific or very new components might lack immediate driver support.
-
- 
 ---
 
-## When choosing CPU for VM...
+## When choosing CPU...
 
 Currently I am running `Proxmox > Ubuntu VM > code-server` for a nice CitC (client in the cloud) like interface I can use to access my projects / documentation and code from anywhere. Had some issues when I wanted to integrate gemini code assistant extension into my code-server instance. 
 
@@ -40,7 +26,7 @@ Currently I am running `Proxmox > Ubuntu VM > code-server` for a nice CitC (clie
 
 This is generally only a problem when you are creating a vm for the first time, so when making a vm; consider its uses and if it would make sense to not use the default options like I did. Luckily; they are interchangable on proxmox vms and do not require any sort of reinstalation like you would on a normal OS. 
 
-### Gemini Code Assist on a VM
+### Code Assist on a VM
 
 The "The Gemini Code Assist server crashed 5 times" error can occur when using code-server or VS Code. This crash, identified by the SIGILL (Illegal Instruction) signal, is usually due to a hardware mismatch.
 
@@ -50,7 +36,7 @@ The "The Gemini Code Assist server crashed 5 times" error can occur when using c
 
 #### The Solution
 
-- [ ] Step 1: Diagnosing the CPU: 
+  - Step 1: Diagnosing the CPU: 
   
     A command can check for the required instruction flags. In the Ubuntu terminal, run:
 
@@ -60,7 +46,7 @@ The "The Gemini Code Assist server crashed 5 times" error can occur when using c
 
     The Result: If the output shows aes, but avx and pclmul are missing, the virtual processor is too "basic".
 
-- [ ] Step 2: The Immediate Fix (Downgrade)
+  - Step 2: The Immediate Fix (Downgrade)
 
     To fix this, roll back to a version before these requirements were enforced:
 
@@ -69,7 +55,7 @@ The "The Gemini Code Assist server crashed 5 times" error can occur when using c
     3. Choose v2.55.x or earlier.
     4. Important: Uncheck "Auto Update" to prevent it from breaking again.
 
-- [ ] Step 3: The Long-Term Fix (Proxmox CPU Passthrough)
+  - Step 3: The Long-Term Fix (Proxmox CPU Passthrough)
 
     The best fix is to expose the physical CPU's features to the VM. No reinstallation is required.
     How to change to "Host" Processor in Proxmox: