diff --git a/en/00_Getting_Started/00_Server_Requirements.md b/en/00_Getting_Started/00_Server_Requirements.md
index f10ab9519..5412a539a 100644
--- a/en/00_Getting_Started/00_Server_Requirements.md
+++ b/en/00_Getting_Started/00_Server_Requirements.md
@@ -12,7 +12,7 @@ the server to update templates, website logic, and perform upgrades or maintenan
 
 ## PHP
 
-- PHP >=8.1, <=8.3
+- PHP 8.3
 - PHP extensions: `ctype`, `dom`, `fileinfo`, `hash`, `intl`, `mbstring`, `session`, `simplexml`, `tokenizer`, `xml`
 - PHP configuration: `memory_limit` with at least `48M`
 - PHP extension for image manipulation: Either `gd` or `imagick`
@@ -295,12 +295,9 @@ table may be of use:
 
 | Silverstripe CMS Version | PHP Version |
 | ------------------------ | ----------- |
+| 6.0 +                    | 8.3         |
 | 5.2 +                    | 8.1 - 8.3   |
 | 5.0 - 5.1                | 8.1 - 8.2   |
-| 4.11 +                   | 7.4 - 8.1   |
-| 4.10                     | 7.3 - 8.0   |
-| 4.5 - 4.9                | 7.1 - 7.4   |
-| 4.0 - 4.4                | 5.6 - 7.4   |
 
 From Silverstripe CMS 5 onwards, the [Silverstripe CMS major release policy](/project_governance/major_release_policy#php-support-commitments) guides which PHP versions are supported by which Silverstripe CMS release.
 
diff --git a/en/00_Getting_Started/02_Composer.md b/en/00_Getting_Started/02_Composer.md
index a7d1c2aa7..ea8b0da37 100644
--- a/en/00_Getting_Started/02_Composer.md
+++ b/en/00_Getting_Started/02_Composer.md
@@ -183,7 +183,7 @@ file. It will appear in your project root, and by default, it will look somethin
     "type": "silverstripe-recipe",
     "description": "The SilverStripe Framework Installer",
     "require": {
-        "php": "^8.1",
+        "php": "^8.3",
         "silverstripe/recipe-plugin": "^2",
         "silverstripe/vendor-plugin": "^2",
         "silverstripe/recipe-cms": "~5.0.0@stable",
@@ -340,7 +340,7 @@ Open `composer.json`, and find the module's `require`. Then put `as (core versio
 ```json
 {
     "require": {
-        "php": "^8.1",
+        "php": "^8.3",
         "silverstripe/recipe-cms": "~5.0.0@stable",
         "silverstripe/framework": "dev-myproj as 5.0.0",
         "silverstripe-themes/simple": "~3.2.0"
diff --git a/en/00_Getting_Started/index.md b/en/00_Getting_Started/index.md
index 073ab82f0..a778a19ba 100644
--- a/en/00_Getting_Started/index.md
+++ b/en/00_Getting_Started/index.md
@@ -8,7 +8,7 @@ icon: rocket
 
 ## Server requirements
 
-Silverstripe requires PHP 8.1 or newer. It runs on many webservers and databases, but is most commonly served using
+Silverstripe requires PHP 8.3 or newer. It runs on many webservers and databases, but is most commonly served using
 Apache and MySQL/MariaDB.
 
 If you are setting up your own environment, you'll need to consider a few configuration settings such as URL rewriting
diff --git a/en/12_Project_Governance/05_Major_release_policy.md b/en/12_Project_Governance/05_Major_release_policy.md
index a2fbf6cd1..ea37038cb 100644
--- a/en/12_Project_Governance/05_Major_release_policy.md
+++ b/en/12_Project_Governance/05_Major_release_policy.md
@@ -116,7 +116,7 @@ The Silverstripe CMS release cycle is built around these assumptions:
 
 At launch, a Silverstripe CMS major release supports all PHP versions in full support. PHP versions in limited support are not supported at launch by new Silverstripe CMS major releases.
 
-Following the initial launch of a Silverstripe CMS major release, the development team aims to add forward compatibility for the next PHP release. e.g: Silverstripe CMS 5 at launch will support PHP 8.1 and PHP 8.2. CMS 5 should receive official support for an eventual PHP 8.3 in early 2024.
+Following the initial launch of a Silverstripe CMS major release, the development team aims to add forward compatibility for the next PHP release. e.g: Silverstripe CMS 6 at launch will support PHP 8.3 and PHP 8.4. CMS 5 should receive official support for an eventual PHP 8.5 in early 2026.
 
 Support for end-of-life PHP releases is not dropped within a Silverstripe CMS major release line, unless it's necessary to address vulnerabilities or high impact bugs.