Merge pull request #430 from stgelaisalex/master

Added a white bullet point

Author: JonathanMagnan

docs2/pages/documentations/query-db-set-filter.md

@@ -4,7 +4,7 @@
 
 The **Query DbSetFilter** is the old filter API for Entity Framework 6 (EF6) before the code switched to use Interceptor instead.
 
-The feature revamp was done in 2016 to support include and LazyLoading but have also some limitation such as performance and instance filter that the old code didn't have.
+The feature revamp was done in 2016 to support include and LazyLoading but, also have some limitation such as performance and instance filter that the old code didn't have.
 
 ## Limitations
 

docs2/pages/documentations/query-filter.md

@@ -56,7 +56,7 @@ var list = ctx.Posts.Filter(MyEnum.EnumValue).ToList();
 
 Global filter can be used by any context.
 
-Global filter is normally preferred in most scenario over instance filter since the filter code is centralized in one method over being spread in multiple methods.
+Global filter is normally preferred in most scenarios over instance filter since the filter code is centralized in one method over being spread in multiple methods.
 
 {% include template-example.html %} 
 ```csharp
@@ -252,7 +252,7 @@ var list = ctx.Invoices.Where(q => q.Where(x => x.CustomerID = myCustomerID)).To
 
 ### Object State
 
-Removing inactive or soft deleted records is probably the most common scenario. A soft delete is often useful when related data cannot be deleted. By example, the customer cannot be deleted because related orders cannot be deleted instead, he becomes inactive.
+Removing inactive or soft deleted records is probably the most common scenario. A soft delete is often useful when related data cannot be deleted. For example, the customer cannot be deleted because related orders cannot be deleted instead, he becomes inactive.
 
 *In this example, we display only active category.*
 
@@ -361,7 +361,7 @@ using (var ctx = new EntityContext())
 
 #### Context Filter
 
-Since the QueryCacheManager is global, our library have some limitations with Filter by context (Global Filter doesn't have this issue since it apply the same logic to all query.)
+Since the QueryCacheManager is global, our library have some limitations with Filter by context (Global Filter doesn't have this issue since it applies the same logic to all query.)
 
  - LazyLoading only work with GlobalFilter
  - context.Set only work with GlobalFilter (You can use the method SetFiltered instead)

docs2/pages/documentations/query-include-filter.md

@@ -138,15 +138,15 @@ var list = q1.Select(x => new { x, p1 }).ToList().Select(x => x.X);
 
 ```
 
-Entity Framework does already all the job to link related entities to the parent. No future logic is required.
+Entity Framework already does all the job by linking related entities to the parent. No future logic is required.
 
 ## Limitations
 
  - **DO NOT** work with **AsNoTracking**
  - Entity Framework Core:
    - Not supported yet.
  - Entity Framework 5:
- - Will never be supported. Use IncludeOptimized instead to filter collections
+   - Will never be supported. Use IncludeOptimized instead to filter collections
  - Cannot be mixed with projection
  - Cannot be mixed with Include (Include doesn't support projection)
  - Cannot be mixed with IncludeOptimized

docs2/pages/getting-started/overview.md

@@ -81,7 +81,7 @@ All future queries are stored in a pending list. When the first future query req
 
 ### Query IncludeFilter
 
-Entity Framework already support eager loading however the major drawback is you cannot control what will be included. There is no way to load only active item or load only the first 10 comments.
+Entity Framework already support eager loading. However, the major drawback is you cannot control what will be included. There is no way to load only active items or load only the first 10 comments.
 
 ### Query IncludeOptimized
 

docs2/pages/getting-started/tutorial-query.md

@@ -121,9 +121,9 @@ var customer = ctx.Customers.Filter(CustomEnum.EnumValue).ToList();
 
 ## Query Future
 
-Query Future allow to reduce database roundtrip by batching multiple queries in the same sql command.
+Query Future allow to reduce database roundtrips by batching multiple queries in the same sql command.
 
-All future query are stored in a pending list. When the first future query require a database roundtrip, all query are resolved in the same sql command instead of making a database roundtrip for every sql command.
+All future queries are stored in a pending list.  When the first future query require a database roundtrip, all queries are resolved in the same sql command instead of making a database roundtrip for every sql command.
 
 ### Support:
 
@@ -144,7 +144,7 @@ var countries = futureCountries.ToList();
 
 {% include template-example.html %} 
 ```csharp
-// GET the first active customer and the number of avtive customers
+// GET the first active customer and the number of active customers
 var futureFirstCustomer = db.Customers.Where(x => x.IsActive).DeferredFirstOrDefault().FutureValue();
 var futureCustomerCount = db.Customers.Where(x => x.IsActive).DeferredCount().FutureValue();
 
@@ -178,7 +178,7 @@ var posts = ctx.Post.IncludeFilter(x => x.Comments.Where(x => x.IsActive));
 
 ## Query IncludeOptimized
 
-Improve SQL generate by Include and filter child collections at the same times!
+Improve SQL generate by Include and filter child collections at the same time!
 
 {% include template-example.html %} 
 ```csharp
@@ -191,4 +191,4 @@ var posts = ctx.Post.IncludeOptimized(x => x.Comments.Where(x => x.IsActive));
 
 ***Support:** EF5, EF6*
 
-[Learn more](/query-include-optimized)
+[Learn more](/query-include-optimized)