initial draft of changes

Author: johnmarco

articles/openshift/support-lifecycle.md

@@ -5,7 +5,7 @@ author: joharder
 ms.author: joharder
 ms.service: azure-redhat-openshift
 ms.topic: conceptual
-ms.date: 06/01/2023
+ms.date: 08/10/2023
 ---
 
 # Support lifecycle for Azure Red Hat OpenShift 4
@@ -68,7 +68,7 @@ When a new minor version is introduced, the oldest minor version is deprecated a
 
 ## Release and deprecation process
 
-You can reference upcoming version releases and deprecations on the Azure Red Hat OpenShift Release Calendar.
+You can reference upcoming version releases and deprecations on the [Azure Red Hat OpenShift release calendar](#azure-red-hat-openshift-release-calendar).
 
 For new minor versions of Red Hat OpenShift Container Platform:
 * The Azure Red Hat OpenShift SRE team publishes a pre-announcement with the planned date of a new version release, and respective old version deprecation, in the [Azure Red Hat OpenShift Release notes](https://github.com/Azure/OpenShift/releases) at least 30 days prior to removal.
@@ -103,7 +103,11 @@ See the following guide for the [past Red Hat OpenShift Container Platform (upst
 |4.9|November 2021| February 1 2022|4.11 GA|
 |4.10|March 2022| June 21 2022|4.12 GA|
 |4.11|August 2022| March 2 2023|4.13 GA|
+|4.12|August 2023| August 19 2023|October 19 2024|
 
+> [!IMPORTANT]
+> Starting with ARO version 4.12, the support lifecycle for new versions will be set to 14 months from the day of general availability. That means that the end date for support of each version will no longer be dependent on the previous version (as shown in the table above for version 4.12.) This does not effect support for the previous version; two generally available (GA) minor versions of Red Hat OpenShift Container Platform will continue to be supported, as [explained previously](#red-hat-openshift-container-platform-version-support-policy).
+> 
 ## FAQ
 
 **What happens when a user upgrades an OpenShift cluster with a minor version that is not supported?**