diff --git a/blog/posts/01-22-2025 - Windows Power Profiles Causing CPU Performance Loss.md b/blog/posts/01-22-2025 - Windows Power Profiles Causing Notable CPU Performance Loss.md
similarity index 96%
rename from blog/posts/01-22-2025 - Windows Power Profiles Causing CPU Performance Loss.md
rename to blog/posts/01-22-2025 - Windows Power Profiles Causing Notable CPU Performance Loss.md
index e6649f8..87c334d 100644
--- a/blog/posts/01-22-2025 - Windows Power Profiles Causing CPU Performance Loss.md	
+++ b/blog/posts/01-22-2025 - Windows Power Profiles Causing Notable CPU Performance Loss.md	
@@ -10,9 +10,10 @@ tags:
   - Windows Server
   - Power Profiles
   - Virtualization
+  - Veeam
 ---
 
-# Windows Power Profiles Causing CPU Performance Loss
+# Windows Power Profiles Causing Notable CPU Performance Loss
 So I've been noticing a trend recently regarding something I never really took much time to consider, but later realized had huge potential to impact performance of potentially both physical and virtual servers.  (I have not personally seen it affect virtual machines, but it's plausible it could happen).
 
 ## Overview of the Problem