diff --git a/doc/source/developing_guides/rally_on_gates.rst b/doc/source/developing_guides/rally_on_gates.rst
index eded5125b2..59d0dd1a23 100644
--- a/doc/source/developing_guides/rally_on_gates.rst
+++ b/doc/source/developing_guides/rally_on_gates.rst
@@ -131,7 +131,7 @@ Another example of using Rally job is writing custom Rally scenarios in Heat
 repository. There is an example of this is presented on review:
 https://review.openstack.org/#/c/270225/
 
-It's similar on the first examnple, but requires more Rally specific coding.
+It's similar on the first example, but requires more Rally specific coding.
 New tasks in ``heat-fakevirt.yaml`` use undefined in Rally repository
 scenarios:
 
diff --git a/doc/source/template_guide/environment.rst b/doc/source/template_guide/environment.rst
index abaf8d28b9..6f2088f11b 100644
--- a/doc/source/template_guide/environment.rst
+++ b/doc/source/template_guide/environment.rst
@@ -225,7 +225,7 @@ To restrict update or replace, add ``restricted_actions: update`` or
 ``restricted_actions: replace`` to the resource dictionary. You can also
 use ``[update, replace]`` to restrict both actions.
 
-You can combine restrcited actions with other ``resources`` properties such
+You can combine restricted actions with other ``resources`` properties such
 as provider templates or type mapping or hooks::
 
   resource_registry: