diff --git a/content/posts/psa-microsoft-kb5022842-breaks-ws2022-secure-boot/index.md b/content/posts/psa-microsoft-kb5022842-breaks-ws2022-secure-boot/index.md
index 17654bd..c348ebc 100644
--- a/content/posts/psa-microsoft-kb5022842-breaks-ws2022-secure-boot/index.md
+++ b/content/posts/psa-microsoft-kb5022842-breaks-ws2022-secure-boot/index.md
@@ -30,7 +30,7 @@ Microsoft released [a patch](https://msrc.microsoft.com/update-guide/releaseNote
 
 So yeah. That's, uh, *not great.*
 
-If you've got any **Windows Server 2022** VMs with **Secure Boot** enabled on **ESXi 6.7/7.x**, you'll want to make sure they *do not* get **KB5022842** until this problem is resolved.
+If you've got any **Windows Server 2022** VMs with **[Secure Boot](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-898217D4-689D-4EB5-866C-888353FE241C.html)** enabled on **ESXi 6.7/7.x**, you'll want to make sure they *do not* get **KB5022842** until this problem is resolved.
 
 I put together a quick PowerCLI query to help identify impacted VMs in my environment:
 ```powershell