changes updated

Signed-off-by: Dishank Tiwari <[email protected]>

content/supported_versions.md

@@ -22,11 +22,11 @@
 ### Innovation (I) Release
 
 - Innovation releases are designed for customers seeking faster modernization and innovation. Progress recommends using continuous integration and continuous delivery to help benefit from the more rapid release cadence. Innovation releases also allow all customers to explore features appearing in future LTS releases.
-- With the introduction of LTS in Chef, any other major release will be termed an Innovation Release. This release will not be time-bound and will allow Progress Chef to release significant versions and new features without LTS.
+- With the introduction of LTS in Chef, any other major release will be termed an Innovation Release. This release will be flexible and allow Progress Chef to release significant versions and new features without LTS.
 
 ### Long-Term Supported (LTS) Release
 
-- From time to time, Progress may elect to designate a new release as Long Term Supported (LTS). Customers who primarily look for stability and minimal change for their implementation over many years can adapt to the LTS release.
+- From time to time, Progress may elect to designate a new release as Long-Term Supported (LTS). Customers who primarily look for stability and minimal change for their implementation over many years can adapt to the LTS release.
 - The software will get support depending on the timeline decided with LTS.
 - Upgrade planning is more manageable for customers since they know when the next LTS version will be out.
 
@@ -35,11 +35,11 @@
 - Progress may offer Technical/Private Previews containing Technical Preview Features on a Progress-hosted environment under the terms in the applicable End User License Agreement.
 - Progress may preview Features/Products planned to be released as future LTS features/products so that customers can validate if new features/products meet their use case and provide early feedback to Progress ahead of a general release.
 - This release does not include CVE fixes, which Progress may choose to do.
-- For Chef products, customers must move to GA release once GA is available. We do not provide any support for any release candidates such as Alpha Beta or Private Preview post the GA launch
+- Customers must move to GA release once GA is available for Chef products. We do not provide any support for any release candidates such as Alpha Beta or Private Preview post the GA launch.
 
 ### Lifecycle Definitions
 
-- Each Innovation and LTS release has its own lifecycle starting at GA, migrates, and ends as described below:
+- Each Innovation and LTS release has its lifecycle starting at GA, migrates, and ends as described below:
 
 ### Generally Available (GA)
 
@@ -48,32 +48,32 @@
 - GA releases are fully supported (LTS or Innovation). If you face any problems, Progress will work with you to find an appropriate resolution if active maintenance and support services cover them.
 - Chef continues to provide releases to the application or version in response to customer needs and security vulnerabilities.
 - Chef welcomes customer feature requests for the product roadmap for the application.
-- Progress will evaluate GA releases for certifications of new third-party products, including new operating system versions. When porting to new operating systems that were not previously supported, only LTS versions will be considered.
+- Progress will evaluate GA releases for certifications of new third-party products, including new operating system versions. If you are porting to a new operating system that has not previously been supported, the LTS versions will be considered.
 
 ### Migration Phase (MP)
 
 - An LTS/I release enters the Migration Phase with the launch of the LTS+/I+ release. When the Sunset Phase starts, in parallel, the Migration Phase starts, which is the transition period provided to customers to move to LTS+/I+.
 - LTS and Innovation releases in the Migration Phase are fully supported. Progress will evaluate them for certifications on new operating environments but not for ports to new hardware systems.
-- If you face any problem using product releases in the Migration Phase, Progress will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses.
+- If you encounter any problems using product releases in the Migration Phase, Progress will work with customers toward an appropriate resolution where possible if active maintenance and support services cover their licenses.
 
 ### Sunset Phase (Only for LTS releases)
 
 - After fulfilling the following conditions, an LTS release enters the Sunset Phase.
 - When the launch of the release is for two or more years, and
 - A new LTS version has been released.
 - The Sunset phase does not apply to Innovation releases. Once a subsequent Innovation release becomes available, the prior Innovation release immediately moves to the EOL life cycle phase with a given period of migration phase.
-- If you face any problem using product releases in the Sunset Phase, Progress will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an Update provided by Progress. We are committed to providing continuous support even during the Sunset Phase, ensuring your confidence in our products.
-- Progress does not provide standard support for the LTS release in the Sunset Phase unless the customer has opted for Extended Paid Support. Progress recommends that customers plan to upgrade from Sunset Phase product releases using this document as a guideline.
+- If you face any problem using product releases in the Sunset Phase, Progress will work with customers towards an appropriate resolution where possible if active maintenance and support services cover their licenses. The resolution includes the possibility of an Update provided by Progress. We are committed to continuous support even during the Sunset Phase, ensuring your confidence in our products.
+- Progress only provides standard support for the LTS release in the Sunset Phase if the customer has opted for Extended Paid Support. Progress recommends that customers plan to upgrade from Sunset Phase product releases using this document as a guideline.
 
 ### End Of Life (EOL) Phase
 
