openstack/barbican
Code Issues Proposed changes

Fix the typo

Browse Source 
Change-Id: I329e6d6289a4d0ba885d221f7b5fe587bc230b7c
This commit is contained in:
liujiong 2016-07-29 23:04:40 +08:00
parent 7af28c8d16
commit 180ea7cb8c
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-guide/source/acls.rst
View File

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

4
api-guide/source/cas.rst
View File

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