diff --git a/breaking-changes.md b/breaking-changes.md
index 72d8f7d8..4b07761e 100644
--- a/breaking-changes.md
+++ b/breaking-changes.md
@@ -15,9 +15,9 @@ The `type` parameter has been removed from all OpenSearch API endpoints. Instead
 
 In order for OpenSearch to include more inclusive naming conventions, we've replaced the following terms in our code with a more inclusive term:
 
-- "White list" is now "Allow list".
-- "Black list is now "Block list".
-- "Master" is now "Cluster Manager".
+- "White list" is now "Allow list"
+- "Black list is now "Block list"
+- "Master" is now "Cluster Manager"
 
 If you are still using the outdated terms in the context of the security APIs or for node management, your calls and automation will continue to work until the terms are removed later in 2022. 
 
@@ -25,6 +25,6 @@ If you are still using the outdated terms in the context of the security APIs or
 
 The override main response setting `compatibility.override_main_response_version` is deprecated from OpenSearch version 1.x and removed from OpenSearch 2.0.0. This setting is no longer supported for compatibility with legacy clients.
 
-### Add OpenSearch Notifications Plugin
+### 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.
\ No newline at end of file