Change setup to set up

entity-framework/core/change-tracking/identity-resolution.md

@@ -607,7 +607,7 @@ The fix for this is to either to set key values explicitly or configure the key
 
 <xref:Microsoft.EntityFrameworkCore.DbContext> is designed to represent a short-lived unit-of-work, as described in [DbContext Initialization and Configuration](xref:core/dbcontext-configuration/index), and elaborated on in [Change Tracking in EF Core](xref:core/change-tracking/index). Not following this guidance makes it is easy to run into situations where an attempt is made to track multiple instances of the same entity. Common examples are:
 
-- Using the same DbContext instance to both setup test state and then execute the test. This often results in the DbContext still tracking one entity instance from test setup, while then attempting to attach a new instance in the test proper. Instead, use a different DbContext instance for setting up test state and the test code proper.
+- Using the same DbContext instance to both set up test state and then execute the test. This often results in the DbContext still tracking one entity instance from test setup, while then attempting to attach a new instance in the test proper. Instead, use a different DbContext instance for setting up test state and the test code proper.
 - Using a shared DbContext instance in a repository or similar code. Instead, make sure your repository uses a single DbContext instance for each unit-of-work.
 
 ## Identity resolution and queries

entity-framework/core/modeling/keys.md

@@ -28,7 +28,7 @@ You can configure a single property to be the primary key of an entity as follow
 
 ***
 
-You can also configure multiple properties to be the key of an entity - this is known as a composite key. Composite keys can only be configured using the Fluent API; conventions will never setup a composite key, and you can not use Data Annotations to configure one.
+You can also configure multiple properties to be the key of an entity - this is known as a composite key. Composite keys can only be configured using the Fluent API; conventions will never set up a composite key, and you can not use Data Annotations to configure one.
 
 [!code-csharp[Main](../../../samples/core/Modeling/FluentAPI/KeyComposite.cs?name=KeyComposite&highlight=4)]
 

entity-framework/core/modeling/relationships.md

@@ -202,7 +202,7 @@ You don't necessarily need to provide a navigation property. You can simply prov
 
 ### Principal key
 
-If you want the foreign key to reference a property other than the primary key, you can use the Fluent API to configure the principal key property for the relationship. The property that you configure as the principal key will automatically be setup as an [alternate key](xref:core/modeling/keys#alternate-keys).
+If you want the foreign key to reference a property other than the primary key, you can use the Fluent API to configure the principal key property for the relationship. The property that you configure as the principal key will automatically be set up as an [alternate key](xref:core/modeling/keys#alternate-keys).
 
 #### [Simple key](#tab/simple-key)
 

entity-framework/core/providers/writing-a-provider.md

@@ -14,7 +14,7 @@ For information about writing an Entity Framework Core database provider, see [S
 > These posts have not been updated since EF Core 1.1 and there have been significant changes since that time.
 [Issue 681](https://github.com/dotnet/EntityFramework.Docs/issues/681) is tracking updates to this documentation.
 
-The EF Core codebase is open source and contains several database providers that can be used as a reference. You can find the source code at <https://github.com/dotnet/efcore>. It may also be helpful to look at the code for commonly used third-party providers, such as [Npgsql](https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL), [Pomelo MySQL](https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql), and [SQL Server Compact](https://github.com/ErikEJ/EntityFramework.SqlServerCompact). In particular, these projects are setup to extend from and run functional tests that we publish on NuGet. This kind of setup is strongly recommended.
+The EF Core codebase is open source and contains several database providers that can be used as a reference. You can find the source code at <https://github.com/dotnet/efcore>. It may also be helpful to look at the code for commonly used third-party providers, such as [Npgsql](https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL), [Pomelo MySQL](https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql), and [SQL Server Compact](https://github.com/ErikEJ/EntityFramework.SqlServerCompact). In particular, these projects are set up to extend from and run functional tests that we publish on NuGet. This kind of setup is strongly recommended.
 
 ## Keeping up-to-date with provider changes
 

entity-framework/core/testing/testing-sample.md

@@ -120,7 +120,7 @@ This is covered in more detail below.
 
 XUnit, like most testing frameworks, will create a new test class instance for each test run.
 Also, XUnit will not run tests within a given test class in parallel.
-This means that we can setup and configure the database in the test constructor and it will be in a well-known state for each test.
+This means that we can set up and configure the database in the test constructor and it will be in a well-known state for each test.
 
 > [!TIP]
 > This sample recreates the database for each test.