diff --git a/astro/src/content/docs/operate/roadmap/deprecation-policy.mdx b/astro/src/content/docs/operate/roadmap/deprecation-policy.mdx
index 0a77c778f9..00ee06e183 100644
--- a/astro/src/content/docs/operate/roadmap/deprecation-policy.mdx
+++ b/astro/src/content/docs/operate/roadmap/deprecation-policy.mdx
@@ -3,7 +3,7 @@ title: Deprecation Policy
 description: Learn more about the FusionAuth deprecation policy.
 ---
 
-FusionAuth is an architectural component integrated into your applications or systems. Such integration means that when changes to FusionAuth occur, it can negatively affect your application. As developers ourselves, we strive to maintain backwards compatibility. 
+FusionAuth is an architectural component integrated into your applications or systems. Such integration means that when changes to FusionAuth occur, it can negatively affect your application. As developers ourselves, we strive to maintain backwards compatibility. We will not remove API support in minor or patch versions (only in major versions), except for security/performance reasons noted below.
 
 However, there are times when features or functionality must be removed. FusionAuth has [extensive release notes](/docs/release-notes/), which are the source of truth for changes to the FusionAuth system, and any deprecated features will be listed there. Changes to existing features or behavior will also be documented in the release notes.
 
@@ -34,24 +34,7 @@ The releases mentioned in this document are either major or point version releas
 Before removing a feature, the FusionAuth team takes the following steps:
 
 * In the first major or point release where the behavior is deprecated, the deprecation is noted in the release notes. The feature is also marked as deprecated in the documentation.
-* The feature deprecation is noted in the documentation for three months.
-* In a major or point release after the three month deprecation period, the feature and corresponding documentation are removed. When the feature is removed, it is noted in the release notes. The documentation for the feature is also removed.
-
-While the team commits to maintaining features for at least three months after they are deprecated, that timeframe is a minimum.
-
-## Example Removal Timeline
-
-Suppose the current release is 1.52.0 and FusionAuth planned to remove feature ABC in the next release. Here is what the timeline would look like.
-
-| FusionAuth Version    | Date Released | Feature ABC Changes | Release Notes Updates |
-| -------- | ------- | ------- | ------- |
-| 1.52.0  | March 1, 2024 | None | None |
-| 1.52.1  | March 8, 2024 | None | None |
-| 1.53.0  | April 1, 2024 | Feature documentation marked as deprecated. | Deprecation announced in release notes. |
-| 1.53.1  | April 5, 2024 | Feature documentation remains marked as deprecated. | None |
-| 1.53.2  | April 15, 2024 | Feature documentation remains marked as deprecated. | None |
-| 1.54.0  | May 15, 2024 | Feature documentation remains marked as deprecated. | None |
-| 1.55.0  | July 13, 2024 | Feature and documentation removed. | Feature removal announced in release notes. |
+* In a major release after the behavior is deprecated, the feature and corresponding documentation are removed. When the feature is removed, it is noted in the release notes. The documentation for the feature is also removed.
 
 ## Policy Exceptions