Minor fix (dotnet#9235)

* minor fix

* removed double fullstop

* fixed typo

* fixed typo

Author: ThePiranha

docs/framework/configure-apps/file-schema/wcf/findcriteria.md

@@ -40,15 +40,15 @@ A configuration element that supplies a set of criteria used by a client applica
 
 |Attribute|Description|  
 |---------------|-----------------|  
-|duration|A Timespan value that specifies the maximum time to wait for replies from services on the network. The default duration is 20 seconds..|  
+|duration|A Timespan value that specifies the maximum time to wait for replies from services on the network. The default duration is 20 seconds.|  
 |maxResults|An integer that specifies the maximum number of replies to wait for, from services on a network or the Internet. If maximum replies are received before the value specified in the `duration` attribute has elapsed, the find operation ends.|  
 |scopeMatchBy|A URI that specify the matching algorithm to use while matching the scopes in the Probe message with that of the endpoint.<br /><br /> There are five supported scope-matching rules. If you do not specify a scope-matching rule, `ScopeMatchByPrefix` is used. For more information on this, see <xref:System.ServiceModel.Discovery.FindCriteria>.|  
 
 ### Child Elements  
 
 |Element|Description|  
 |-------------|-----------------|  
-|[\<contractTypeNames>](../../../../../docs/framework/configure-apps/file-schema/wcf/contracttypenames.md)|A collection of configuration elements that contain the names of workflow service contract types..|  
+|[\<contractTypeNames>](../../../../../docs/framework/configure-apps/file-schema/wcf/contracttypenames.md)|A collection of configuration elements that contain the names of workflow service contract types.|  
 |\<extensions> of \<findCriteria>|A collection of XML element objects that provide extensions.|  
 |[\<scopes>](../../../../../docs/framework/configure-apps/file-schema/wcf/scopes.md)|A collection of objects that contain absolute URIs that are used during a find operation to locate a specific service or services.<br /><br /> If the specific service is found, a successful match has been made between the service URI and the Scope URI, sometimes with the help of scope rules that handle complications of matching.|  
 

docs/framework/configure-apps/file-schema/wcf/message-of-wsdualhttpbinding.md

@@ -46,7 +46,7 @@ Defines message-level security for the [\<wsDualHttpBinding>](../../../../../doc
 |Basic256|Use Aes256 encryption, Sha1 for message digest, Rsa-oaep-mgf1p for key wrap.|  
 |Basic256Rsa15|Use Aes256 for message encryption, Sha1 for message digest and Rsa15 for key wrap.|  
 |Basic192Rsa15|Use Aes192 for message encryption, Sha1 for message digest and Rsa15 for key wrap.|  
-|TripleDes|Use TripleDes encryption, , Sha1 for message digest, Rsa-oaep-mgf1p for key wrap.|  
+|TripleDes|Use TripleDes encryption, Sha1 for message digest, Rsa-oaep-mgf1p for key wrap.|  
 |Basic128Rsa15|Use Aes128 for message encryption, Sha1 for message digest and Rsa15 for key wrap.|  
 |TripleDesRsa15|Use TripleDes encryption, Sha1 for message digest and Rsa15 for key wrap.|  
 |Basic128Sha256|Use Aes256 for message encryption, Sha256 for message digest and Rsa-oaep-mgf1p for key wrap.|  

docs/framework/configure-apps/file-schema/wcf/msmqintegration.md

@@ -52,7 +52,7 @@ Specifies a MSMQ transport for custom binding.
 |exactlyOnce|A Boolean that specifies whether messages processed by this binding will be received exactly once. The default is `true`.<br /><br /> A message can be sent with or without assurances. An assurance enables an application to ensure that a sent message reached the receiving message queue, or if it did not, the application can determine this by reading the dead letter queue.<br /><br /> `exactlyOnce`, when set to `true`, indicates that MSMQ will ensure that a sent message is delivered to the receiving message queue once and only once, and if delivery fails, the message is sent to the dead letter queue.<br /><br /> Messages sent with `exactlyOnce` set to `true` must be sent to a transactional queue only.|  
 |manualAddressing|A Boolean value that enables the user to take control of message addressing. This property is usually used in router scenarios, where the application determines which one of several destinations to send a message to.<br /><br /> When set to `true`, the channel assumes the message has already been addressed and does not add any additional information to it. The user can then address every message individually.<br /><br /> When set to `false`, the default Windows Communication Foundation (WCF) addressing mechanism automatically creates addresses for all messages.<br /><br /> The default is `false`.|  
 |maxBufferPoolSize|A positive integer that specifies the maximum size of the buffer pool. The default is 524288.<br /><br /> Many parts of WCF use buffers. Creating and destroying buffers each time they are used is expensive, and garbage collection for buffers is also expensive. With buffer pools, you can take a buffer from the pool, use it, and return it to the pool once you are done. Thus the overhead in creating and destroying buffers is avoided.|  
-|maxImmediateRetries|An integer that specifies the maximum number of immediate retry attempts on a message that is read from the application queue.. The default is 5.<br /><br /> If the maximum number of immediate retries for the message is attempted and the message is not consumed by the application, then the message is sent to a retry queue for retrying at some later point in time. If no retry cycles are specified, then the messages is either sent to the poison message queue, or a negative acknowledgment is sent back to the sender.|  
+|maxImmediateRetries|An integer that specifies the maximum number of immediate retry attempts on a message that is read from the application queue. The default is 5.<br /><br /> If the maximum number of immediate retries for the message is attempted and the message is not consumed by the application, then the message is sent to a retry queue for retrying at some later point in time. If no retry cycles are specified, then the messages is either sent to the poison message queue, or a negative acknowledgment is sent back to the sender.|  
 |maxReceivedMessageSize|A positive integer that specifies the maximum message size in bytes including headers. The sender of a message receives a SOAP fault when the message is too large for the receiver. The receiver drops the message and creates an entry of the event in the trace log. The default is 65536.|  
 |maxRetryCycles|An integer that specifies the maximum number of retry cycles to attempt delivery of messages to the receiving application. The default is <xref:System.Int32.MaxValue>.<br /><br /> A single retry cycle attempts to deliver a message to an application a specified number of times. The number of attempts made is set by the `maxImmediateRetries` attribute. If the application fails to consume the message after the attempts at delivery have been exhausted, the message is sent to a retry queue. Subsequent retry cycles consist of the message being returned from the retry queue to the application queue to attempt delivery to the application again, after a delay specified by the `retryCycleDelay` attribute. The `maxRetryCycles` attribute specifies the number of retry cycles the application uses to attempt to deliver the message.|  
 |rejectAfterLastRetry|A Boolean value that specifies what action to take for a message that has failed delivery after the maximum number of retries have been attempted.<br /><br /> `true` means that a negative acknowledgment is returned to the sender and the message is dropped; `false` means that the message is sent to the poison message queue. The default is `false`.<br /><br /> If the value is `false`, the receiving application can read the poison message queue to process poison messages (that is, messages that have failed delivery).<br /><br /> MSMQ 3.0 does not support returning a negative acknowledgment to the sender, so this attribute will be ignored in MSMQ 3.0.|  

docs/framework/configure-apps/file-schema/wcf/msmqtransport.md

@@ -51,7 +51,7 @@ Causes a channel to transfers messages on the MSMQ transport when it is included
 |exactlyOnce|A Boolean that specifies whether messages processed by this binding will be received exactly once. The default is `true`.<br /><br /> A message can be sent with or without assurances. An assurance enables an application to ensure that a sent message reached the receiving message queue, or if it did not, the application can determine this by reading the dead letter queue.<br /><br /> `exactlyOnce`, when set to `true`, indicates that MSMQ will ensure that a sent message is delivered to the receiving message queue once and only once, and if delivery fails, the message is sent to the dead letter queue.<br /><br /> Messages sent with `exactlyOnce` set to `true` must be sent to a transactional queue only.|  
 |manualAddressing|A Boolean value that enables the user to take control of message addressing. This property is usually used in router scenarios, where the application determines which one of several destinations to send a message to.<br /><br /> When set to `true`, the channel assumes the message has already been addressed and does not add any additional information to it. The user can then address every message individually.<br /><br /> When set to `false`, the default Windows Communication Foundation (WCF) addressing mechanism automatically creates addresses for all messages.<br /><br /> The default is `false`.|  
 |maxBufferPoolSize|A positive integer that specifies the maximum size of the buffer pool. The default is 524288.<br /><br /> Many parts of WCF use buffers. Creating and destroying buffers each time they are used is expensive, and garbage collection for buffers is also expensive. With buffer pools, you can take a buffer from the pool, use it, and return it to the pool once you are done. Thus the overhead in creating and destroying buffers is avoided.|  
-|maxImmediateRetries|An integer that specifies the maximum number of immediate retry attempts on a message that is read from the application queue.. The default is 5.<br /><br /> If the maximum number of immediate retries for the message is attempted and the message is not consumed by the application, then the message is sent to a retry queue for retrying at some later point in time. If no retry cycles are specified, then the messages is either sent to the poison message queue, or a negative acknowledgment is sent back to the sender.|  
+|maxImmediateRetries|An integer that specifies the maximum number of immediate retry attempts on a message that is read from the application queue. The default is 5.<br /><br /> If the maximum number of immediate retries for the message is attempted and the message is not consumed by the application, then the message is sent to a retry queue for retrying at some later point in time. If no retry cycles are specified, then the messages is either sent to the poison message queue, or a negative acknowledgment is sent back to the sender.|  
 |maxPoolSize|A positive integer that specifies the maximum size of the pool. The default is 524288.|  
 |maxReceivedMessageSize|A positive integer that specifies the maximum message size in bytes including headers. The sender of a message receives a SOAP fault when the message is too large for the receiver. The receiver drops the message and creates an entry of the event in the trace log. The default is 65536.|  
 |maxRetryCycles|An integer that specifies the maximum number of retry cycles to attempt delivery of messages to the receiving application. The default is <xref:System.Int32.MaxValue>.<br /><br /> A single retry cycle attempts to deliver a message to an application a specified number of times. The number of attempts made is set by the `maxImmediateRetries` attribute. If the application fails to consume the message after the attempts at delivery have been exhausted, the message is sent to a retry queue. Subsequent retry cycles consist of the message being returned from the retry queue to the application queue to attempt delivery to the application again, after a delay specified by the `retryCycleDelay` attribute. The `maxRetryCycles` attribute specifies the number of retry cycles the application uses to attempt to deliver the message.|  

docs/framework/configure-apps/file-schema/wcf/nethttpbinding.md

@@ -133,7 +133,7 @@ Represents a binding that a Windows Communication Foundation (WCF) service can u
 ```  
 
 ## Example  
- Starting with [!INCLUDE[netfx40_short](../../../../../includes/netfx40-short-md.md)], bindings and behaviors are not required to have a name. The functionality from the previous example can be accomplished by removing the bindingConfiguration from the endpoint address and the name frm the binding.  
+ Starting with [!INCLUDE[netfx40_short](../../../../../includes/netfx40-short-md.md)], bindings and behaviors are not required to have a name. The functionality from the previous example can be accomplished by removing the bindingConfiguration from the endpoint address and the name from the binding.  
 
 ```xml  
 <system.serviceModel>   

docs/framework/configure-apps/file-schema/wcf/nethttpsbinding.md

@@ -130,7 +130,7 @@ Next Element
 ```  
 
 ## Example  
- Starting with [!INCLUDE[netfx40_short](../../../../../includes/netfx40-short-md.md)], bindings and behaviors are not required to have a name. The functionality from the previous example can be accomplished by removing the bindingConfiguration from the endpoint address and the name frm the binding.  
+ Starting with [!INCLUDE[netfx40_short](../../../../../includes/netfx40-short-md.md)], bindings and behaviors are not required to have a name. The functionality from the previous example can be accomplished by removing the bindingConfiguration from the endpoint address and the name from the binding.  
 
 ```xml  
 <system.serviceModel>