Update apps/reference/docs/guides/platform/disk-usage.mdx

Co-authored-by: dng <danny@supabase.io>

apps/reference/docs/guides/platform/disk-usage.mdx

@@ -23,4 +23,4 @@ Postgres does not immediately reclaim the physical space used by dead tuples (i.
 Vacuum operations can temporarily increase resource utilization, which can adversely impact the observed performance of your project until the maintenance is completed.
 :::
 
-Supabase projects come with automatic vacuuming enabled, which ensures that these operations are performed regularly, in order to keep the database healthy and performant. However, it can sometimes be necessary to either [fine-tune](https://www.percona.com/blog/2018/08/10/tuning-autovacuum-in-postgresql-and-autovacuum-internals/) [the autovacuum parameters](https://www.enterprisedb.com/blog/postgresql-vacuum-and-analyze-best-practice-tips), or [manually initiate](https://www.postgresql.org/docs/current/sql-vacuum.html) vacuum operations. As an example, running a manual vacuum after deleting large amounts of data from your DB could help reduce the reported disk usage by Postgres.
+Supabase projects have automatic vacuuming, which ensures that these operations are performed regularly to keep the database healthy and performant. However, it can be necessary to either [fine-tune](https://www.percona.com/blog/2018/08/10/tuning-autovacuum-in-postgresql-and-autovacuum-internals/) [the autovacuum parameters](https://www.enterprisedb.com/blog/postgresql-vacuum-and-analyze-best-practice-tips), or [manually initiate](https://www.postgresql.org/docs/current/sql-vacuum.html) vacuum operations. For example, running a manual vacuum after deleting large amounts of data from your DB could help reduce the reported disk usage by Postgres.