Update index.mdx

Author: wedamija

develop-docs/api-server/application-domains/database-migrations/index.mdx

@@ -313,7 +313,7 @@ creating new columns they should either be:
 
 ### Adding Columns With a Default
 
-Since we run Postgres >= 14 in production we are able to add columns with a default. To do so, instead of using `default=<your_default>`, instead use `db_default=<your_default>`. This tells Django to set a default at the database level and manage it there, rather than managing it in code.
+Since we run Postgres >= 14 in production we are able to add columns with a default. To do so, instead of using `default=<your_default>`, use `db_default=<your_default>`. This tells Django to set a default at the database level and manage it there, rather than managing it in application code.
 
 We can't use `default` because Django's default behaviour for creating a new not null column with a default is dangerous. When using default, in the migration Django will add the default to backfill all fields, then immediately remove it so that it can handle them in the app layer. This means that during a deploy, the column is sitting in production without a default until all code rolls out, which means that inserts will fail for this table until the deploy completes.