docs: improve clarity and consistency across multiple guide documents

Author: alirezanet

docs/pages/example/api-controller.md

@@ -1,8 +1,8 @@
 # Using Gridify in API Controllers
 
-When working with ASP.NET APIs, especially when you need to apply string-based filtering conditions, sorting based on field names, or implementing pagination functionality, the Gridify library is a valuable tool. It can be used in any .NET project and with any type of collection, not just limited to ASP.NET projects.
+When working with ASP.NET APIs, especially when you need to apply string-based filtering, sorting by field names, or implementing pagination, the Gridify library is a valuable tool. It can be used in any .NET project and with any type of collection, not just limited to ASP.NET projects.
 
-To demonstrate the core concepts of Gridify, let's look at a simple implementation in the following example.
+Let's look at a simple implementation to demonstrate the core concepts of Gridify.
 
 ## Describing the Scenario
 

docs/pages/guide/autoMapper.md

@@ -14,11 +14,11 @@ QueryablePaging<Person> qp = personRepo.GridifyQueryable(gridifyQuery);
 var result = new Paging<Person>(qp.Count, qp.Query.ProjectTo<PersonDTO>().ToList());
 ```
 
-## GridifyTo!
+## GridifyTo Extension
 
-Filtering, Ordering, Paging, and Projection are all done with `GridifyTo`.
+Filtering, ordering, paging, and projection are all done with a `GridifyTo` extension method.
 
-Gridify library does not have a built-in `GridifyTo` extension method because we don't want to have AutoMapper dependency. but if you are using AutoMapper in your project, I recommend you to add the bellow extension method to your project.
+The Gridify library does not include a built-in `GridifyTo` extension method because we don't want to add an AutoMapper dependency. However, if you are using AutoMapper in your project, we recommend adding the following extension method:
 
 ``` csharp
 public static Paging<TDestination> GridifyTo<TSource, TDestination>(

docs/pages/guide/compile.md

@@ -1,13 +1,13 @@
 # Compile and Reuse
 
-You can access Gridify generated expressions using the `GetFilteringExpression` of [GridifyQuery](./gridifyQuery.md)
-or `BuildCompiled` methods of [QueryBuilder](./queryBuilder.md) class,
-by storing an expression you can use it multiple times without having any overheads,
-also if you store a compiled expression you get a massive performance boost.
+You can access Gridify-generated expressions using the `GetFilteringExpression` method of [GridifyQuery](./gridifyQuery.md)
+or the `BuildCompiled` method of the [QueryBuilder](./queryBuilder.md) class.
+By storing an expression, you can reuse it multiple times without any overhead.
+If you store a compiled expression, you get a massive performance boost.
 
 ::: warning
-You should only use a **compiled** expression (delegate) if you are **not** using Gridify alongside an ORM like
-Entity-Framework.
+You should only use a **compiled** expression (delegate) if you are **not** using Gridify with an ORM like
+Entity Framework.
 :::
 
 ``` csharp

docs/pages/guide/dependency-injection.md

@@ -1,10 +1,10 @@
 # Dependency Injection
 
-Gridify offers a powerful feature that enables you to streamline data mapping and configurations in your application by integrating with the Dependency Injection (DI) container. By registering your mapping profiles with DI, you can achieve cleaner, more maintainable code and improved separation of concerns. This section provides an overview of how to register your GridifyMapper configurations with DI.
+Gridify offers a powerful feature that enables you to streamline data mapping and configuration in your application by integrating with the Dependency Injection (DI) container. By registering your mapping profiles with DI, you can achieve cleaner, more maintainable code and improved separation of concerns. This section provides an overview of how to register your GridifyMapper configurations in the DI container.
 
 ## Register GridifyMapper with DI
 
-Registering Gridify mapping with DI is a straightforward process. You'll define mapping profiles for your models and then register them in the DI container. Follow these steps to get started:
+Registering Gridify mappings with DI is straightforward. Define mapping profiles for your models, then register them in the DI container. Follow these steps to get started:
 
 ## 1. Define Mapping Profiles
 

docs/pages/guide/extensions.md

@@ -1,41 +1,41 @@
 # Extensions
 
-The Gridify library adds the below extension methods to `IQueryable` objects.
+The Gridify library adds the following extension methods to `IQueryable` objects.
 
-All Gridify extension methods can accept [GridifyQuery](./gridifyQuery.md) and [GridifyMapper](./gridifyMapper.md) as a parameter.
-Make sure to check out the documentation of these classes for more information.
+All Gridify extension methods can accept [GridifyQuery](./gridifyQuery.md) and [GridifyMapper](./gridifyMapper.md) as parameters.
+Make sure to check out the documentation for these classes for more information.
 
 ::: tip
-If you want to use Gridify extension methods on an `IEnumerable` object, use `.AsQueryable()` first.
+To use Gridify extension methods on an `IEnumerable` object, first call `.AsQueryable()` on it.
 :::
 
 ## ApplyFiltering
 
-You can use this method if you want to only apply **filtering** on an `IQueriable` or `DbSet`.
+Use this method to apply **filtering** to an `IQueryable` or `DbSet`.
 
 ``` csharp
 var query = personsRepo.ApplyFiltering("name = John");
 ```
 
-this is completely equivalent to the below LINQ query:
+This is equivalent to the following LINQ query:
 
 ``` csharp
 var query = personsRepo.Where(p => p.Name == "John");
 ```
 
-In the `ApplyFiltering` method, we can use a raw string to filter the data, which can be generated dynamically or passed by the end-user for example through an API client or console input, but using the Linq `Where` method, we always have to hard code the query for the supported fields.
+With the `ApplyFiltering` method, you can use a raw string to filter data. This string can be generated dynamically or passed by the end-user (for example, through an API client or console input). In contrast, when using the LINQ `Where` method, you must hard-code the query for the supported fields.
 
 Check out the [Filtering Operators](./filtering.md) section for more information.
 
 ## ApplyOrdering
 
-You can use this method if you want to only apply **ordering** on an `IQueriable` collection or `DbSet`.
+Use this method to apply **ordering** to an `IQueryable` collection or `DbSet`.
 
 ``` csharp
 var query = personsRepo.ApplyOrdering("name, age desc");
 ```
 
-this is completely equivalent to the below LINQ query:
+This is equivalent to the following LINQ query:
 
 ``` csharp
 var query = personsRepo.OrderBy(x => x.Name).ThenByDescending(x => x.Age);
@@ -45,35 +45,35 @@ Check out the [Ordering](./ordering.md) section for more information.
 
 ## ApplyPaging
 
-You can use this method if you want to only apply **paging** on an `IQueryable` collection or `DbSet`.
+Use this method to apply **paging** to an `IQueryable` collection or `DbSet`.
 
 ``` csharp
 var query = personsRepo.ApplyPaging(3, 20);
 ```
 
-this is completely equivalent to the below LINQ query:
+This is equivalent to the following LINQ query:
 
 ``` csharp
 var query = personsRepo.Skip((3-1) * 20).Take(20);
 ```
 
 ## ApplyFilteringAndOrdering
 
-You can use this method if you want to apply **filtering** and **ordering** on an `IQueryable` collection or `DbSet`. This method accepts `IGridifyQuery`.
+Use this method to apply **filtering** and **ordering** to an `IQueryable` collection or `DbSet`. This method accepts `IGridifyQuery`.
 
 ## ApplyOrderingAndPaging
 
-You can use this method if you want to apply **ordering** and **paging** on an `IQueryable` collection or `DbSet`. This method accepts `IGridifyQuery`.
+Use this method to apply **ordering** and **paging** to an `IQueryable` collection or `DbSet`. This method accepts `IGridifyQuery`.
 
 ## ApplyFilteringOrderingPaging
 
-You can use this method if you want to apply  **filtering** and **ordering** and **paging** on an `IQueryable` collection or `DbSet`. This method accepts `IGridifyQuery`.
+Use this method to apply **filtering**, **ordering**, and **paging** to an `IQueryable` collection or `DbSet`. This method accepts `IGridifyQuery`.
 
 ## GridifyQueryable
 
-Like [ApplyFilteringOrderingPaging](#ApplyFilteringOrderingPaging) but it returns a `QueryablePaging<T>` that has an extra `int Count` value that can be used for pagination.
+Like [ApplyFilteringOrderingPaging](#applyfilteringorderingpaging), but it returns a `QueryablePaging<T>` that includes an extra `int Count` value for pagination.
 
 ## Gridify
 
-This is an ALL-IN-ONE package, it accepts `IGridifyQuery`, applies filtering, ordering, and paging, and returns a `Paging<T>` object.
-This method is completely optimized to be used with any **Grid** component.
+This is an all-in-one method. It accepts `IGridifyQuery`, applies filtering, ordering, and paging, and returns a `Paging<T>` object.
+This method is optimized for use with any grid component.

docs/pages/guide/extensions/elasticsearch.md

@@ -1,10 +1,10 @@
 # Elasticsearch
 
-Gridify.Elasticsearch is an extension of Gridify, that provides an ability to generate Elasticsearch DSL queries.
+Gridify.Elasticsearch is an extension of Gridify that provides the ability to generate Elasticsearch DSL queries.
 
 ## Gridify.Elasticsearch Package
 
-The `Gridify.Elasticsearch` package has a bunch of extension methods that allow to convert Gridify filters and sortings to Elasticsearch DSL queries using Elastic.Clients.Elasticsearch .NET client.
+The `Gridify.Elasticsearch` package includes extension methods that convert Gridify filters and sortings to Elasticsearch DSL queries using the Elastic.Clients.Elasticsearch .NET client.
 
 ## Installation
 

docs/pages/guide/extensions/entityframework.md

@@ -2,7 +2,7 @@
 
 ## Gridify.EntityFramework Package
 
-The `Gridify.EntityFramework` package has two additional `GridifyAsync()` and `GridifyQueryableAsync()` methods.
+The `Gridify.EntityFramework` package includes two additional methods: `GridifyAsync()` and `GridifyQueryableAsync()`.
 
 ## Installation
 
@@ -18,19 +18,19 @@ Install-Package Gridify.EntityFramework -Version {{ $version }}
 dotnet add package Gridify.EntityFramework --version {{ $version }}
 ```
 
-## Compatibility layer
+## Compatibility Layer
 
-If you want to use gridify with Entity Framework, you should enable the compatibility layer:
+To use Gridify with Entity Framework, enable the compatibility layer:
 
 ``` csharp
 GridifyGlobalConfiguration.EnableEntityFrameworkCompatibilityLayer();
 ```
 
 Enabling the compatibility layer provides the following features:
 
-- It tweaks the internal expression builder to make it compatible with Entity Framework.
+- Tweaks the internal expression builder for Entity Framework compatibility
 - EF query optimization
-- EF ServiceProviderCaching support
+- EF ServiceProvider caching support
 - Creates parameterized queries
 
 ``` sql

docs/pages/guide/extensions/gridify-client.md

@@ -1,8 +1,6 @@
 # Gridify Client Library
 
-The Gridify Client library is a lightweight JavaScript and TypeScript library designed to simplify the creation of
-dynamic queries on the client side. This library facilitates the construction of queries that can be seamlessly
-integrated with your server-side APIs, leveraging the powerful features of Gridify.
+The Gridify Client library is a lightweight JavaScript and TypeScript library designed to simplify creating dynamic queries on the client side. This library facilitates building queries that can be seamlessly integrated with your server-side APIs, leveraging the powerful features of Gridify.
 
 ## Installation
 

docs/pages/guide/filtering.md

@@ -63,9 +63,7 @@ this query matches with JOHN - john - John - jOHn ...
 
 ## Escaping
 
-Gridify have five special operators  `, | ( ) /i` to handle complex queries and case-insensitive searches. If you want
-to use these characters in your query values (after conditional operator), you should add a backslash <code>\ </code>
-before them. having this regex could be helpful `([(),|]|\/i)`.
+Gridify has five special operators: `, | ( ) /i` that are used to handle complex queries and case-insensitive searches. If you want to use these characters as literal values in your queries (after the conditional operator), you need to escape them by adding a backslash `\` before each one. This regex pattern can help identify characters that need escaping: `([(),|]|\/i)`.
 
 JavaScript escape example:
 
@@ -113,15 +111,12 @@ Check out [Defining Mappings for Indexable Properties](./gridifyMapper.md#defini
 
 ## Custom Operators
 
-Sometimes the default Gridify operators are not enough, For example, if you need an operator for regex matching or when
-you are using the EntityFramework, you may want to use `EF.Functions.FreeText` rather than a LIKE with wildcards. In
-this case, you can define your own operators. (added in `v2.6.0`)
+Sometimes the default Gridify operators are not enough. For example, if you need an operator for regex matching, or when using Entity Framework and you want to use `EF.Functions.FreeText` instead of a LIKE with wildcards. In these cases, you can define your own custom operators (added in `v2.6.0`).
 
-To define a custom operator, you need to create a class that implements the `IGridifyOperator` interface. then you need
-to register it through the global [CustomOperators](./gridifyGlobalConfiguration.md#customoperators) configuration.
+To define a custom operator, create a class that implements the `IGridifyOperator` interface, then register it through the global [CustomOperators](./gridifyGlobalConfiguration.md#customoperators) configuration.
 
 ::: tip
-Custom operators must be start with the `#` character.
+Custom operators must start with the `#` character.
 :::
 
 - FreeTextOperator Example:

docs/pages/guide/getting-started.md

@@ -1,23 +1,20 @@
 
 # Getting Started
 
-There are three packages available for gridify in the nuget repository:
+There are three main packages available for Gridify on NuGet:
 
 - [Gridify](https://www.nuget.org/packages/Gridify/)
 - [Gridify.EntityFramework](https://www.nuget.org/packages/Gridify.EntityFramework/)
+- [Gridify.Elasticsearch](https://www.nuget.org/packages/Gridify.Elasticsearch/)
 
 ::: tip
-If you are using the Entity Framework in your project, you should install the `Gridify.EntityFramework` package instead of `Gridify`.
+If you are using Entity Framework in your project, install the `Gridify.EntityFramework` package instead of `Gridify`.
 
-This package provides the same functionality as the `Gridify` package but is designed to be more compatible with [Entity Framework](./extensions/entityframework).
+This package provides the same functionality as the `Gridify` package but is optimized for [Entity Framework](./extensions/entityframework) compatibility.
 :::
 
----
-
-- [Gridify.Elasticsearch](https://www.nuget.org/packages/Gridify.Elasticsearch/)
-
 ::: tip
-To use Gridify with Elasticsearch, it's necessary to install [`Gridify.Elasticsearch`](./extensions/elasticsearch).
+To use Gridify with Elasticsearch, install the [`Gridify.Elasticsearch`](./extensions/elasticsearch) package.
 :::
 
 ---