@@ -189,7 +189,7 @@ Format::
189189 key_file: "key.pem"
190190
191191*key_file * is the name of a PEM formatted file that contains the private key
192- of the service. This is presently used both to encrypt/sign assertions and as
192+ of the service. This is currently used both to encrypt/sign assertions and as
193193the client key in an HTTPS session.
194194
195195metadata
@@ -270,7 +270,7 @@ Where you describe the organization responsible for the service.::
270270preferred_binding
271271^^^^^^^^^^^^^^^^^
272272
273- Which binding should be prefered for a service.
273+ Which binding should be preferred for a service.
274274Example configuration::
275275
276276 "preferred_binding" = {
@@ -340,16 +340,16 @@ accepted_time_diff
340340^^^^^^^^^^^^^^^^^^
341341
342342If your computer and another computer that you are communicating with are not
343- in synch regarding the computer clock, then here you can state how big a
343+ in sync regarding the computer clock, then here you can state how big a
344344difference you are prepared to accept.
345345
346- .. note :: This will indiscriminately affect all- time comparisons.
347- Hence your server my accept a statement that in fact is too old.
346+ .. note :: This will indiscriminately affect all time comparisons.
347+ Hence your server may accept a statement that in fact is too old.
348348
349349xmlsec_binary
350350^^^^^^^^^^^^^
351351
352- Presently xmlsec1 binaries are used for all the signing and encryption stuff.
352+ Currently xmlsec1 binaries are used for all the signing and encryption stuff.
353353This option defines where the binary is situated.
354354
355355Example::
@@ -385,7 +385,7 @@ Directives that are specific to a certain type of service.
385385idp/aa
386386^^^^^^
387387
388- Directives that are specific to an IdP or AA service instance
388+ Directives that are specific to an IdP or AA service instance.
389389
390390sign_assertion
391391""""""""""""""
@@ -498,6 +498,8 @@ want_response_signed
498498Indicates that Authentication Responses to this SP must be signed. If set to
499499True, the SP will not consume any SAML Responses that are not signed.
500500
501+ Valid values are True or False. Default value is True.
502+
501503Example::
502504
503505 "service": {
@@ -629,7 +631,7 @@ name_format indicates the name format for that attribute, such as
629631
630632It is mandatory that at least name or friendly_name is set.
631633By default attributes are assumed to be required.
632- Missing attributes are infered based on the attribute maps data.
634+ Missing attributes are inferred based on the attribute maps data.
633635
634636Example::
635637
@@ -844,7 +846,7 @@ or if you want to use for instance memcache::
844846
845847 "subject_data": ("memcached", "localhost:12121"),
846848
847- *shelve * and *memcached * are the only database types that are presently
849+ *shelve * and *memcached * are the only database types that are currently
848850supported.
849851
850852
0 commit comments