Tweak wording on migrations warning

Closes #2641
dotnet · Sep 14, 2020 · 04d39cd · 04d39cd
1 parent c550261
commit 04d39cd
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/entity-framework/core/managing-schemas/migrations/applying.md b/entity-framework/core/managing-schemas/migrations/applying.md
@@ -187,5 +187,5 @@ Note that `Migrate()` builds on top of the `IMigrator` service, which can be use
 
 > [!WARNING]
 >
-> * Carefully consider before using this approach in production. Experience has shown that the simplicity of this deployment strategy is outweighed by the issues it creates. Consider using SQL scripts instead.
+> * Carefully consider before using this approach in production. Experience has shown that the simplicity of this deployment strategy is outweighed by the issues it creates. Consider generating SQL scripts from migrations instead.
 > * Don't call `EnsureCreated()` before `Migrate()`. `EnsureCreated()` bypasses Migrations to create the schema, which causes `Migrate()` to fail.