diff --git a/src/CopyOnWrite/README.md b/src/CopyOnWrite/README.md
index 969ceb3c..6b0c165d 100644
--- a/src/CopyOnWrite/README.md
+++ b/src/CopyOnWrite/README.md
@@ -37,6 +37,6 @@ This SDK aims to improve the performance of large repositories by minimizing fil
 Perf test results on large-sized repos can be found in this [blog post](https://devblogs.microsoft.com/engineering-at-microsoft/copy-on-write-performance-and-debugging/). That post also includes debugging information such as how to determine if a filesystem entry is a CoW link (block clone).
 
 ## Using on Windows
-To use this feature on Windows, you need run your build on a drive formatted with [Dev Drive](https://aka.ms/devdrive) or [ReFS](https://learn.microsoft.com/en-us/windows-server/storage/refs/refs-overview) on Windows. You should also move your package cahce to the same volume. ReFS is available on Windows Server, or on Windows 11 22H2 Enterprise and Pro SKUs. Dev Drive is available on all Windows 11 SKUs starting in 22H2 and in [Windows Server 2025](https://learn.microsoft.com/en-us/windows-server/get-started/whats-new-windows-server-2025#block-cloning-support).
+To use this feature on Windows, you need run your build on a drive formatted with [Dev Drive](https://aka.ms/devdrive) or [ReFS](https://learn.microsoft.com/en-us/windows-server/storage/refs/refs-overview) on Windows. You should also move your package cache to the same volume. ReFS is available on Windows Server, or on Windows 11 22H2 Enterprise and Pro SKUs. Dev Drive is available on all Windows 11 SKUs starting in 22H2 and in [Windows Server 2025](https://learn.microsoft.com/en-us/windows-server/get-started/whats-new-windows-server-2025#block-cloning-support).
 
 See [blog post 1](https://aka.ms/EngMSDevDrive) and [blog post 2](https://aka.ms/VSDevDrive) for more information on Dev Drive, copy-on-write, and moving your package caches.