From f4207507205d6e97d2595ff2dc70080e8e737e8f Mon Sep 17 00:00:00 2001
From: Ralf Kistner <ralf@journeyapps.com>
Date: Sat, 7 Dec 2024 18:48:43 +0200
Subject: [PATCH] Update supabase-auth.mdx

Fix image urls
---
 installation/authentication-setup/supabase-auth.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/installation/authentication-setup/supabase-auth.mdx b/installation/authentication-setup/supabase-auth.mdx
index 81a830be..48d108f5 100644
--- a/installation/authentication-setup/supabase-auth.mdx
+++ b/installation/authentication-setup/supabase-auth.mdx
@@ -36,11 +36,11 @@ To implement either **Supabase Auth** or **Anonymous Sign-Ins**, enable the rele
 2. Under the **"Client Auth"** tab, enable **"Use Supabase Auth"** and enter your Supabase **JWT Secret** (the secret can be copied from your Supabase project's API Settings):
 
 <Frame caption="Copy the secret from your Supabase project settings.">
-  <img src="/images/authentication/supabase-jwt-secret.png)" />
+  <img src="/images/authentication/supabase-jwt-secret.png" />
 </Frame>
 
 <Frame caption="Enable Supabase Auth in your PowerSync instance settings and paste the secret.">
-  <img src="/images/authentication/use-supabase-auth.png)" />
+  <img src="/images/authentication/use-supabase-auth.png" />
 </Frame>
 
 3. Click **"Save and deploy"** to deploy the updates to your instance.
@@ -58,4 +58,4 @@ client_auth:
 
 ## Sync Rules
 
-The Supabase user UUID will be available as `request.user_id()` in [Sync Rules](/usage/sync-rules). To use a different identifier as the user ID in sync rules (for example user email), use [Custom authentication](/installation/authentication-setup/custom).
\ No newline at end of file
+The Supabase user UUID will be available as `request.user_id()` in [Sync Rules](/usage/sync-rules). To use a different identifier as the user ID in sync rules (for example user email), use [Custom authentication](/installation/authentication-setup/custom).