Grammar Check.

Documentation/4.0/Raven.Documentation.Pages/client-api/operations/patching/set-based.dotnet.markdown

@@ -5,7 +5,7 @@ Sometimes we need to update a large amount of documents answering certain criter
 
 `UPDATE Users SET IsActive = 0 WHERE LastLogin < '2010-01-01'`   
 
-This is usually not the case for NoSQL databases, where set based operations are not supported. RavenDB does support them, and by passing it a query and an operation definition. It will run the query and perform that operation on its results.
+This is usually not the case for NoSQL databases where set based operations are not supported. RavenDB does support them by passing it a query and an operation definition. It will run the query and perform that operation on its results.
 
 The same queries and indexes that are used for data retrieval are used for the set based operations. The syntax defining which documents to work on is exactly the same as you'd specified for those documents to be pulled from the store.
 
@@ -18,7 +18,7 @@ In this page:
 
 {PANEL: Syntax overview}
 
-### Sending patch request
+### Sending Patch Request
 
 {CODE [email protected] /}
 
@@ -89,8 +89,7 @@ For indexes that are updated all the time, you can set the AllowStale field of Q
 
 {WARNING: Patching and Concurrency} 
 
-The patching of documents matching a specified query is run in batches of size 1024. RavenDB doesn't do concurrency checks during the operation
-so it can happen than a document has been updated or deleted meanwhile.
+The patching of documents matching a specified query is run in batches of size 1024. RavenDB doesn't do concurrency checks during the operation so it can happen than a document has been updated or deleted meanwhile.
 
 {WARNING/}
 

Documentation/4.0/Raven.Documentation.Pages/client-api/session/querying/how-to-query.dotnet.markdown

@@ -8,8 +8,7 @@ This session explains the following methods to query a database:
 
 ## Session.Query
 
-The most straightforward way to issue a query is by using the `Query` method which allows you to define queries using LINQ. In order to take advantage of querying capabilities specific for RavenDB,
-the querying API provides extension methods that will be described later.
+The most straightforward way to issue a query is by using the `Query` method which allows you to define queries using LINQ. In order to take advantage of querying capabilities specific for RavenDB, the querying API provides extension methods that will be described later.
 
 ### Syntax
 
@@ -35,10 +34,9 @@ the querying API provides extension methods that will be described later.
 
 The above is an example of a dynamic query which doesn't require you to specify an index name. RavenDB will create an auto index automatically if necessary.
 
-The provided `Employee` type as the generic type parameter does not only define the type of returned
-results, but it also indicates that the queried collection will be `Employees`. There is no need to specify it as the parameter.
+The provided `Employee` type as the generic type parameter does not only define the type of returned results, but it also indicates that the queried collection will be `Employees`. There is no need to specify it as the parameter.
 
-### Example II - Linq Syntax Support
+### Example II - LINQ Syntax Support
 
 Both LINQ syntaxes are supported:
 

Documentation/4.0/Raven.Documentation.Pages/migration/client-api/introduction.markdown

@@ -1,10 +1,10 @@
-# Migration : Introduction to 3.x to 4.0 migration
+# Migration : Introduction to 3.x to 4.0 Migration
 
 RavenDB Client 4.0 is a major upgrade. It's not backward compatible and the API has a lot of breaking changes.
 
-This section discusses the changes that you need to be aware of when migrating your application using 3.x DLLs and recommended actions you need to take.
+This section discusses the changes that you need to be aware of when migrating your application using 3.x DLLs, and the recommended actions you need to take.
 
-## 3.x packages
+## 3.x Packages
 
 Please remove the following 3.x packages:
 
@@ -13,14 +13,14 @@ Please remove the following 3.x packages:
 - `RavenDB.Database`
 - `RavenDB.Embedded`
 
-## 4.0 package
+## 4.0 Package
 
