From 180ea7cb8c0ab512a8a1fb4d21c0362603731867 Mon Sep 17 00:00:00 2001 From: liujiong Date: Fri, 29 Jul 2016 23:04:40 +0800 Subject: [PATCH] Fix the typo Change-Id: I329e6d6289a4d0ba885d221f7b5fe587bc230b7c --- api-guide/source/acls.rst | 2 +- api-guide/source/cas.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/api-guide/source/acls.rst b/api-guide/source/acls.rst index a5123bf0..323dbc69 100644 --- a/api-guide/source/acls.rst +++ b/api-guide/source/acls.rst @@ -41,7 +41,7 @@ An operation specific ACL definition has following attribute: * `project-access`: Flag to mark a secret or a container private for an operation. Pass `false` to mark private. -To acommplish above mentioned behavior for a secret/container resource, having ACL data populated +To accomplish above mentioned behavior for a secret/container resource, having ACL data populated alone is not sufficient. Following ACL rules are defined and used as `OR` in resource access policy: diff --git a/api-guide/source/cas.rst b/api-guide/source/cas.rst index cd947e2a..e982127f 100644 --- a/api-guide/source/cas.rst +++ b/api-guide/source/cas.rst @@ -7,7 +7,7 @@ public and private) to issue, renew and revoke certificates. In PKI parlance, barbican acts as a Registration Authority for these CAs. This interaction is done through certificate plugins, which in turn, can talk -to one of more CAs. Details about the CA each plugin communicates with are +to one or more CAs. Details about the CA each plugin communicates with are updated by the plugins. This includes details like the CA name, description, signing cert and PKCS#7 certificate chain. @@ -31,7 +31,7 @@ reference the Listing CAs ########### -To see the list of CA's that are currently configured, you can query the cas +To see the list of CAs that are currently configured, you can query the cas resource: .. code-block:: bash