From 061d746ca32aa746e07c32933962d7391fd5f9c8 Mon Sep 17 00:00:00 2001
From: zhaoleilc <15247232416@163.com>
Date: Sat, 11 Jul 2020 11:31:53 +0800
Subject: [PATCH] Correct a typo in the document

This patch changes 'stoped' to 'stopped'
in deploy-guide/source/post_deployment/
backup_and_restore/04_overcloud_restore.rst

Change-Id: I8ecb3abb8fb2e0365e26c76da4b3f6ca9f1aeb08
---
 .../post_deployment/backup_and_restore/04_overcloud_restore.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/deploy-guide/source/post_deployment/backup_and_restore/04_overcloud_restore.rst b/deploy-guide/source/post_deployment/backup_and_restore/04_overcloud_restore.rst
index 21841331..7c3658a2 100644
--- a/deploy-guide/source/post_deployment/backup_and_restore/04_overcloud_restore.rst
+++ b/deploy-guide/source/post_deployment/backup_and_restore/04_overcloud_restore.rst
@@ -32,7 +32,7 @@ In the case we have updated the packages correctly, and the user has an
 issue with updating the database schemas, we might need to restore the
 database cluster.
 
-With all the services stoped in the Overcloud controllers (except MySQL), go through
+With all the services stopped in the Overcloud controllers (except MySQL), go through
 the following procedure:
 
 On all the controller nodes, drop connections to the database port via the VIP by running::