Merge pull request #684 from dnmvisser/dv_nitpick1

Fix typos and phrasing in docs

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/howto/config.rst b/docs/howto/config.rst
index 73fd8d41..829100ce 100644
--- a/docs/howto/config.rst
+++ b/docs/howto/config.rst
@@ -189,7 +189,7 @@ Format::
     key_file: "key.pem"
 
 *key_file* is the name of a PEM formatted file that contains the private key
-of the service. This is presently used both to encrypt/sign assertions and as
+ef the service. This is currently used both to encrypt/sign assertions and as
 the client key in an HTTPS session.
 
 metadata
@@ -270,7 +270,7 @@ Where you describe the organization responsible for the service.::
 preferred_binding
 ^^^^^^^^^^^^^^^^^
 
-Which binding should be prefered for a service.
+Which binding should be preferred for a service.
 Example configuration::
 
     "preferred_binding" = {
@@ -340,16 +340,16 @@ accepted_time_diff
 ^^^^^^^^^^^^^^^^^^
 
 If your computer and another computer that you are communicating with are not
-in synch regarding the computer clock, then here you can state how big a
+in sync regarding the computer clock, then here you can state how big a
 difference you are prepared to accept.
 
-.. note:: This will indiscriminately affect all-time comparisons.
-    Hence your server my accept a statement that in fact is too old.
+.. note:: This will indiscriminately affect all time comparisons.
+    Hence your server may accept a statement that in fact is too old.
 
 xmlsec_binary
 ^^^^^^^^^^^^^
 
-Presently xmlsec1 binaries are used for all the signing and encryption stuff.
+Currently xmlsec1 binaries are used for all the signing and encryption stuff.
 This option defines where the binary is situated.
 
 Example::
@@ -385,7 +385,7 @@ Directives that are specific to a certain type of service.
 idp/aa
 ^^^^^^
 
-Directives that are specific to an IdP or AA service instance
+Directives that are specific to an IdP or AA service instance.
 
 sign_assertion
 """"""""""""""
@@ -631,7 +631,7 @@ name_format indicates the name format for that attribute, such as
 
 It is mandatory that at least name or friendly_name is set.
 By default attributes are assumed to be required.
-Missing attributes are infered based on the attribute maps data.
+Missing attributes are inferred based on the attribute maps data.
 
 Example::
 
@@ -846,7 +846,7 @@ or if you want to use for instance memcache::
 
     "subject_data": ("memcached", "localhost:12121"),
 
-*shelve* and *memcached* are the only database types that are presently
+*shelve* and *memcached* are the only database types that are currently
 supported.