Fix typos in documents and comments
Fix typos detected by toolkit misspellings. * pip install misspellings * git ls-files | grep -v locale | misspellings -f - Change-Id: If986f8cfefae08089caa567618dbb13bff0d62d2
This commit is contained in:
parent
c8099159f9
commit
e8f104ad85
|
@ -24,7 +24,7 @@ from sphinx import apidoc
|
||||||
|
|
||||||
# NOTE(dstanek): pbr will run Sphinx multiple times when it generates
|
# NOTE(dstanek): pbr will run Sphinx multiple times when it generates
|
||||||
# documentation. Once for each builder. To run this extension we use the
|
# documentation. Once for each builder. To run this extension we use the
|
||||||
# 'builder-inited' hook that fires at the begining of a Sphinx build.
|
# 'builder-inited' hook that fires at the beginning of a Sphinx build.
|
||||||
# We use ``run_already`` to make sure apidocs are only generated once
|
# We use ``run_already`` to make sure apidocs are only generated once
|
||||||
# even if Sphinx is run multiple times.
|
# even if Sphinx is run multiple times.
|
||||||
run_already = False
|
run_already = False
|
||||||
|
|
|
@ -78,7 +78,7 @@ Example::
|
||||||
|
|
||||||
In case the Extension is overriding or re-implementing an existing portion of
|
In case the Extension is overriding or re-implementing an existing portion of
|
||||||
Keystone the required change should be commented in the `configuration.rst` but
|
Keystone the required change should be commented in the `configuration.rst` but
|
||||||
not placed in the `keystone.conf.sample` file to avoid unecessary confusion.
|
not placed in the `keystone.conf.sample` file to avoid unnecessary confusion.
|
||||||
|
|
||||||
|
|
||||||
`keystone-paste.ini` File
|
`keystone-paste.ini` File
|
||||||
|
|
|
@ -1349,7 +1349,7 @@ Read Only LDAP
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
Many environments typically have user and group information in directories that
|
Many environments typically have user and group information in directories that
|
||||||
are accessable by LDAP. This information is for read-only use in a wide array
|
are accessible by LDAP. This information is for read-only use in a wide array
|
||||||
of applications. Prior to the Havana release, we could not deploy Keystone with
|
of applications. Prior to the Havana release, we could not deploy Keystone with
|
||||||
read-only directories as backends because Keystone also needed to store
|
read-only directories as backends because Keystone also needed to store
|
||||||
information such as projects, roles, domains and role assignments into the
|
information such as projects, roles, domains and role assignments into the
|
||||||
|
|
|
@ -38,14 +38,14 @@ class Token(auth.AuthMethodHandler):
|
||||||
target=METHOD_NAME)
|
target=METHOD_NAME)
|
||||||
token_id = auth_payload['id']
|
token_id = auth_payload['id']
|
||||||
response = self.provider.validate_token(token_id)
|
response = self.provider.validate_token(token_id)
|
||||||
#for V3 tokens, the esential data is under the 'token' value.
|
#for V3 tokens, the essential data is under the 'token' value.
|
||||||
#For V2, the comparable data was nested under 'access'
|
#For V2, the comparable data was nested under 'access'
|
||||||
token_ref = response.get('token', response.get('access'))
|
token_ref = response.get('token', response.get('access'))
|
||||||
|
|
||||||
#Do not allow tokens used for delegation to
|
#Do not allow tokens used for delegation to
|
||||||
#create another token, or perform any changes of
|
#create another token, or perform any changes of
|
||||||
#state in Keystone. TO do so is to invite elevation of
|
#state in Keystone. TO do so is to invite elevation of
|
||||||
#priviledge attacks
|
#privilege attacks
|
||||||
if 'OS-TRUST:trust' in token_ref:
|
if 'OS-TRUST:trust' in token_ref:
|
||||||
raise exception.Forbidden()
|
raise exception.Forbidden()
|
||||||
if 'trust' in token_ref:
|
if 'trust' in token_ref:
|
||||||
|
|
|
@ -68,7 +68,7 @@ class MemcachedLock(object):
|
||||||
i += 1
|
i += 1
|
||||||
else:
|
else:
|
||||||
raise exception.UnexpectedError(
|
raise exception.UnexpectedError(
|
||||||
_('Maximum lock attempts on %s occured.') % self.key)
|
_('Maximum lock attempts on %s occurred.') % self.key)
|
||||||
|
|
||||||
def release(self):
|
def release(self):
|
||||||
client = self.client_fn()
|
client = self.client_fn()
|
||||||
|
|
|
@ -16,7 +16,7 @@
|
||||||
|
|
||||||
|
|
||||||
"""
|
"""
|
||||||
PEM formatted data is used frequenlty in conjunction with X509 PKI as
|
PEM formatted data is used frequently in conjunction with X509 PKI as
|
||||||
a data exchange mechanism for binary data. The acronym PEM stands for
|
a data exchange mechanism for binary data. The acronym PEM stands for
|
||||||
Privacy Enhanced Mail as defined in RFC-1421. Contrary to expectation
|
Privacy Enhanced Mail as defined in RFC-1421. Contrary to expectation
|
||||||
the PEM format in common use has little to do with RFC-1421. Instead
|
the PEM format in common use has little to do with RFC-1421. Instead
|
||||||
|
@ -24,7 +24,7 @@ what we know as PEM format grew out of the need for a data exchange
|
||||||
mechanism largely by the influence of OpenSSL. Other X509
|
mechanism largely by the influence of OpenSSL. Other X509
|
||||||
implementations have adopted it.
|
implementations have adopted it.
|
||||||
|
|
||||||
Unfortunately PEM format has never been officialy standarized. It's
|
Unfortunately PEM format has never been officially standarized. It's
|
||||||
basic format is as follows:
|
basic format is as follows:
|
||||||
|
|
||||||
1) A header consisting of 5 hyphens followed by the word BEGIN and a
|
1) A header consisting of 5 hyphens followed by the word BEGIN and a
|
||||||
|
@ -38,7 +38,7 @@ text may be less than 64 characters. The content and format of the
|
||||||
binary data is entirely dependent upon the type of data announced in
|
binary data is entirely dependent upon the type of data announced in
|
||||||
the header and footer.
|
the header and footer.
|
||||||
|
|
||||||
3) A footer in the exact same as the header execpt the word BEGIN is
|
3) A footer in the exact same as the header except the word BEGIN is
|
||||||
replaced by END. The content name in both the header and footer should
|
replaced by END. The content name in both the header and footer should
|
||||||
exactly match.
|
exactly match.
|
||||||
|
|
||||||
|
|
|
@ -994,7 +994,7 @@ class RestfulTestCase(rest.RestfulTestCase):
|
||||||
|
|
||||||
if summary:
|
if summary:
|
||||||
# Trust list contains no roles, but getting a specific
|
# Trust list contains no roles, but getting a specific
|
||||||
# trust by ID provides the detailed reponse containing roles
|
# trust by ID provides the detailed response containing roles
|
||||||
self.assertNotIn('roles', entity)
|
self.assertNotIn('roles', entity)
|
||||||
self.assertIn('project_id', entity)
|
self.assertIn('project_id', entity)
|
||||||
else:
|
else:
|
||||||
|
|
Loading…
Reference in New Issue