From 78a5537c36dc5b99a0d89ccfa9a36147fd1e4d93 Mon Sep 17 00:00:00 2001 From: Aileen Rae <38075097+aileen-r@users.noreply.github.com> Date: Tue, 21 Dec 2021 15:13:26 +0000 Subject: [PATCH] Fix minor typo: code-first/migrations/team.md Changing "thru" -> "through" in "Code First Migrations in Team Environments". --- entity-framework/ef6/modeling/code-first/migrations/teams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/entity-framework/ef6/modeling/code-first/migrations/teams.md b/entity-framework/ef6/modeling/code-first/migrations/teams.md index 679aafcb3b..767d6d5636 100644 --- a/entity-framework/ef6/modeling/code-first/migrations/teams.md +++ b/entity-framework/ef6/modeling/code-first/migrations/teams.md @@ -89,7 +89,7 @@ Issues start to arise when you have multiple developers making changes to the EF First let’s look at a concrete example of such a merge conflict. We’ll continue on with the example we looked at earlier. As a starting point let’s assume the changes from the previous section were checked in by the original developer. We’ll track two developers as they make changes to code base. -We’ll track the EF model and the migrations thru a number of changes. For a starting point, both developers have synced to the source control repository, as depicted in the following graphic. +We’ll track the EF model and the migrations through a number of changes. For a starting point, both developers have synced to the source control repository, as depicted in the following graphic. ![Starting Point](~/ef6/media/startingpoint.png)