From 1309ce7c3936c7e649393c9ed8ba04888a942847 Mon Sep 17 00:00:00 2001
From: Christian Berendt <berendt@b1-systems.de>
Date: Wed, 6 May 2015 22:40:23 +0200
Subject: [PATCH] Use 'REST API' instead of 'ReST API'

Change-Id: I6b3cfb749bdf6b8ae058fc7c22458a027ba3f32b
---
 doc/admin-guide-cloud/ch_orchestration.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/admin-guide-cloud/ch_orchestration.xml b/doc/admin-guide-cloud/ch_orchestration.xml
index 532c1e394a..d697065ad9 100644
--- a/doc/admin-guide-cloud/ch_orchestration.xml
+++ b/doc/admin-guide-cloud/ch_orchestration.xml
@@ -31,7 +31,7 @@
         indentation) so it’s more easily to write, parse, grep, generate with
         tools, and maintain with source-code management systems.</para>
     <para>Orchestration can be accessed via the CLI, and using RESTful queries.
-        Orchestration module provides both an OpenStack-native ReST API
+        Orchestration module provides both an OpenStack-native REST API
         and a CloudFormation-compatible Query API. Orchestration is also
         integrated with OpenStack dashboard in order to launching stacks from
         templates through web-interface.</para>