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

Co-authored-by: Mark Story <[email protected]>

Author: wedamija

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

@@ -152,7 +152,7 @@ To avoid this, follow these steps:
     - Remove the column and in the generated migration use `SafeRemoveField(..., deletion_action=DeletionAction.MOVE_TO_PENDING)` to replace `RemoveField(...)`. This only marks the state for the column as removed.
     - Combine these migrations together to save making multiple deploys
 - Deploy your migration changes. It's important that all previous pull requests are in production before we remove the actual column from the table.
-- Make a PR that create a new migration that has the same `SafeRemoveField` operation as before, but set `deletion_action=DeletionAction.DELETE` instead. This deletes the actual column from the table in Postgres.
+- Make a pull request that create a new migration that has the same `SafeRemoveField` operation as before, but set `deletion_action=DeletionAction.DELETE` instead. This deletes the actual column from the table in Postgres.
 - Deploy
 
 Here's an example of removing the `project` column from this model. It is both a foreign key and not null: