diff --git a/reference/emerging-technology-and-inactive-projects.rst b/reference/emerging-technology-and-inactive-projects.rst
index 75dba37ce..966890113 100644
--- a/reference/emerging-technology-and-inactive-projects.rst
+++ b/reference/emerging-technology-and-inactive-projects.rst
@@ -75,18 +75,18 @@ timeframe, TC will discuss with the team if more time is required for the
 project to meet the :doc:`new-projects-requirements` or will retire the project.
 
 An existing project should be reinstated as an active OpenStack project before
-the final release of the cycle they entered the ``inactive`` state to be become
-``active`` again and to be released in that cycle.  In the case where an
-``inactive`` project does not become ``active`` before the end of the cycle,
-there will be no release of it proposed by the release team in that cycle. In
-such a case it is up to the project itself to get CI working and propose a
-release if that is needed. It may be required like that for example when there
-will be some security fixes or compatibility fixes merged in the project.
-In the case where an ``inactive`` project still does not become ``active``
-during the next cycle after the cycle they entered the ``inactive`` state, TC
-will discuss with the team if project will be retired before final release
-in the release cycle. In such a case there will be no new releases of that
-project.
+the release milestone-2 of the cycle they entered the ``inactive`` state to
+become ``active`` again and to be released in that cycle.  In the case where an
+``inactive`` project does not become ``active`` before the release milestone-2,
+there will be no release of it proposed by the release team in that cycle.
+In such a case it is up to the project itself to get CI working and propose
+a release if that is needed. It may be required like that for example
+when there will be some security fixes or compatibility fixes merged in the
+project. In the case where an ``inactive`` project still does not become
+``active`` during the next cycle after the cycle they entered the ``inactive``
+state, TC will discuss with the team if project will be retired before the
+release milestone-2 of the cycle. In such a case there will be no new releases
+of that project.
 
 Tracking
 ========