diff --git a/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx b/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx
index b25b2e8d51..668d5d57ae 100644
--- a/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx
+++ b/apps/docs/content/docs/orm/prisma-migrate/workflows/prototyping-your-schema.mdx
@@ -11,7 +11,7 @@ The Prisma CLI has a dedicated command for prototyping schemas: [`db push`](/orm
 `db push` uses the same engine as Prisma Migrate to synchronize your Prisma schema with your database schema. The `db push` command:
 
 - Introspects the database to infer and executes the changes required to make your database schema reflect the state of your Prisma schema.
-- By default, after changes have been applied to the database schema, generators are triggered (for example, Prisma Client). You do not need to manually invoke `prisma generate`.
+- Does not automatically trigger generators (for example, Prisma Client). You need to manually invoke `prisma generate` after making schema changes.
 - If `db push` anticipates that the changes could result in data loss, it will:
    - Throw an error
    - Require the `--accept-data-loss` option if you still want to make the changes