From 3cf7f9481596b93bca1a29dce9d283966fbacb48 Mon Sep 17 00:00:00 2001 From: Brant Knudson Date: Fri, 10 Oct 2014 19:16:43 -0500 Subject: [PATCH] Correct typos in using-sessions Fixed typos in using-sessions. Change-Id: Id931bfdb8eb8bf214ca538673e727c6bf1e06280 --- doc/source/using-api-v2.rst | 2 +- doc/source/using-sessions.rst | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/source/using-api-v2.rst b/doc/source/using-api-v2.rst index 192e683c6..52feefac2 100644 --- a/doc/source/using-api-v2.rst +++ b/doc/source/using-api-v2.rst @@ -13,7 +13,7 @@ The main concepts in the Identity v2 API are: * services * endpoints -The client v2 API lets you query and make changes through +The V2 client API lets you query and make changes through managers. For example, to manipulate tenants, you interact with a ``keystoneclient.v2_0.tenants.TenantManager`` object. diff --git a/doc/source/using-sessions.rst b/doc/source/using-sessions.rst index 099dc7017..7d31a2d61 100644 --- a/doc/source/using-sessions.rst +++ b/doc/source/using-sessions.rst @@ -75,13 +75,13 @@ fashion by passing the Session object to the client's constructor. Migrating keystoneclient to use a Session ----------------------------------------- -By using a session with a keystonclient Client we define that you have opted in -to new behaviour defined by the session. For example authentication is now -on-demand rather than on creation. To allow this change in behaviour there are -a number of functions that have changed behaviour or are no longer available. +By using a session with a keystoneclient Client we presume that you have opted +in to new behavior defined by the session. For example authentication is now +on-demand rather than on creation. To allow this change in behavior there are +a number of functions that have changed behavior or are no longer available. For example the -:py:meth:`keystoneclient.httpclient.HTTPClient.authenticate` command used +:py:meth:`keystoneclient.httpclient.HTTPClient.authenticate` method used to be able to always re-authenticate the current client and fetch a new token. As this is now controlled by the Session and not the client this has changed, however the function will still exist to provide compatibility with older