From 4ee7e0849339ca6be986ef6ea9c1ff2c0bfb333a Mon Sep 17 00:00:00 2001
From: Chris Gwilliams <517923+encima@users.noreply.github.com>
Date: Wed, 6 Aug 2025 08:38:09 +0300
Subject: [PATCH] Update event-triggers.mdx

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
 apps/docs/content/guides/database/postgres/event-triggers.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/docs/content/guides/database/postgres/event-triggers.mdx b/apps/docs/content/guides/database/postgres/event-triggers.mdx
index fb5db6d9b38..434e24c6db4 100644
--- a/apps/docs/content/guides/database/postgres/event-triggers.mdx
+++ b/apps/docs/content/guides/database/postgres/event-triggers.mdx
@@ -10,7 +10,7 @@ In Postgres, an [event trigger](https://www.postgresql.org/docs/current/event-tr
 With our `Supautils` extension (installed automatically for all Supabase projects), the `postgres` user has the ability to create and manage event triggers.
 
 Some use cases for event triggers ares:
-- Capturing Data Definition Language (DDL) changes - these are changes to your database schema (though the [pgaudit](/docs/guides/database/extensions/pgaudit) extension provides a more complete solution)
+- Capturing Data Definition Language (DDL) changes - these are changes to your database schema (though the [pgAudit](/docs/guides/database/extensions/pgaudit) extension provides a more complete solution)
 - Monitoring/preventing actions - such as preventing tables from being dropped in Production or enforcing RLS on all new tables
 
 In this guide, we will go through an example event trigger that prevents accidental dropping of a table