Correct production frontend hostname

README.md

@@ -51,7 +51,7 @@ Apply `../Database/migrations/20261016_node_analysis.sql` before analyses. It as
 2. Authentication → Providers → Google: enable it, add the Google client ID/secret, and use Supabase's displayed callback URL in Google Cloud.
 3. Authentication → URL Configuration:
    - Site URL: `http://localhost:8080` during development.
-   - Redirect URLs: `http://localhost:4000/api/auth/callback` (and its `?next=**` variant) for development; `https://sporalizer.pages.dev/api/auth/callback` and `https://sporalizer.pages.dev/api/auth/callback?next=**` for production. Replace the frontend origin if deploying elsewhere. The Google Cloud redirect URI stays the Supabase provider callback.
+   - Redirect URLs: `http://localhost:4000/api/auth/callback` (and its `?next=**` variant) for development; `https://sporalize.pages.dev/api/auth/callback` and `https://sporalize.pages.dev/api/auth/callback?next=**` for production. Replace the frontend origin if deploying elsewhere. The Google Cloud redirect URI stays the Supabase provider callback.
 
 ## Brevo email verification
 
@@ -71,7 +71,7 @@ Brevo is configured as Supabase Auth's SMTP provider; the Express API does not s
 
    ```html
    <h2>Confirm your Sporalize account</h2>
-   <p><a href="https://sporalizer.pages.dev/api/auth/confirm?token_hash={{ .TokenHash }}">Confirm email</a></p>
+   <p><a href="https://sporalize.pages.dev/api/auth/confirm?token_hash={{ .TokenHash }}">Confirm email</a></p>
    ```
 
    Set **Site URL** to the frontend origin. Allow the frontend callback URLs listed above. The Pages proxy forwards confirmation to the backend, which verifies the one-time token and redirects to `/login?verified=1`; the user then signs in with their email and password. Existing email links using the Space origin should be replaced by newly issued emails.