diff --git a/doc/source/operating_guides/upgrades_guide.rst b/doc/source/operating_guides/upgrades_guide.rst
index e1dfa08253..6144184286 100644
--- a/doc/source/operating_guides/upgrades_guide.rst
+++ b/doc/source/operating_guides/upgrades_guide.rst
@@ -40,7 +40,7 @@ Cold Upgrades
 Heat already supports "`cold-upgrades`_", where the heat services have to be
 down during the upgrade. For time-consuming upgrades, it may be unacceptable
 for the services to be unavailable for a long period of time. This type of
-upgrade is quite simple, follow the bellow steps:
+upgrade is quite simple, follow the below steps:
 
 1. Stop all heat-api and heat-engine services.
 
diff --git a/doc/source/template_guide/multi-clouds.rst b/doc/source/template_guide/multi-clouds.rst
index e6266db46b..0038725007 100644
--- a/doc/source/template_guide/multi-clouds.rst
+++ b/doc/source/template_guide/multi-clouds.rst
@@ -124,7 +124,7 @@ To create a remote stack, you can simply use an :ref:`OS::Heat::Stack` resource
 in your template.
 
 In resource properties, provide `credential_secret_id` (Barbican secret ID
-from the secret we just builded for credential) under `context` property.
+from the secret we just built for credential) under `context` property.
 
 Here is an template example for you: