From 475dfb3063df3f8baf08bf536d69fb9607eb5383 Mon Sep 17 00:00:00 2001
From: TheOtherBrian1 <91111415+TheOtherBrian1@users.noreply.github.com>
Date: Tue, 27 Feb 2024 11:13:33 -0500
Subject: [PATCH] Removed typo configuration.mdx

---
 .../docs/pages/guides/database/postgres/configuration.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/apps/docs/pages/guides/database/postgres/configuration.mdx b/apps/docs/pages/guides/database/postgres/configuration.mdx
index 9c685b06606..32a2423354f 100644
--- a/apps/docs/pages/guides/database/postgres/configuration.mdx
+++ b/apps/docs/pages/guides/database/postgres/configuration.mdx
@@ -20,19 +20,19 @@ SELECT
 FROM pg_roles
 WHERE rolname IN (
   'anon',
-  'authenticated'
+  'authenticated',
   'postgres',
-  'service_role',
+  'service_role'
 );
 ```
 
-Additionally, all users are subject to a global limit of _2 minutes_. This serves as a backstop against resource exhaustion due to either poorly written queries, or abusive usage. The current global timeout can be view with the following query:
+Additionally, all users are subject to a global limit of _2 minutes_. This serves as a backstop against resource exhaustion due to either poorly written queries, or abusive usage. To view the global timeout, you can execute the below query:
 
 ```sql
 SHOW statement_timeout;
 ```
 
-This can be overridden using [Custom Postgres configuration](https://supabase.com/docs/guides/platform/custom-postgres-config#supported-parameters). The below example is for changing the global timeout with NPX:
+This can be overridden using [Custom Postgres configuration](https://supabase.com/docs/guides/platform/custom-postgres-config#supported-parameters). The below example is for changing the global timeout with `npx`:
 
 ```bash
 #Logs you into the Supabase CLI