openstack
/
heat
Code Issues Proposed changes

Fix minor typos in documentation 

Change-Id: Ie2f5f65d21186c13e89a784867b488d46ec1a3a2
This commit is contained in:
Takashi Kajinami 2024-01-30 18:27:13 +09:00
parent 313a5afa6a
commit 60a2d9f2ec
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/operating_guides/upgrades_guide.rst
View File

@ -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.

2
doc/source/template_guide/multi-clouds.rst
View File

@ -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: