diff --git a/CHANGELOG.rst b/CHANGELOG.rst
index 930d6c18..e8b3152d 100644
--- a/CHANGELOG.rst
+++ b/CHANGELOG.rst
@@ -14,7 +14,7 @@ Change Log
 Unreleased
 ~~~~~~~~~~
 
-*
+* Rename toggle_warnings to toggle_warning for consistency with setting_warning.
 
 [5.2.1]
 ~~~~~~~
@@ -26,7 +26,7 @@ Unreleased
 
 * Added Support for Django4 and used djfernet instead of django-fernet-fields
 * Removed Django22, 30 and 31 support
-* Constrained "click" to 7.1.2 as edx-celeryutils constraints the version to this package 
+* Constrained "click" to 7.1.2 as edx-celeryutils constraints the version to this package
 
 
 [4.1.1]
diff --git a/event_routing_backends/processors/caliper/__init__.py b/event_routing_backends/processors/caliper/__init__.py
index 175cb2c0..71b10334 100644
--- a/event_routing_backends/processors/caliper/__init__.py
+++ b/event_routing_backends/processors/caliper/__init__.py
@@ -11,7 +11,7 @@
 # .. toggle_description: Allow sending events to external servers via Caliper.
 #   Toggle intended both for gating initial release and for shutting off all
 #   Caliper events in case of emergency.
-# .. toggle_warnings: Do not enable sending of Caliper events until there has
+# .. toggle_warning: Do not enable sending of Caliper events until there has
 #   been a thorough review of PII implications and safeguards put in place to
 #   prevent accidental leakage of novel event fields to third parties. See
 #   ARCHBOM-1655 for details.
diff --git a/event_routing_backends/processors/xapi/__init__.py b/event_routing_backends/processors/xapi/__init__.py
index 1e49d6c2..479b6ce9 100644
--- a/event_routing_backends/processors/xapi/__init__.py
+++ b/event_routing_backends/processors/xapi/__init__.py
@@ -11,7 +11,7 @@
 # .. toggle_description: Allow sending events to external servers via xAPI.
 #   Toggle intended both for gating initial release and for shutting off all
 #   xAPI events in case of emergency.
-# .. toggle_warnings: Do not enable sending of xAPI events until there has
+# .. toggle_warning: Do not enable sending of xAPI events until there has
 #   been a thorough review of PII implications and safeguards put in place to
 #   prevent accidental leakage of novel event fields to third parties. See
 #   ARCHBOM-1655 for details.