-The following describes the general impact of a product reaching EOL. For more details, refer to the official EOL communication, usually delivered via email. You can also find this information [here].
+The following describes the general impact of a product reaching EOL. For more details, refer to the official EOL communication, usually emailing. You can also find this information [here].
 
 - This stage indicates that Progress has set a date after which the application or version will no longer be supported or recommended for customers' use.
 - Products covered by active maintenance and support services at the time of an announced EOL will continue receiving Technical Support on the same terms as Sunset product releases for the duration of the purchased maintenance and support services.
 - Progress does not allow renewal of maintenance and support services for EOL products.
 - Once the existing maintenance and support services expire, Progress will not provide any further enhancements or fixes or entertain any new support cases. The existing product documentation, knowledgebase articles, and online user community discussions will remain the only support.
 For more details on the Chef on Prem Life Cycle Policy, click here <policy link>
 
 ### Versions and Status
 
@@ -81,11 +81,11 @@
 
 - LTS for Progress Chef will be for three years.
 - LTS will follow the released version.
     - For Example, Chef Infra 19 LTS is a significant version. All minor releases are like 19. X and patches are like 19.2.x and will fall under LTS support.
 - As the Product EOL date is predetermined, a new release is not required to publish this message.
 - There can be more than one Innovation release between the next LTS release. For example, Chef Infra 20 and 22 will be an Innovation Release, and the next LTS release can be Chef 23 LTS.
-- When LTS is released, it will have a declared sunset date that is not to be shorter than two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed and a new LTS version is released. 'Sunset' in this context means the end of active support and the start of the EOL phase.
-- Customers will then have a specified migration time (no less than 6 months) declared as part of the LTS+ release. At the end of the “migration window,” LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress).
+- When LTS is released, it will have a declared sunset date of at most two years. The LTS will only be marked ‘Sunset’ when the date (>=2 yr) has elapsed, and a new LTS version is released. 'Sunset' in this context means the end of active support and the start of the EOL phase.
+- Customers will then have a specified migration time (no less than six months) declared as part of the LTS+ release. At the end of the “migration window,” LTS will be declared end of life. Customers may purchase extended migration support that will extend the time required to migrate to the new LTS version (up to a reasonable limit set by Progress).
 - Upon releasing I+, the current Innovation release is EOL and subject to the migration window.
 
 ## Supported Commercial Distributions
@@ -96,8 +96,8 @@
 |-------------------|---------|---------|------------------|--------------|---------------------------------------|
 | Chef Courier      | 1.0     | I       | GA               |              | 6 months after the release of I+      |
 | Chef 360 Platform | 1.0     | I       | GA               |              | 6 months after the release of I+      |
 | Chef Infra Client | 19      | LTS     | GA               | <TBD>        | 3 years or more from the release date |
 | Chef InSpec       | 7       | LTS     | GA               | <TBD>        | 3 years or more from the release date |
 
 {{< note >}} Chef Backend does not directly require acceptance of the Chef EULA, but it does have functionality that requires its acceptance in other products. {{< /note >}}
 
@@ -135,7 +135,7 @@
 | Chef Push Jobs           | All                 | EOL              | December 31, 2020 |
 | Chef Replication/Sync    | All                 | EOL              | August 31, 2019   |
 | Chef Server DRBD HA      | All                 | EOL              | March 31, 2019    |
 | Chef Workflow (Delivery) | All                 | EOL              | December 31, 2020 | 
 | Chef Workstation         | 20.12.205 and under | EOL              | December 31, 2021 |
 | Enterprise Chef          | All                 | EOL              | December 31, 2018 |
 | Reporting                | All                 | EOL              | December 31, 2018 |

content/versions.md

@@ -13,7 +13,7 @@
     weight = 30
 +++
 
-This section lists the free and commercial Chef products and versions we currently support and will continue to support until the end of year 2024 or till Infra Client 18 is End of Life (which ever happens first). The lifecycle stage defines the involvement by Chef Software in updating and maintaining each product.
+This section lists the free and commercial Chef products and versions we currently support and will continue to support until the end of 2024 or until Infra Client 18 is End of Life (whichever happens first). The lifecycle stage defines Chef Software's involvement in updating and maintaining each product.
 
 ## Lifecycle Definitions
 
@@ -44,7 +44,7 @@
 
 Unless otherwise stated, versions older than those listed below are EOL.
 
 Chef Infra Client 19 and other chef products that will launch after Infra client 19 will follow new long term support policy. Please refer our new page for <supported version> for more details.
 
 {{< /important >}}