summaryrefslogtreecommitdiffstats
path: root/doc/source
diff options
context:
space:
mode:
authorPaul McMillan <paul.mcmillan@nebula.com>2012-04-10 10:52:35 -0700
committerPaul McMillan <paul.mcmillan@nebula.com>2012-04-10 11:29:02 -0700
commit06ae06708cdfcb9d2be97a234c88fc46634a8765 (patch)
tree13d52363dd9a30e6e4874e8ea226b16855a77c9f /doc/source
parent75a8dfef51f3566cd5d4cacee41f34bbbf9d15bd (diff)
Fix "it's" grammar errors.
Change-Id: I32a41a60bc36caaa6bbc71ac24b620a0bb66a6dc
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/configuringservices.rst2
-rw-r--r--doc/source/developing.rst4
-rw-r--r--doc/source/old/endpoints.rst2
3 files changed, 4 insertions, 4 deletions
diff --git a/doc/source/configuringservices.rst b/doc/source/configuringservices.rst
index 2b0a5d2c..a714bd29 100644
--- a/doc/source/configuringservices.rst
+++ b/doc/source/configuringservices.rst
@@ -175,7 +175,7 @@ Configuring Swift to use Keystone
---------------------------------
Similar to Nova, swift can be configured to use Keystone for authentication
-rather than it's built in 'tempauth'.
+rather than its built in 'tempauth'.
1. Add a service endpoint for Swift to Keystone
diff --git a/doc/source/developing.rst b/doc/source/developing.rst
index 11207a95..4acb3b2e 100644
--- a/doc/source/developing.rst
+++ b/doc/source/developing.rst
@@ -60,9 +60,9 @@ You can interact with Keystone through the command line using
:doc:`man/keystone-manage` which allows you to establish tenants, users, etc.
-You can also interact with Keystone through it's REST API. There is a python
+You can also interact with Keystone through its REST API. There is a python
keystone client library `python-keystoneclient`_ which interacts exclusively
-through the REST API, and which keystone itself uses to provide it's
+through the REST API, and which keystone itself uses to provide its
command-line interface.
When initially getting set up, after you've configured which databases to use,
diff --git a/doc/source/old/endpoints.rst b/doc/source/old/endpoints.rst
index bb334543..477592b9 100644
--- a/doc/source/old/endpoints.rst
+++ b/doc/source/old/endpoints.rst
@@ -285,7 +285,7 @@ them all whenever a service changed versions or I added a new service.
To provide a simpler mechanism to manage endpoints on tenants, Keystone uses
Endpoint Templates. I can, for example, define a template with parametrized URLs
-and set it's `global` to true and that will show up as an endpoint on all the tenants
+and set its `global` to true and that will show up as an endpoint on all the tenants
I have. Here is an example:
Define a global Endpoint Template::