Removed suggestion to grant personal user privs in migration.

Reworded to emphasise use of migration scripts.

Author: mortenlj

docs/persistence/postgres/explanations/grants-and-privileges.md

@@ -9,9 +9,8 @@ By default, the user is granted `SELECT` privileges on all tables and sequences
 
 With the `--all-privs` flag, the user is granted `ALL` privileges on all tables and sequences in the default schema.
 In addition, the user is granted `CREATE` on the default schema.
+This should be enough to allow most maintenance tasks, but if you need more privileges, you can usually grant yourself the necessary privileges.
 
-This should be enough to allow most maintenance tasks, but if you need more privileges, you can usually grant yourself the needed privileges.
-If you find there are still some things you are unable to do, a common workaround is to make the changes via database-migration scripts (such as [Flyway](https://flywaydb.org/), [Liquibase](https://www.liquibase.org/), or [Alembic](https://alembic.sqlalchemy.org/)) that run as part of the application startup.
-Since these scripts are run by the application user, such scripts can also be used to grant additional privileges to personal users if needed.
+However, making changes to the database is best done through the application or through database migration scripts (such as [Flyway](https://flywaydb.org/), [Liquibase](https://www.liquibase.org/), or [Alembic](https://alembic.sqlalchemy.org/)) that run as part of the application startup.
 
 Read more about PostgreSQL privileges in the official [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-grant.html).