Fix small typos (#3046)

Author: garyng

entity-framework/core/change-tracking/explicit-tracking.md

@@ -888,7 +888,7 @@ After SaveChanges completes, all the deleted entities are detached from the DbCo
 
 <xref:Microsoft.EntityFrameworkCore.ChangeTracking.ChangeTracker.TrackGraph%2A?displayProperty=nameWithType> works like `Add`, `Attach` and `Update` except that it generates a callback for every entity instance before tracking it. This allows custom logic to be used when determining how to track individual entities in a graph.
 
-For example, consider the rule EF Core uses when tracking entities with generated key values: if the kye value is zero, then the entity is new and should be inserted. Let's extend this rule to say if the key value is negative, then the entity should be deleted. This allows us to change the primary key values in entities of a disconnected graph to mark deleted entities:
+For example, consider the rule EF Core uses when tracking entities with generated key values: if the key value is zero, then the entity is new and should be inserted. Let's extend this rule to say if the key value is negative, then the entity should be deleted. This allows us to change the primary key values in entities of a disconnected graph to mark deleted entities:
 
 <!--
             blog.Posts.Add(

entity-framework/core/change-tracking/index.md

@@ -45,7 +45,7 @@ DbContext is designed to represent a short-lived unit-of-work, as described in [
 
 ## Entity states
 
-Every entity is is associated with a given <xref:Microsoft.EntityFrameworkCore.EntityState>:
+Every entity is associated with a given <xref:Microsoft.EntityFrameworkCore.EntityState>:
 
 - `Detached` entities are not being tracked by the <xref:Microsoft.EntityFrameworkCore.DbContext>.
 - `Added` entities are new and have not yet been inserted into the database. This means they will be inserted when <xref:Microsoft.EntityFrameworkCore.DbContext.SaveChanges%2A> is called.

entity-framework/core/change-tracking/relationship-changes.md

@@ -179,8 +179,7 @@ Relationship fixup also happens between entities returned from a tracking query
         var posts = context.Posts.ToList();
         Console.WriteLine(context.ChangeTracker.DebugView.LongView);
 -->
-[!code-csharp[Relationship_fixup_2](../../../ samples / core / ChangeTracking / ChangingFKsAndNavigations / OptionalRelationshipsSamples.cs ? name = Relationship_fixup_2
-) ]
+[!code-csharp[Relationship_fixup_2](../../../samples/core/ChangeTracking/ChangingFKsAndNavigations/OptionalRelationshipsSamples.cs?name=Relationship_fixup_2)]
 Looking again at the debug views, after the first query only the two blogs are tracked:
 
 ```output