diff --git a/snippets/supabase-database-connection.mdx b/snippets/supabase-database-connection.mdx
index c48c8dc4..e1a71414 100644
--- a/snippets/supabase-database-connection.mdx
+++ b/snippets/supabase-database-connection.mdx
@@ -14,18 +14,18 @@
 
    * PowerSync has the Supabase CA certificate pre-configured — `verify-full` SSL mode can be used directly, without any custom certificates.
 
-   - In your Supabase dashboard, navigate to **"Project Settings"** -> **"Database" -> "Connection string**" and select the "URI" tab.
+   * In your Supabase dashboard, navigate to **Project Settings** > **Database** > **Connection string** and select the "URI" tab.
 
-   - Uncheck the "**Display connection pooler**" checkbox. PowerSync needs to connect to the database directly and cannot use the pooler.
+   * Uncheck the **Display connection pooler** checkbox. PowerSync needs to connect to the database directly and cannot use the pooler.
 
-2. Click **"Test Connection"** and fix any errors.
+2. Click **Test Connection** and fix any errors.
 
-3. Under the **"Client Auth"** tab, enable **"Use Supabase Auth"** and enter your Supabase **JWT Secret**:
+3. Under the **Client Auth** tab, enable **Use Supabase Auth** and enter your Supabase **JWT Secret**:
   
   <Frame caption="PowerSync uses the secret to verify Supabase's JWTs">
     <img src="/images/authentication/use-supabase-auth.png" />
   </Frame>
 
-4. Click **"Save and deploy"** to deploy the updates to your instance.
+4. Click **Save and deploy** to deploy the updates to your instance.
 
 PowerSync deploys and configures an isolated cloud environment for you, which will take a few minutes to complete.
\ No newline at end of file