-Please install [RavenDB.Client](https://www.nuget.org/packages/RavenDB.Client) package from NuGet. See what [.NET targets are supported](../../client-api/net-client-versions) by RavenDB Client.
+Please install the [RavenDB.Client](https://www.nuget.org/packages/RavenDB.Client) package from NuGet. See what [.NET targets are supported](../../client-api/net-client-versions) by RavenDB Client.
 
-### Internalized Json.NET usage
+### Internalized Json.NET Usage
 
-RavenDB Client doesn't use customized Json.NET any longer. Replace all references to RavenDB Json.NET, like `Raven.Imports.Newtonsoft`, with `Newtonsoft.Json` reference. 
-Please use latest version of Json.NET for good performance.
+RavenDB Client doesn't use a customized Json.NET any longer. Replace all references to RavenDB Json.NET, like `Raven.Imports.Newtonsoft`, with `Newtonsoft.Json` reference. 
+Please use the latest version of Json.NET for good performance.
 
 ### RavenJObject 
 
@@ -29,7 +29,7 @@ with low-level stuff in the client as `BlittableJsonReaderObject` or `BlittableJ
 
 ### Etags
 
-Documents don't have etags. Instead, since documents can be stored in a cluster environment, that is on different nodes, they use a change vector to reflect changes on particular cluster nodes.
+Documents don't have etags. Instead, since documents can be stored in a cluster environment that is on different nodes, they use a change vector to reflect changes on particular cluster nodes.
 The change vector is composed of list of node IDs and a sequential number (per node). The sequential number, still named as the etag, is represented by `long`.
 
 ### Identifiers
@@ -68,6 +68,6 @@ Documents no longer cannot be marked as read-only. The metadata entry `Raven-Rea
 
 Instead of `EmbeddableDocumentStore` your tests should use [RavenDB.TestDriver](https://www.nuget.org/packages/RavenDB.TestDriver) package. See the dedicated [article](../../start/test-driver).
 
-### DTC transactions
+### DTC Transactions
 
 There is no support for DTC transactions.

Documentation/4.0/Raven.Documentation.Pages/migration/server/snmp.markdown

@@ -1,6 +1,6 @@
 # Migration : SNMP
 
-{NOTE Complete list of OID can be found [here](../../server/administration/SNMP/snmp) /}
+{NOTE The complete list of OID can be found [here](../../server/administration/SNMP/snmp) /}
 
 The table below shows mapping of RavenDB 3.X OIDS to version 4.0.
 

Documentation/4.0/Raven.Documentation.Pages/server/administration/SNMP/snmp.markdown

@@ -17,11 +17,11 @@ As users start running large numbers of RavenDB instances, it becomes unpractica
 SNMP support is available for enterprise licenses only.
 {NOTE/}
 
-
 ### Enabling SNMP in RavenDB
 
 RavenDB is already configured to support SNMP. All you have to do is enable it and restart the server. 
 This is done by adding the following key to your settings.json file:
+
 {CODE-BLOCK:json}
 {
     ...
@@ -42,8 +42,7 @@ You can change those with the following configuration keys:
 }
 {CODE-BLOCK/}
 
-The community string is used like a password. It is sent with each SNMP Get request and 
-allows or denies access to the monitored device.
+The community string is used like a password. It is sent with each SNMP Get request and allows or denies access to the monitored device.
 
 ### The Metrics
 
@@ -146,7 +145,7 @@ RavenDB's root OID id: 1.3.6.1.4.1.45751.1.1.
 
 ### Templates
 
-For easier setup, we have prepared a few templates for monitoring tools which can be found [here](https://github.com/ravendb/ravendb/tree/v4.0/src/Raven.Server/Monitoring/Snmp/Templates).   
+For easier setup we have prepared a few templates for monitoring tools which can be found [here](https://github.com/ravendb/ravendb/tree/v4.0/src/Raven.Server/Monitoring/Snmp/Templates).   
 These templates include the metrics and their associated OIDs.
 
 ## Related Articles