Fixing the markdown fixes because the markdown linter contradicts our…

.markdownlint.json

@@ -1,5 +1,6 @@
 {
     "MD013": false,
+    "MD041": false,
     "emphasis": { "style": "asterisk" },
     "no-inline-html": false,
     "ul-style": { "style": "dash" }

src/pages/docs/administration/upgrading/index.mdx

@@ -63,8 +63,6 @@ The Windows Service is split across multiple folders to make upgrading easy and
 - **Tentacles**: Octopus Deploy connects to deployment targets via the Tentacle service.  Each version of Octopus Deploy includes a specific Tentacle version.  Tentacle upgrades do not occur until *after* the Octopus Deploy server is upgraded.  Tentacle upgrades are optional; any Tentacle greater than 4.x will work [with any modern version of Octopus Deploy](/docs/support/compatibility).  We recommend you upgrade them to get the latest bug fixes and security patches when convenient.  
 - **Calamari**: The Tentacles facilitate communication between Octopus Deploy and the deployment targets.  Calamari is the software that does the actual deployments.  Calamari and Octopus Deploy are coupled together.  Calamari is upgraded automatically during the first deployment to a target.
 
-## Supported Octopus Deploy Server Versions
-
 <OctopusReleases />
 
 ## How we version Octopus Deploy

src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx

@@ -23,8 +23,6 @@ There are three components to an Octopus Deploy instance:
 
 This document will provide you with guidelines and recommendations for self-hosting Octopus Deploy.
 
-## Supported Octopus Deploy Server Versions
-
 <OctopusReleases />
 
 ## Host Octopus on Windows Server or as a Linux Container

src/pages/docs/installation/index.mdx

@@ -45,8 +45,6 @@ When installed, the self-hosted Octopus Server:
 
 Before you install Octopus Deploy, review the software and hardware [requirements](/docs/installation/requirements/), and make sure you have access to an instance of [SQL Server Database](/docs/installation/sql-server-database) that you can use with Octopus Deploy.
 
-## Supported Octopus Deploy Server Versions
-
 <OctopusReleases />
 
 ## Install Octopus as a Windows Service \{#install-octopus}

src/pages/docs/installation/requirements.mdx

@@ -21,8 +21,6 @@ Octopus Server can be hosted on either:
 
 However, once your Octopus Server is up and running, you can deploy to Windows servers, Linux servers, Microsoft Azure, AWS, GCP, Cloud Regions, or even an offline package drop.
 
-## Supported Octopus Deploy Server Versions
-
 <OctopusReleases />
 
 ### Windows Server

src/shared-content/installation/octopus-releases.include.md

@@ -1,13 +1,6 @@
----
-layout: src/layouts/Default.astro
-pubDate: 2023-01-01
-modDate: 2023-01-01
-title: octopus release and supported versions include
-description: Include the octopus deploy release and supported versions
-navOrder: 666
----
+## Supported Octopus Deploy Server Versions
 
-Each self-hosted major.minor release of Octopus Deploy will receive critical patches and support for a period of six months.  For example, 2025.4 was released in December 2025 and will be supported for six months.
+Each self-hosted major.minor release of Octopus Deploy will receive *critical patches and support* for a period of **six months.**  For example, 2025.4 was released in December 2025 and will be supported through May 2026.
 
 All new releases of Octopus Deploy will run in Octopus Cloud first for at least one quarter.  As a result, Octopus Cloud is always at least one version ahead of the self-hosted version.