Wrong usage of "an"
an historical anomaly -> a historical anomaly an token -> a token Change-Id: Id4b50e2e3e6f5a0c65107ddf6faeb7d6c45ca9ef
This commit is contained in:
parent
7f485562f9
commit
1bb8f18680
|
@ -28,7 +28,7 @@ Tokens
|
||||||
Default scope
|
Default scope
|
||||||
-------------
|
-------------
|
||||||
|
|
||||||
Get an token with default scope (may be unscoped):
|
Get a token with default scope (may be unscoped):
|
||||||
|
|
||||||
.. code-block:: bash
|
.. code-block:: bash
|
||||||
|
|
||||||
|
|
|
@ -73,7 +73,7 @@ services are configured to run in a single process.
|
||||||
|
|
||||||
.. NOTE::
|
.. NOTE::
|
||||||
|
|
||||||
The separation into ``admin`` and ``main`` interfaces is an historical
|
The separation into ``admin`` and ``main`` interfaces is a historical
|
||||||
anomaly. The new V3 API provides the same interface on both the admin and
|
anomaly. The new V3 API provides the same interface on both the admin and
|
||||||
main interfaces (this can be configured in ``keystone-paste.ini``, but the
|
main interfaces (this can be configured in ``keystone-paste.ini``, but the
|
||||||
default is to have both the same). The V2.0 API provides a limited public
|
default is to have both the same). The V2.0 API provides a limited public
|
||||||
|
|
Loading…
Reference in New Issue