From a936b28c493a3e3bfef5d14bf86d7ff020a1f5fd Mon Sep 17 00:00:00 2001 From: Nam Nguyen Hoai Date: Fri, 20 Jan 2017 11:47:36 +0700 Subject: [PATCH] Fix typos There are some wrong words, it should be updated. Change-Id: Ib57e056ac43c0e1815ee135f402490f2cef0ad10 --- doc/source/setup/noauth.rst | 2 +- doc/source/setup/plugin_backends.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/setup/noauth.rst b/doc/source/setup/noauth.rst index e405587d9..55a0c72cc 100644 --- a/doc/source/setup/noauth.rst +++ b/doc/source/setup/noauth.rst @@ -33,7 +33,7 @@ To enable this pipe line proceed as follows: With every OpenStack service integrated with keystone, its API requires access token to retireve certain information and validate user's information and -prviledges. If you are running barbican in no auth mode, you have to specify +privileges. If you are running barbican in no auth mode, you have to specify project_id instead of an access token which was retrieved from the token instead. In case of API, replace ``'X-Auth-Token: $TOKEN'`` with ``'X-Project-Id: {project_id}'`` for every API request in :doc:`../api/index`. diff --git a/doc/source/setup/plugin_backends.rst b/doc/source/setup/plugin_backends.rst index 09cf7a836..f3662eee8 100644 --- a/doc/source/setup/plugin_backends.rst +++ b/doc/source/setup/plugin_backends.rst @@ -91,7 +91,7 @@ Multiple backend can be useful in following type of usage scenarios. * HSM devices generally have limited storage capacity so a deployment will have to watch its stored keys size proactively to remain under the limit constraint. This is more applicable in KMIP backend than with PKCS11 backend - because of plugin's different storage apporach. This aspect can also result + because of plugin's different storage approach. This aspect can also result from above use case scenario where deployment is storing non-sensitive (from dev/test environment) encryption keys in HSM. * Barbican running as IaaS service or platform component where some class of