diff --git a/doc/source/topics/settings.rst b/doc/source/topics/settings.rst
index ebed8daa61..fdd940e2cd 100644
--- a/doc/source/topics/settings.rst
+++ b/doc/source/topics/settings.rst
@@ -1897,7 +1897,7 @@ is set to False.
 
 .. versionadded:: 10.0.0(Newton)
 
-Template loaders defined here will be be loaded at the end of TEMPLATE_LOADERS,
+Template loaders defined here will be loaded at the end of TEMPLATE_LOADERS,
 after the CACHED_TEMPLATE_LOADERS and will never have a cached output.
 
 ``NG_TEMPLATE_CACHE_AGE``
diff --git a/doc/source/topics/testing.rst b/doc/source/topics/testing.rst
index 122e345301..45153fb2d9 100644
--- a/doc/source/topics/testing.rst
+++ b/doc/source/topics/testing.rst
@@ -439,7 +439,7 @@ attached to every `gate-horizon-dsvm-integration` finished job is that the test
 failure may appear either as failure (assertion failed), or as error (expected
 element didn't show up). In both cases an inquirer should suspect a legitimate
 failure first (i.e., treat errors as failures). Unfortunately, no clear method
-exists for the separation of "good" from from "bad" failures. Each case is
+exists for the separation of "good" from "bad" failures. Each case is
 unique and full of mysteries.
 
 The Horizon testing mechanism tries to alleviate this ambiguity by providing