diff --git a/README.md b/README.md
index 3d6caeee6..af71cd48a 100644
--- a/README.md
+++ b/README.md
@@ -69,7 +69,7 @@ The example above also has an [annotated and production ready version here](docs
 
 ## Installation
 
-Pester runs on Windows, Linux, MacOS and anywhere else thanks to PowerShell. It is compatible with Windows PowerShell 5.1 and PowerShell 7.2 and newer.
+Pester runs on Windows, Linux, MacOS and anywhere else thanks to PowerShell. It is compatible with Windows PowerShell 5.1 and PowerShell 7.4 and newer.
 
 Pester 3 comes pre-installed with Windows 10, but we recommend updating, by running this PowerShell command _as administrator_:
 
diff --git a/docs/6.0.0.md b/docs/6.0.0.md
index 5ea221074..65b204b76 100644
--- a/docs/6.0.0.md
+++ b/docs/6.0.0.md
@@ -8,7 +8,7 @@ real-world testing before the final release. Pester 6 builds on the v5 runtime (
 configuration object, the rich result object) and focuses on a brand new assertion syntax, faster
 code coverage, and an experimental parallel runner.
 
-Pester 6 runs on **Windows PowerShell 5.1** and **PowerShell 7.2+**.
+Pester 6 runs on **Windows PowerShell 5.1** and **PowerShell 7.4+**.
 
 - [What's new?](#whats-new)
   - [New `Should-*` assertions](#new-should--assertions)
@@ -369,7 +369,7 @@ still change before it is declared stable.
 Support for **PowerShell 3, 4, 6, and early/unsupported 7** has been removed — all of these are out
 of support from Microsoft. Dropping them let us delete a large amount of compatibility code, move the
 C# to **.NET 8** (with net462 for Windows PowerShell 5.1), and modernize the runtime. Pester 6
-targets **Windows PowerShell 5.1** and **PowerShell 7.2+**.
+targets **Windows PowerShell 5.1** and **PowerShell 7.4+**.
 
 ### Richer failure messages and output
 
@@ -414,7 +414,7 @@ targets **Windows PowerShell 5.1** and **PowerShell 7.2+**.
 ## Breaking changes
 
 - **PowerShell 3, 4, 6, and unsupported 7 are no longer supported.** Minimum is Windows PowerShell
-  5.1 / PowerShell 7.2+.
+  5.1 / PowerShell 7.4+.
 - **Discovery and run now happen per file** instead of discovering every file up front and then
   running everything. It is invisible for self-contained files, but discovery-time side effects (for
   example a module imported at the top of one file) no longer carry into another file's discovery.