fix(docs): replace non-existing migrate command

docs/pages/docs/guides/database-migration.md

@@ -24,7 +24,7 @@ Running `keystone dev --no-db-push` will return GraphQL runtime errors if tables
 ## Keystone Prisma Migrate CLI
 
 Keystone offers the following three commonly used commands through Prisma to help manage your migrations.
-- `keystone prisma migrate generate` - Generates the migration files to run to set up your production database - these files should be committed to source control and accessible by the `deploy` step. This command is helpful if you want to either leave `keystone dev` as the default behaviour for rapid schema iteration and generate the migrations once you are ready to submit a PR.
+- `keystone prisma migrate dev` - Generates the migration files to run to set up your production database - these files should be committed to source control and accessible by the `deploy` step. This command is helpful if you want to either leave `keystone dev` as the default behaviour for rapid schema iteration and generate the migrations once you are ready to submit a PR.
 - `keystone prisma migrate deploy` - Runs the generated migrations - this command can only be run after a `build` step, and is generally run in the deploy step of your app or before running `keystone start`.
 - `keystone start --with-migrations` - Runs the generated migrations then starts Keystone.
 ## Prisma CLI
@@ -47,4 +47,4 @@ heading="Command Line Guide"
 href="/docs/guides/cli" %}
 Learn how to use Keystone's command line interface (CLI) to develop, build, and deploy your Keystone projects.
 {% /well %}
-{% /related-content %}
+{% /related-content %}