diff --git a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md
index 5e778f8..545f8bf 100644
--- a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md	
+++ b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md	
@@ -3,15 +3,22 @@
 !!! note "Assumptions"
     This guide assumes you have two Hyper-V Failover Clusters, for the sake of the guide, we will refer to the Production cluster as `CLUSTER-01` and the Replication cluster as `CLUSTER-02`.  This guide also assumes that Replication was set up beforehand, and does not include instructions on how to deploy a Replica Broker (at this time).
 
-## Locate the GuestVM (CLUSTER-01)
+## Production Cluster - CLUSTER-01
+### Locate the GuestVM
 You need to start by locating the GuestVM in the Production cluster, CLUSTER-01.  You will know you found the VM if the "Replication Health" is either `Unhealthy`, `Warning`, or `Critical`.
 
-### Remove Replication from GuestVM (CLUSTER-01)
+### Remove Replication from GuestVM
 - Within Hyper-V: Failover Cluster Manager
     - Right-Click the GuestVM
     - Navigate to "**Replication > Remove Replication**"
+    - Confirm the removal by clicking the "**Yes**" button `You will know if it worked when the "Replication State" is `Not enabled`
+
+## Replication Cluster - CLUSTER-02
+### Delete the GuestVM from Replication Cluster
+- Within Hyper-V: Failover Cluster Manager
+    - Right-Click the GuestVM
+    - 
 
-Delete the GuestVM Entirely from Hyper-V: Failover Cluster in Cluster-02 (Replication Cluster)
 Delete the GuestVM manually from Hyper-V Manager on Host-05, Host-06, Host-07, Host-08)
 Delete the GuestVM's replicated VHDX storage from replication storage on C:\ClusterStorage\Volume02
 Enable Replication on GuestVM in Cluster-01 (Production Cluster)
\ No newline at end of file