Update POST.md

docs/en/Community-Articles/2022-18-11-whats-new-with-net7/POST.md

@@ -1,10 +1,10 @@
 # What's new with .NET 7?
 
-In this article, I will highligt a few interesting features that are now available with the release of C# 11 and .NET 7.
+In this article, I will highlight a few interesting features that are now available with the release of C# 11 and .NET 7.
 
-> If you are considering to use ABP 7.0, you should update your projects to .NET 7. There is a good community article you might want to check 👉 "[Upgrade Your Existing Projects to .NET7](https://community.abp.io/posts/upgrade-your-existing-projects-to-.net7-nmx6vm9m)".
+> If you are considering using ABP 7.0, you should update your projects to .NET 7. There is a good community article you might want to check out 👉 "[Upgrade Your Existing Projects to .NET7](https://community.abp.io/posts/upgrade-your-existing-projects-to-.net7-nmx6vm9m)".
 
-There are many new features came with this release. We are going to examine new features within 4 sub-section: ASP.NET Core, C#11, EF 7 and MAUI. Let's start with ASP.NET Core.
+There are many new features coming with this release. We are going to examine new features within 4 sub-section: ASP.NET Core, C#11, EF 7 and MAUI. Let's start with ASP.NET Core.
 
 ## ASP.NET Core
 
@@ -20,11 +20,11 @@ We will see the following features in this section:
 
 ### Rate Limiting
 
-Rate limiting is a way to limit request frequency for a limit of time. Before, .NET 7 we weren’t have built-in support so we would needed to implement it ourselves or use some NuGet packages around or let the CDN provider do this on server level behalf of us (like Cloudflare).
+Rate limiting is a way to limit request frequency for a limited time. Before, .NET 7 we didn’t have built-in support so we would needed to implement it ourselves or use some NuGet packages around or let the CDN provider do this on server level behalf of us (like Cloudflare).
 
-With .NET 7, built-in Rate Limiting support have been added and we can easily define rate-limiting policies and attach them with our endpoints.
+With .NET 7, built-in Rate Limiting support has been added and we can easily define rate-limiting policies and attach them to our endpoints.
 
-*Defining rate-limiting policy and registring the required services to DI container*:
+*Defining rate-limiting policy and registering the required services to DI container*:
 
 ![](rate-limiting-1.png)
 
@@ -34,12 +34,12 @@ With .NET 7, built-in Rate Limiting support have been added and we can easily de
 
 ### Output Caching
 
-Output Caching is a new middleware that provides a caching mechanism and allow to store results from your web application and serve them from a cache rather than computing everytime. This improves performance and frees up resources for other tasks.
+Output Caching is a new middleware that provides a caching mechanism and allows you to store results from your web application and serve them from a cache rather than computing them every time. This improves performance and frees up resources for other tasks.
 
 It’s pretty straightforward to use output caching in minimal APIs. 
-You just need to create an endpoint and use the `CacheOutput` method with an expire time. Then when someone sends a request to your endpoint, it will be cached for specified time and not calculate the result every time.
+You just need to create an endpoint and use the `CacheOutput` method with an expiration time. Then when someone sends a request to your endpoint, it will be cached for a specified time and not calculate the result every time.
 
-For the following example, result will be same for 10 minutes:
+For the following example, the result will be same for 10 minutes:
 
 ```csharp
 app.MapGet("/cached-output", () => $"Minute: {DateTime.Now.Minute}")
@@ -51,9 +51,9 @@ app.MapGet("/cached-output", () => $"Minute: {DateTime.Now.Minute}")
 
 ### Built-in HTTP/3 Support
 
-In .NET 6, HTTP/3 was introduced for an experimental purposes and with .NET 7 now it’s fully supported. But it's not enabled by default, it's understandable since it's still new and only %20 of the applications currently uses it, on the other hand HTTP/2 uses by almost every application.
+In .NET 6, HTTP/3 was introduced for experimental purposes and with .NET 7 now it’s fully supported. But it's not enabled by default, it's understandable since it's still new and only %20 of the applications currently use it, on the other hand, HTTP/2 uses by almost every application.
 
-To enable the HTTP/3 support, we need to configure it our **Program.cs** file:
+To enable the HTTP/3 support, we need to configure it in our **Program.cs** file:
 
 ```csharp
 var builder = WebApplication.CreateBuilder(args);
@@ -76,7 +76,7 @@ gRPC - JSON Transcoding is an extension for ASP.NET Core that creates RESTful JS
 
 ![](json-transcoding.png)
 
-It's really good feature and allow us to expose our gRPC services as REST APIs. It's worth checking out 👉 [JSON Transcoding](https://learn.microsoft.com/en-us/aspnet/core/grpc/json-transcoding?view=aspnetcore-7.0).
+It's a really good feature and allows us to expose our gRPC services as REST APIs. It's worth checking out 👉 [JSON Transcoding](https://learn.microsoft.com/en-us/aspnet/core/grpc/json-transcoding?view=aspnetcore-7.0).
 
 ### Blazor
 
@@ -124,17 +124,17 @@ There are great features that came with C# 11. In this article, we are going to
 
 ### Required Members
 
-C# 11 introduces a new **required** keyword to allows us to ensure property initialization while object creation. 
+C# 11 introduces a new **required** keyword to allow us to ensure property initialization while object creation. 
 
-We just need to use the **required** keyword before the property type. That’s it. Then if we try to create an object without initializing the required properties, compile-time errors will shown. 
+We just need to use the **required** keyword before the property type. That’s it. Then if we try to create an object without initializing the required properties, compile-time errors will be shown:
 
 ![](required-members.png)
 
 ### Generic Attributes
 
-Generic Attributes is also one of the good features that came with C# 11. Before C#11, creating a typed attribute was cumbersome. We would need to pass **Type** object as argument to our constructor and assign it to a property in our attribute class and do stuff with this **Type** property.
+Generic Attributes are also one of the good features that came with C# 11. Before C#11, creating a typed attribute was cumbersome. We would need to pass a **Type** object as an argument to our constructor and assign it to a property in our attribute class and do stuff with this **Type** property.
 
-With C#11, Generic Attributes is introduced. Now, it’s possible to easily create generic attributes like creating generic classes:
+With C#11, Generic Attributes are introduced. Now, it’s possible to easily create generic attributes like creating generic classes:
 
 ```csharp
 //defining a generic attribute
@@ -147,7 +147,7 @@ public int MyMethod() => default;
 
 ### Raw String Literals
 
-Raw String Literals is a great syntactic-sugar that came with C#11. It allows containing of arbitrary text without escaping. 
+Raw String Literals is a great syntactic sugar that came with C#11. It allows containing of arbitrary text without escaping. 
 
 By wrapping a string with three double quotes (”””...”””), we are free to put any string value into variables:
 
@@ -160,29 +160,29 @@ var jsonContent = """
 """;
 ```
 
-Also, we can use string interpolation with this new syntax. We just need to add $ sign before the first triple quotes.
+Also, we can use string interpolation with this new syntax. We just need to add a $ sign before the first triple quotes:
 
 ![](raw-string-literals.png)
 
 ### List Patterns
 
-C# 11 introduces the “List Pattern”. It expands the pattern matching for list and arrays. There are three different ways for list pattern matching:
+C# 11 introduces the “List Pattern”. It expands the pattern matching for lists and arrays. There are three different ways for list pattern matching:
 
 #### 1-) Discard Pattern
 
-This pattern can be helpful to match one or more elements from a sequence, if we know the length of the sequence.
+This pattern can be helpful to match one or more elements from a sequence if we know the length of the sequence.
 
 ![](discard-pattern.png)
 
 #### 2-) Range Pattern
 
-If the length of the sequence is not know, then range pattern may be useful. We can use this pattern to check the first or/and last element from a sequence.
+If the length of the sequence is not known, then the range pattern may be useful. We can use this pattern to check the first or/and last element from a sequence.
 
 ![](range-pattern.png)
 
 #### 3-) var Pattern
 
-This pattern allows us to capture a element at that position and use the variable in our code.
+This pattern allows us to capture an element at that position and use the variable in our code.
 
 ![](var-pattern.png)
 
@@ -196,7 +196,9 @@ There are too many improvements and new features that shipped with EF Core 7. He
 
 ### JSON Columns
 
-EF 7 supports JSON Columns and this allows mapping of aggregates built from .NET types to JSON documents. Thus, it's kind a combine relational database and document-based databases in a way.
+EF 7 supports JSON Columns and this allows mapping of aggregates built from .NET types to JSON documents. 
+
+Thus, it's kind of combines relational database and document-based databases in a way.
 
 We can easily mark a column as JSON column on the `OnModelCreating` method of our `DbContext` class:
 
@@ -213,7 +215,7 @@ protected override void OnModelCreating(ModelBuilder modelBuilder)
 }
 ```
 
-Also with this version, LINQ JSON query support have been announced. So, we can query over JSON Columns using LINQ like below:
+Also with this version, LINQ JSON query support has been announced. So, we can query over JSON Columns using LINQ like below:
 
 ```csharp
 var posts = await context.Posts
@@ -231,7 +233,7 @@ var posts = await context.Posts
 
 ### Improvements on Bulk Updates & Deletes
 
-EF 7 introduces the new **ExecuteUpdateAsync** and **ExecuteDeleteAsync** methods. By using these methods while making bulk updates or deletes, we can not involving the change tracker into this process and this brings great performance gains. 
+EF 7 introduces the new **ExecuteUpdateAsync** and **ExecuteDeleteAsync** methods. By using these methods while making bulk updates or deletes, we can take out the change tracker in this process and this brings great performance gains. 
 
 Example:
 
@@ -243,31 +245,31 @@ await (await GetDbContextAsync()).Tags
 
 ### Performance Improvements on SaveChanges & SaveChangesAsync
 
-With EF 7, there are significant performance improvements on SaveChanges & SaveChangesAsync methods. According to the EF Core team, in some cases saving changes are now four times faster that EF 6. You can see a simple benchmark result from the EF Core blog post in here. 
+With EF 7, there are significant performance improvements on SaveChanges & SaveChangesAsync methods. According to the EF Core team, in some cases, saving changes are now four times faster than EF 6. You can see a simple benchmark result from the EF Core blog post here. 
 
 ![](benchmark.png)
 
-Even inserting just four records there is a great performance gain.
+Even after inserting just four records, there is a significant performance gain.
 
 ## .NET MAUI 7
 
 As you know, .NET MAUI is a cross-platform framework for creating native mobile and desktop applications by using C# and XAML. By using the .NET MAUI, apps can be developed that can run on Android, IOS, macOS and Windows from a single-code base.
 
-It’s a new technology, so it's evolving and .NET MAUI team introduces good features with every release.
+It’s a new technology, so it's evolving and the .NET MAUI team introduces good features with every release.
 
-In this article, I will only mention about a new feature called "Map Control" and some enhancements made with this release.
+In this article, I will only mention a new feature called "Map Control" and some enhancements made with this release.
 
 ### Map Control
 
-.NET MAUI 7 introduces the Map Control. This provides us a good native map experience.
+.NET MAUI 7 introduces **Map Control**. This provides us a good native map experience.
 
-It supports pins, poligons, circles, geolocations and much more...
+It supports pins, polygons, circles, geolocations and much more...
 
 ![](maui.png)
 
 ### Improvements on Mobile Rendering & Desktop Enhancements
 
-.NET MAUI 7 came with optimized rendering for mobile application and much faster than .NET MAUI 6.
+.NET MAUI 7 came with an optimized rendering for mobile applications and is much faster than .NET MAUI 6.
 
 Also, there are some good enhancements on the desktop side:
 
@@ -282,7 +284,7 @@ Also, there are some good enhancements on the desktop side:
 
 In this article, I've highlighted some features that shipped with .NET 7.
 
-> I'm adding references section down below, so you can check the references and see other features came with this version.
+> I've added a references section down below, so you can check the references and see other features came with this version.
 
 Thanks for reading the article and I hope you find it helpful. See you in the next one!