From ff3ef6dd8e71879e9a963fc72ef3a6fa0cf8563c Mon Sep 17 00:00:00 2001
From: Shay Rojansky <roji@roji.org>
Date: Sat, 26 Apr 2025 23:57:29 +0200
Subject: [PATCH] Typo

Fixes #5017
---
 entity-framework/core/change-tracking/entity-entries.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/entity-framework/core/change-tracking/entity-entries.md b/entity-framework/core/change-tracking/entity-entries.md
index 956a46cb0e..8dd8c89e25 100644
--- a/entity-framework/core/change-tracking/entity-entries.md
+++ b/entity-framework/core/change-tracking/entity-entries.md
@@ -481,7 +481,7 @@ Notice that, unlike <xref:Microsoft.EntityFrameworkCore.ChangeTracking.ChangeTra
 - `Added` entities are included. Note that this is not the case for normal EF Core queries, since `Added` entities do not yet exist in the database and so are therefore never returned by a database query.
 - `Deleted` entities are excluded. Note that this is again not the case for normal EF Core queries, since `Deleted` entities still exist in the database and so _are_ returned by database queries.
 
-All of this means that `DbSet.Local` is view over the data that reflects the current conceptual state of the entity graph, with `Added` entities included and `Deleted` entities excluded. This matches what database state is expected to be after SaveChanges is called.
+All of this means that `DbSet.Local` is a view over the data that reflects the current conceptual state of the entity graph, with `Added` entities included and `Deleted` entities excluded. This matches what database state is expected to be after SaveChanges is called.
 
 This is typically the ideal view for data binding, since it presents to the user the data as they understand it based on the changes made by the application.