continue updating tutorial

prisma · Sep 3, 2019 · 321a054 · 321a054
1 parent 356cbca
commit 321a054
Show file tree

Hide file tree

Showing 2 changed files with 319 additions and 195 deletions.
diff --git a/docs/development-mode.md b/docs/development-mode.md
@@ -34,7 +34,7 @@ This is **not** how migrations are performed in development mode! When running i
 
 1. **Adjust data model**: Change your [data model definition](./data-modeling.md#data-model-definition) to match your desired database schema. Then **save** the schema file.
 
-Because the development server is watching your schema file (which includes the data model definition) in the background, it notices that you've performed a change and updates your database schema for you. There are **no migration files** created for this schema update! However, it does update Lift's `_Migrations` table in your database schema.
+Because the development server is watching your schema file (which includes the data model definition) in the background, it notices that you've performed a change and updates your database schema for you. There migration files created for this schema update are stored in the `migrations/dev` directory! However, it does update Lift's `_Migrations` table in your database schema.
 
 The development mode lets you make quick changes to your data model as you develop your application without the need to persist these changes in a migration. Only once you're happy with your data model, you can [stop the development mode](#stopping-development-mode) and persist your migration using: