From de4fce113fa2cb33380ed0a2d09e7d33e8a451c2 Mon Sep 17 00:00:00 2001
From: Copple <10214025+kiwicopple@users.noreply.github.com>
Date: Tue, 16 May 2023 19:09:16 -0700
Subject: [PATCH] pgaudit

---
 apps/docs/pages/guides/platform/going-into-prod.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/apps/docs/pages/guides/platform/going-into-prod.mdx b/apps/docs/pages/guides/platform/going-into-prod.mdx
index 39841ba37c3..f03cb5361c2 100644
--- a/apps/docs/pages/guides/platform/going-into-prod.mdx
+++ b/apps/docs/pages/guides/platform/going-into-prod.mdx
@@ -92,10 +92,10 @@ As your team grows, consider the different [access levels](/docs/guides/platform
 - Free and Pro: Supabase provides access controls within the Dashboard for Developers and Administrators.
 - Teams and Enterprise: these tiers include advanced access controls, such as read-only Dashboard roles.
 
-You can turn on the [PGAudit](/docs/guides/database/extensions/pgaudit) extension to keep track of all changes to your database.
-
 For a more secure setup, consider running your workload across several organizations. It's a common pattern to have a Production organization which is restricted to only those team members who are qualified to have direct access to production databases.
 
+One other small tipe: the [PGAudit](/docs/guides/database/extensions/pgaudit) extension tracks changes to your database. You can use it to track schema changes.
+
 ## Next steps
 
 This checklist is always growing so be sure to check back frequently, and also feel free to suggest additions and amendments by making a PR on [GitHub](https://github.com/supabase/supabase).