Updates

Author: guardrex

aspnetcore/blazor/blazor-ef-core.md

@@ -62,15 +62,15 @@ The sample app was built as a reference for server-side Blazor apps that use EF
 
 The sample uses a local [SQLite](https://www.sqlite.org/index.html) database so that it can be used on any platform.
 
-The sample demonstrates use of EF Core to handle optimistic concurrency. However, [native database-generated concurrency tokens](/ef/core/saving/concurrency?tabs=fluent-api#native-database-generated-concurrency-tokens) aren't supported for SQLite databases, which is the database provider for the sample app. To demonstrate concurrency with the sample app, adopt a different database provider that supports database-generated concurrency tokens (for example, the [SQL Server provider](/ef/core/providers/sql-server)).
+The sample demonstrates use of EF Core to handle optimistic concurrency. However, [native database-generated concurrency tokens](/ef/core/saving/concurrency?tabs=fluent-api#native-database-generated-concurrency-tokens) aren't supported for SQLite databases, which is the database provider for the sample app. To demonstrate concurrency with the sample app, adopt a different database provider that supports database-generated concurrency tokens (for example, the [SQL Server provider](/ef/core/providers/sql-server)). You can adopt SQL Server for the sample app by following the guidance in the next section, *Use the sample with SQL Server and optimistic concurrency*.
 
 ### Use the sample with SQL Server and optimistic concurrency
 
 The sample demonstrates use of EF Core to handle optimistic concurrency but only for a database provider that uses [native database-generated concurrency tokens](/ef/core/saving/concurrency?tabs=fluent-api#native-database-generated-concurrency-tokens), which is a feature supported for SQL Server. To demonstrate concurrency with the sample app, the sample app can be converted from the SQLite provider to use the [SQL Server provider](/ef/core/providers/sql-server) with a new SQL Server database created using .NET scaffolding.
 
 Use the following guidance to adopt SQL Server for the sample app using Visual Studio.
 
-Open the `Program` file (`Program.cs`) and comment out the lines that add the SQLite provider:
+Open the `Program` file (`Program.cs`) and comment out the lines that add the database context factory with the SQLite provider:
 
 ```diff
 - builder.Services.AddDbContextFactory<ContactContext>(opt =>
@@ -87,25 +87,25 @@ In the **Add New Scaffolded Item** dialog, select **Installed** > **Common** > *
 
 In the **Add Razor Components Using Entity Framework (CRUD)** dialog, use the following settings:
 
-* **Template**: Leave the selection on **CRUD**.
-* **Model class**: Select the `Contact` model.
+* **Template**: Use the default selection (**CRUD**).
+* **Model class**: Select the `Contact` model from the dropdown list.
 * **DbContext class**: Select the plus sign (`+`) and select **Add** using the default context class name generated by the scaffolder.
-* **Database provider**: Leave the default **SQL Server** value.
+* **Database provider**: Use the default selection (**SQL Server**).
 
 Select **Add** to scaffold the model and create the SQL Server database.
 
 When the scaffolding operation completes, delete the generated context class from the `Data` folder (`Data/{PROJECT NAME}Context.cs`, where the `{PROJECT NAME}` placeholder is the project's name/namespace).
 
 Delete the `ContactPages` folder from the `Components/Pages` folder, which contains [QuickGrid](xref:blazor/components/quickgrid)-based pages for contact management. For a complete demonstration of QuickGrid-based pages for managing data, use the <xref:blazor/tutorials/movie-database-app/index> tutorial.
 
-Open the `Program` file (`Program.cs`) and find the line that scaffolding added to create a database context factory using the SQL Server provider. Change the context from the generated context class (deleted earlier) to the existing `ContactContext` class:
+Open the `Program` file (`Program.cs`) and find the line that scaffolding added to create a database context factory using the SQL Server provider. Change the context from the generated context class (deleted earlier) to the app's existing `ContactContext` class:
 
 ```diff
 - builder.Services.AddDbContextFactory<BlazorWebAppEFCoreContext>(options =>
 + builder.Services.AddDbContextFactory<ContactContext>(options =>
 ```
 
-At this point, the app is using the SQL Server provider and a SQL Server database created for the `Contacts` model class. Optimistic concurrency works using [native database-generated concurrency tokens](/ef/core/saving/concurrency?tabs=fluent-api#native-database-generated-concurrency-tokens) that are already implemented in the sample app's code.
+At this point, the app is using the SQL Server provider and a SQL Server database created for the `Contact` model class. Optimistic concurrency works using [native database-generated concurrency tokens](/ef/core/saving/concurrency?tabs=fluent-api#native-database-generated-concurrency-tokens) that are already implemented in the sample app's `ContactContext` class.
 
 ### Database logging