diff --git a/Configs & Servers/Windows Server/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md b/Configs & Servers/Windows Server/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md
index 2cb753b..e9238e3 100644
--- a/Configs & Servers/Windows Server/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md	
+++ b/Configs & Servers/Windows Server/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md	
@@ -1,5 +1,4 @@
-# Deploy Additional Failover Cluster Node
-Deploying a Windows Server Node into the Hyper-V Failover Cluster is an essential part of rebuilding and expanding the backbone of my homelab.  The documentation below goes over the process of setting up a bare-metal host from scratch and integrating it into the Hyper-V Failover Cluster.
+**Purpose**: Deploying a Windows Server Node into the Hyper-V Failover Cluster is an essential part of rebuilding and expanding the backbone of my homelab.  The documentation below goes over the process of setting up a bare-metal host from scratch and integrating it into the Hyper-V Failover Cluster.
 
 !!! note "Prerequisites"
     This document assumes you are have installed and are running a bare-metal Hewlett-Packard Enterprise server running iLO (Integrated Lights Out) with the latest build of **Windows Server 2022 Datacenter (Desktop Experience)**.  Windows will prompt you that your build is expired if it is too old.