Fix minor doc typos

Author: lonetwin

docs/source/basic-tutorial.md

@@ -26,7 +26,7 @@ functions available in the `REALM` object (see gssapi-console.py in
 try `$ run-lit -e gssapi basic-tutorial.md` when you have both
 gssapi_console and yalpt installed).  Any actions performed using the
 `REALM` object are not part of the GSSAPI library; the `REALM` object
-simply contians wrappers to krb5 commands generally run separately from
+simply contains wrappers to krb5 commands generally run separately from
 the application using GSSAPI.
 
 Names and Credentials
@@ -36,7 +36,7 @@ Two important concepts in GSSAPI are *names* and *credentials*.
 
 *Names*, as the name suggests, identify different entities, be they
 users or services.  GSSAPI has the concept of different *name types*.
-These represent different types of names and corresponding sytaxes
+These represent different types of names and corresponding syntax
 for representing names as strings.
 
 Suppose we wanted to refer to an HTTP server on the current host.
@@ -95,7 +95,7 @@ Credentials have a *usage*: 'accept' for accepting security contexts,
 credentials used for both initiating and accepting security contexts.
 
 Credentials also have an associated *name*, *lifetime* (which may
-be `None` for indefinite), and set of *mechansims* with which the
+be `None` for indefinite), and set of *mechanisms* with which the
 credentials are usable:
 
     >>> server_creds.usage
@@ -132,7 +132,7 @@ the user's already acquired credentials:
     >>>
 
 Just like credentials, security contexts are either initiating
-contexts, or accepting contexts (they cannot be both).  Initating
+contexts, or accepting contexts (they cannot be both).  Initiating
 contexts must specify at least a target name.  In this case,
 we indicate that we wish to establish a context with the HTTP server
 from above.  The http server can then accept that context:
@@ -186,7 +186,7 @@ messages, or just sign them:
     >>>
 
 Manually passing in a second parameter and checking whether or not encryption
-was used can get tedious, so python-gssapi provides two convinience methods
+was used can get tedious, so python-gssapi provides two convenience methods
 to help with this: `encrypt` and `decrypt`.  If the context is set up to use
 encryption, they will call `wrap` with encryption.  If not, they will
 call `wrap` without encryption.

docs/source/credstore.rst

@@ -2,7 +2,7 @@ Common Values for Credentials Store Extensions
 ==============================================
 
 The credentials store extension is an extension introduced by the MIT krb5
-library implementation of GSSAPI. It allows for finer control of creedntials
+library implementation of GSSAPI. It allows for finer control of credentials
 from within a GSSAPI application.
 Each mechanism can define keywords to manipulate various aspects of their
 credentials for storage or retrieval operations.

docs/source/gssapi.rst

@@ -46,7 +46,7 @@ Enums and Helper Classes
 ------------------------
 
 The following enumerations from the low-level API are also
-used with the high-level API.  For convienience, the are
+used with the high-level API.  For convenience, they are
 imported in the high-level API :mod:`gssapi` module:
 
 .. autoclass:: gssapi.NameType
@@ -68,7 +68,7 @@ imported in the high-level API :mod:`gssapi` module:
 .. autoclass:: gssapi.AddressType
     :show-inheritance:
 
-Similiarly, there are a couple classes from the low-level API
+Similarly, there are a couple classes from the low-level API
 that are imported into the high-level API module.  These classes
 are less likely to be used directly by a user, but are returned
 by several methods: