diff --git a/charles-patching-guide.md b/charles-patching-guide.md
index c8e6e5f..306bb12 100644
--- a/charles-patching-guide.md
+++ b/charles-patching-guide.md
@@ -1,20 +1,35 @@
 # TopNotch Gaming — Patching Guide for Charles Tepper
 
-**Version Number** 1.0.1 Release
+**Version Number** 1.0.2 Release
+
 **Last updated:** 2026-05-23
-**Applies to:** All Salt-managed Linux hosts (15 minions)  
+
+**Applies to:** All Salt-managed Linux hosts (15 minions)
+
 **Run from:** undyne (192.168.16.9) — Salt Master
 
 ---
 
 ## Overview
 
-Patching is handled by Salt and runs in three tiers: **dev → staging → prod**. The orchestrator waits for each tier to succeed before moving to the next, so a bad update won't automatically roll forward to production.
+Patching is handled by Salt and runs in four groups: **dev → staging → prod/Infra**. The orchestrator waits for each tier to succeed before moving to the next, so a bad update won't automatically roll forward to production.
 
 Reboots are **disabled by default** (controlled via pillar). The patch run upgrades packages only; reboots are a separate decision made after reviewing what changed.
 
 ---
+## Overview of Machines we manage using Salt
 
+INFRA: Granberia, Undyne, Midgar, Junon, gw5, Kalm, almaelma, pve, proxvm1, proxweb0, proxVM2
+
+PROD: Leviathan, Gnome, Salamander, vaultwarden
+
+*DO NOTE: PVE, ProxVM1, ProxWeb0, and ProxVM2 are all the Proxmox Hypervisors. Under NO circumstance should these ever have any updates that are pertainent or require a reboot, unless strictly specified under the header "What's Held (Won't be Patched)"*
+
+INFRA should be rebooted every Sunday if a reboot is required. Patches should be applied every Sunday.
+
+PROD should be rebooted every FIRST sunday regardless of if a reboot is required or not. Patches should be applied every Sunday.
+
+---
 ## Before You Start
 
 SSH into undyne using your AD credentials: