Addressed review feedback

Author: Bart Koelman

README.md

@@ -87,13 +87,13 @@ public class Startup
 The following chart should help you pick the best version, based on your environment.
 See also our [versioning policy](./VERSIONING_POLICY.md).
 
-| .NET version | EF Core version | JsonApiDotNetCore version |
-| ------------ | --------------- | ------------------------- |
-| Core 2.x     | 2.x             | 3.x                       |
-| Core 3.1     | 3.1             | 4.x                       |
-| Core 3.1     | 5               | 4.x                       |
-| 5            | 5               | 4.x or 5.x                |
-| 6            | 6               | 5.x                       |
+| .NET version | Entity Framework Core version | JsonApiDotNetCore version |
+| ------------ | ----------------------------- | ------------------------- |
+| Core 2.x     | 2.x                           | 3.x                       |
+| Core 3.1     | 3.1                           | 4.x                       |
+| Core 3.1     | 5                             | 4.x                       |
+| 5            | 5                             | 4.x or 5.x                |
+| 6            | 6                             | 5.x                       |
 
 ## Contributing
 

docs/internals/queries.md

@@ -5,7 +5,7 @@ _since v4.0_
 The query pipeline roughly looks like this:
 
 ```
-HTTP --[ASP.NET]--> QueryString --[JADNC:QueryStringParameterReader]--> QueryExpression[] --[JADNC:ResourceService]--> QueryLayer --[JADNC:Repository]--> IQueryable --[EF Core]--> SQL
+HTTP --[ASP.NET]--> QueryString --[JADNC:QueryStringParameterReader]--> QueryExpression[] --[JADNC:ResourceService]--> QueryLayer --[JADNC:Repository]--> IQueryable --[Entity Framework Core]--> SQL
 ```
 
 Processing a request involves the following steps:
@@ -22,7 +22,7 @@ Processing a request involves the following steps:
 	- `JsonApiResourceService` contains no more usage of `IQueryable`.
 - `EntityFrameworkCoreRepository` delegates to `QueryableBuilder` to transform the `QueryLayer` tree into `IQueryable` expression trees.
 	`QueryBuilder` depends on `QueryClauseBuilder` implementations that visit the tree nodes, transforming them to `System.Linq.Expression` equivalents.
-	The `IQueryable` expression trees are executed by EF Core, which produces SQL statements out of them.
+	The `IQueryable` expression trees are executed by Entity Framework Core, which produces SQL statements out of them.
 - `JsonApiWriter` transforms resource objects into json response.
 
 # Example

docs/usage/extensibility/resource-definitions.md

@@ -223,7 +223,7 @@ _since v3_
 You can define additional query string parameters with the LINQ expression that should be used.
 If the key is present in a query string, the supplied LINQ expression will be added to the database query.
 
-Note this directly influences the Entity Framework Core `IQueryable`. As opposed to using `OnApplyFilter`, this enables the full range of EF Core operators. 
+Note this directly influences the Entity Framework Core `IQueryable`. As opposed to using `OnApplyFilter`, this enables the full range of Entity Framework Core operators. 
 But it only works on primary resource endpoints (for example: /articles, but not on /blogs/1/articles or /blogs?include=articles).
 
 ```c#

docs/usage/resources/nullability.md

@@ -20,15 +20,15 @@ public sealed class User : Identifiable<int>
 }
 ```
 
-This makes EF Core generate non-nullable columns. And model errors are returned when nullable fields are omitted.
+This makes Entity Framework Core generate non-nullable columns. And model errors are returned when nullable fields are omitted.
 
 # Reference types
 
 When the [nullable reference types](https://docs.microsoft.com/en-us/dotnet/csharp/nullable-references) (NRT) compiler feature is enabled, it affects both ASP.NET ModelState validation and Entity Framework Core.
 
 ## NRT turned off
 
-When NRT is turned off, use `[Required]` on required attributes and relationships. This makes EF Core generate non-nullable columns. And model errors are returned when required fields are omitted.
+When NRT is turned off, use `[Required]` on required attributes and relationships. This makes Entity Framework Core generate non-nullable columns. And model errors are returned when required fields are omitted.
 
 Example:
 
@@ -56,9 +56,9 @@ public sealed class Label : Identifiable<int>
 
 ## NRT turned on
 
-When NRT is turned on, use nullability annotations (?) on attributes and relationships. This makes EF Core generate non-nullable columns. And model errors are returned when non-nullable fields are omitted.
+When NRT is turned on, use nullability annotations (?) on attributes and relationships. This makes Entity Framework Core generate non-nullable columns. And model errors are returned when non-nullable fields are omitted.
 
-The [EF Core guidance on NRT](https://docs.microsoft.com/en-us/ef/core/miscellaneous/nullable-reference-types) recommends to use constructor binding to initialize non-nullable properties, but JsonApiDotNetCore does not support that. For required navigation properties, it suggests to use a non-nullable property with a nullable backing field. JsonApiDotNetCore does not support that either. In both cases, just use the null-forgiving operator (!).
+The [Entity Framework Core guide on NRT](https://docs.microsoft.com/en-us/ef/core/miscellaneous/nullable-reference-types) recommends to use constructor binding to initialize non-nullable properties, but JsonApiDotNetCore does not support that. For required navigation properties, it suggests to use a non-nullable property with a nullable backing field. JsonApiDotNetCore does not support that either. In both cases, just use the null-forgiving operator (!).
 
 When ModelState validation is turned on, to-many relationships must be assigned an empty collection. Otherwise an error is returned when they don't occur in the request body.
 

docs/usage/resources/relationships.md

@@ -53,7 +53,7 @@ public sealed class AppDbContext : DbContext
 }
 ```
 
-Which results in EF Core generating the next database objects:
+Which results in Entity Framework Core generating the next database objects:
 ```sql
 CREATE TABLE "Engine" (
     "Id" integer GENERATED BY DEFAULT AS IDENTITY,