Revert "Update to Breaking changes file (#3550)"

This reverts commit c8e296e.

breaking-changes.md

@@ -12,14 +12,17 @@ permalink: /breaking-changes/
 
 The `type` parameter has been removed from all OpenSearch API endpoints. Instead, indexes can be categorized by document type. For more details, see issue [#1940](https://github.com/opensearch-project/opensearch/issues/1940).
 
-### Deprecate non-inclusive terms 
+### Deprecate outdated nomenclature 
 
-Non-inclusive terms are deprecated in version 2.x and will be permanently removed in OpenSearch 3.0.  We are using the following replacements: 
+In order for OpenSearch to include more inclusive naming conventions, we've replaced the following terms in our code with more inclusive terms:
 
 - "Whitelist" is now "Allow list"
 - "Blacklist" is now "Deny list"
 - "Master" is now "Cluster Manager"
 
+If you are using any outdated terms in the context of the security APIs or for node management, your calls and automation will continue to work in all 2.x releases. However, support for the outdated terms will be removed in 3.0 -- which will be a breaking change -- so plan accordingly.  
+{: .warning}
+
 ### Add OpenSearch Notifications plugins
 
 In OpenSearch 2.0, the Alerting plugin is now integrated with new plugins for Notifications. If you want to continue to use the notification action in the Alerting plugin, install the new backend plugins `notifications-core` and `notifications`. If you want to manage notifications in OpenSearch Dashboards, use the new `notificationsDashboards` plugin. For more information, see [Questions about destinations]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/monitors#questions-about-destinations) on the Monitors page.