Grammar check.

Documentation/4.0/Raven.Documentation.Pages/client-api/configuration/load-balance-and-failover.dotnet.markdown

@@ -4,7 +4,7 @@
 
 ###ReadBalanceBehavior
 
-* This convention gets or sets the default load-balancing behaviour of ***Read*** requests done from the client to RavenDB cluster.  
+* This convention gets or sets the default load-balancing behavior of ***Read*** requests done from the client to RavenDB cluster.  
 
 * The method selected in the convention determines which node the client's _RequestExecuter_ will send the ***Read*** requests to,  
   and which node to **failover** to in case of issues with the ***Read*** request.  
@@ -35,26 +35,26 @@
   * `FastestNode`  
     * Load-balance: _Read_ request will go to the fastest node.  
       The fastest node is determined by a [Speed Test](../../client-api/cluster/speed-test).  
-    * Failover: In case of a failure, speed test will be triggered again and in the meantime, the client will use the _preferred node_.  
+    * Failover: In case of a failure, a speed test will be triggered again and in the meantime the client will use the _preferred node_.  
 {PANEL/}
 
 {PANEL: Preferred Node}
 
 * The preferred node is selected by simply going over the _topology nodes list_ and returning the first node that has not had any errors.  
 
-* If all nodes are in a failure state then the _first_ node in the list is returned, the user would get an error or recover if the error was transient.  
+* If all nodes are in a failure state then the _first_ node in the list is returned and the user would get an error or recover if the error was transient.  
 {PANEL/}
 
 {PANEL: Session Usage}
 
 * When using `RoundRobin` or `FastestNode` it might happen that the next [session](../../client-api/session/opening-a-session) you open will access a different node.  
 
-* In most cases, a short delay in replicating changes to all nodes in the cluster is acceptable.  
-  But, if you need to ensure that the next request will be able to immediately read what you just wrote, 
+* In most cases a short delay in replicating changes to all nodes in the cluster is acceptable.  
+  But if you need to ensure that the next request will be able to immediately read what you just wrote, 
   you need to use [write assurance](../../client-api/session/saving-changes#waiting-for-replication---write-assurance).  
 {PANEL/}
 
-## Related articles
+## Related Articles
 
 ### Configuration
 

Documentation/4.0/Raven.Documentation.Pages/indexes/querying/morelikethis.dotnet.markdown

@@ -4,13 +4,13 @@ MoreLikeThis returns a list of similar documents that are related to a given doc
 
 ## Setup
 
-In order to work, MoreLikeThis requires access to the text in the index, therefore, the index being queried needs to [store](../../indexes/storing-data-in-index) the fields or store the [term vectors](../../indexes/using-term-vectors) for those fields.
+In order to work, MoreLikeThis requires access to the text in the index. Therefore, the index being queried needs to [store](../../indexes/storing-data-in-index) the fields or store the [term vectors](../../indexes/using-term-vectors) for those fields.
 
 {CODE more_like_this_4@Indexes\Querying\MoreLikeThis.cs /}
 
 ## Basic Usage
 
-MoreLikeThis has many defaults already set, and the simplest mode will satisfy the majority of the usage scenarios.
+MoreLikeThis has many defaults already set and the simplest mode will satisfy the majority of the usage scenarios.
 
 {CODE-TABS}
 {CODE-TAB:csharp:Query more_like_this_1@Indexes\Querying\MoreLikeThis.cs /}

Documentation/4.0/Raven.Documentation.Pages/studio/database/settings/client-configuration-per-database.markdown

@@ -14,10 +14,10 @@
 
 * **1**. Override Server Configuration -  
       This option needs to be checked in order to be able to override the existing requests configuration.  
-      If not checked, then the existing general server requests configuration will be used.  
+      If not checked, the existing general server requests configuration will be used.  
 
 * **2**. Check these options to actually override the existing [general server requests configuration](../../../studio/server/client-configuration).  
-      If not checked, when the above 'override' is turned on, then the Effective Configuration will be: 'Client Default'.  
+      If not checked, when the above 'override' is turned on, the Effective Configuration will be: 'Client Default'.  
 
 * **3**. Set the specific _read-balance_ method and the _max requests_ number value desired for this database.  
       For a detailed explanation about each field see: [server requests configuration](../../../studio/server/client-configuration) 
@@ -33,7 +33,7 @@ This view will be as in the above image when a general configuration is defined.
 If a general configuration is not yet defined then this view will be similar to the general server configuration view.  
 {NOTE/}
 
-## Related articles
+## Related Articles
 
 - [Requests Configuration in Cluster](../../../studio/server/client-configuration)
 - [Load Balance & Failover](../../../client-api/configuration/load-balance-and-failover)

Documentation/4.0/Raven.Documentation.Pages/studio/server/client-configuration.markdown

@@ -3,7 +3,7 @@
 
 {NOTE: }
 
-* Configure the RavenDB client requests behaviour for ***all*** databases in the cluster  
+* Configures the RavenDB client requests behavior for ***all*** databases in the cluster  
 
 * These default values can be overwritten ***per database*** in [Client Requests Configuration - per database](../../studio/database/settings/client-configuration-per-database)  
 {NOTE/}
@@ -18,7 +18,7 @@
 
   * Set the load-balance method that the client will use when accessing a node with ***Read*** requests.  
   The method selected will also affect the client's decision of which node to failover to in case of issues with the ***Read*** request.  
-  Note: ***Write*** requests will always access the [preffered node](../../client-api/configuration/load-balance-and-failover#preferred-node) calculated by the client.  
+  Note: ***Write*** requests will always access the [preferred node](../../client-api/configuration/load-balance-and-failover#preferred-node) calculated by the client.  
 
   * Available options are:  
      * _None_