From a19f35a4af26cff1034307d071c886aab06c34b7 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Thu, 12 Dec 2024 05:45:20 -0500 Subject: [PATCH] Clarify the goal of EF Core code-first (#34347) --- aspnetcore/blazor/tutorials/movie-database-app/part-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md index 38cffb270f..c5f4fecd88 100644 --- a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md +++ b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md @@ -319,7 +319,7 @@ EF Core adopts the *code-first* approach for database design and maintenance: * Entity classes are created and updated first in the app. * The database is created and updated from the app's entity classes. -This is the reverse procedure of *database-first* approaches, where the database is designed, built, and updated first. Adopting EF Core's code-first approach speeds up the process of app development because most of the difficult and time-consuming database creation and management procedures are handled transparently by the EF Core tooling, so you can focus on app development. +This is the reverse procedure of *database-first* approaches, where the database is designed, built, and updated first. Adopting EF Core's code-first approach aims to speed up the process of app development because most of the difficult and time-consuming database creation and management procedures are handled transparently by the EF Core tooling, so you can focus on app development. :::zone pivot="vs"