diff --git a/doc/source/devref/callbacks.rst b/doc/source/devref/callbacks.rst
index cb8bab51061..bce93be422f 100644
--- a/doc/source/devref/callbacks.rst
+++ b/doc/source/devref/callbacks.rst
@@ -359,7 +359,7 @@ Is there any ordering guarantee during notifications?
   notified. Priorities can be a future extension, if a use case arises that require enforced
   ordering.
 
-How is the the notifying object expected to interact with the subscribing objects?
+How is the notifying object expected to interact with the subscribing objects?
 
   The ``notify`` method implements a one-way communication paradigm: the notifier sends a message
   without expecting a response back (in other words it fires and forget). However, due to the nature
diff --git a/doc/source/devref/tag.rst b/doc/source/devref/tag.rst
index 1c4813c0172..05ffcb470af 100644
--- a/doc/source/devref/tag.rst
+++ b/doc/source/devref/tag.rst
@@ -41,7 +41,7 @@ can be applicable to any other Neutron resource:
 3) Leverage tags by deployment tools
 
 4) allow operators to tag information about provider networks
-   (e.g. high-bandwith, low-latency, etc)
+   (e.g. high-bandwidth, low-latency, etc)
 
 5) new features like get-me-a-network or a similar port scheduler
    could choose a network for a port based on tags