DOCSP-50306-directions-mck-release-notes (#30)

* (DOCSP-50306) add details and fix release notes

* link fix

Author: shuangela

source/index.txt

@@ -54,6 +54,10 @@ You can then deploy MongoDB databases as you deploy them now after the
 cluster is created. You can use the |com| console to run MongoDB at
 optimal performance.
 
+The |k8s-op-full| is an operator that replaces the previous MongoDB
+Enterprise Kubernetes Operator and MongoDB Community Operator. For more information
+about the first version of |k8s-op-short|, see the :ref:`release notes <mck-1.1.0-rn>`.
+
 .. seealso::
 
    - :ref:`faq-k8s-advanced`

source/release-notes.txt

@@ -85,13 +85,12 @@ Migration from the Community Kubernetes Operator and the Enterprise Kubernetes O
 |k8s-op-short| is seamless: your MongoDB deployments are not impacted by the upgrade and 
 require no changes. Simply follow the instructions in the :ref:`migration guide <migrate-to-mck>`.
 
-
 Legacy Operator Deprecation and EOL
 -----------------------------------
 
-We will continue best-effort support of the Community Kubernetes Operator for 6 month,
-until November, 2025). Each Enterprise Kubernetes Operator release will remain supported 
-according to the current `guidance <https://www.mongodb.com/docs/kubernetes-operator/current/reference/support-lifecycle/>`__
+We will continue best-effort support of the Community Kubernetes Operator for 6 months,
+until November, 2025. Each Enterprise Kubernetes Operator release will remain supported 
+according to the current `guidance <https://www.mongodb.com/docs/kubernetes-operator/v1.33/reference/support-lifecycle/>`__.
 
 All future bug fixes and improvements will be released in new versions of |k8s-op-short|. 
 We encourage all users to plan their migration to |k8s-op-short| within these timelines.