@@ -209,9 +209,7 @@ Migration guides which help you to migrate to supported major SDK versions can b
 
 We use a modified version of [Semantic Versioning](https://semver.org/) for all changes. See [version strategy](VERSIONS.md) for details which is effective from 30 July 2022.
 
-A current release is on the leading edge of our SDK development, and is intended for customers who are in active development and want the latest and greatest features.  
-Instead of stating a release date for a new feature, we set a fixed minor or patch release cadence of maximum 2-3 months (while we may release more often).
-At the same time, there is no schedule for major or breaking release. Instead, we will communicate one quarter in advance the upcoming breaking change to allow customers to plan for the upgrade.
+A current release is on the leading edge of our SDK development, and is intended for customers who are in active development and want the latest and greatest features.
 
 We always recommend that all users run the latest available minor release for whatever major version is in use.
 We highly recommend upgrading to the latest SDK major release at the earliest convenient time and before the EOL date.
 
@@ -11,7 +11,6 @@ The MAJOR version is used to indicate the family of technology represented by th
 
 New MAJOR versions will be communicated in advance via:
 
-* An email announcement is sent to affected accounts, announcing our plans to end support for the specific SDK version. The email will outline the path to end-of-support, specify the campaign timelines, and provide upgrade guidance.
 * Box SDK documentation, such as API reference documentation, user guides, SDK product marketing pages, and GitHub readme(s) are updated to indicate the campaign timeline and provide guidance on upgrading affected applications.
 * Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation.