From 2d84214a12466933db360b72608db143706454ae Mon Sep 17 00:00:00 2001
From: Viktor Larsson <viktor@wemadeyoulook.at>
Date: Thu, 9 Feb 2017 14:26:51 +0100
Subject: [PATCH] Fixes spelling error in WSSecurityCert-section. Changed the
 word 'succefully' to 'successfully'

---
 Readme.md | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/Readme.md b/Readme.md
index 7f4792c0f..637f3b77c 100644
--- a/Readme.md
+++ b/Readme.md
@@ -436,18 +436,18 @@ client.MyService.MyPort.MyFunction({name: 'value'}, options, extraHeaders, funct
 Client instances emit the following events:
 
 * request - Emitted before a request is sent. The event handler receives the
-entire Soap request (Envelope) including headers. The second parameter is the exchange id. 
+entire Soap request (Envelope) including headers. The second parameter is the exchange id.
 * message - Emitted before a request is sent. The event handler receives the
-Soap body contents. Useful if you don't want to log /store Soap headers. The second parameter is the exchange id. 
+Soap body contents. Useful if you don't want to log /store Soap headers. The second parameter is the exchange id.
 * soapError - Emitted when an erroneous response is received.
   Useful if you want to globally log errors.
-  The second parameter is the exchange id. 
+  The second parameter is the exchange id.
 * response - Emitted after a response is received. The event handler receives
 the SOAP response body as well as the entire `IncomingMessage` response object.
-The third parameter is the exchange id. 
+The third parameter is the exchange id.
 This is emitted for all responses (both success and errors).
 
-An 'exchange' is a request/response couple. 
+An 'exchange' is a request/response couple.
 Event handlers receive the exchange id in all events.
 The exchange id is the same for the requests events and the responses events, this way you can use it to retrieve the matching request
 when an response event is received.
@@ -458,7 +458,7 @@ Example :
 
 ```javascript
   client.MyService.MyPort.MyFunction(args , function(err, result) {
-      
+
   }, {exchangeId: myExchangeId})
 ```
 
@@ -526,7 +526,7 @@ WS-Security X509 Certificate support.
   client.setSecurity(wsSecurity);
 ```
 
-_Note_: Optional dependency 'ursa' is required to be installed succefully when WSSecurityCert is used.
+_Note_: Optional dependency 'ursa' is required to be installed successfully when WSSecurityCert is used.
 
 ## Handling XML Attributes, Value and XML (wsdlOptions).
 Sometimes it is necessary to override the default behaviour of `node-soap` in order to deal with the special requirements
@@ -660,32 +660,32 @@ To do so, you can pass an customDeserializer object in options. The properties o
 
 Example :
 ```javascript
-   
+
    var wsdlOptions = {
      customDeserializer = {
-     
+
        // this function will be used to any date found in soap responses
        date: function (text, context) {
          /* text is the value of the xml element.
-           context contains the name of the xml element and other infos : 
-             { 
+           context contains the name of the xml element and other infos :
+             {
                  name: 'lastUpdatedDate',
                  object: {},
                  schema: 'xsd:date',
                  id: undefined,
-                 nil: false 
+                 nil: false
              }
-                    
+
           */
          return text;
        }
      }
    };
-   
+
    soap.createClient(__dirname + '/wsdl/default_namespace.wsdl', wsdlOptions, function (err, client) {
      ...
    });
-   
+
 ```
 
 ## Handling "ignored" namespaces