[pull] master from supabase:master

apps/docs/content/_partials/billing/pricing/pricing_storage_image_transformations.mdx

@@ -1,5 +1,3 @@
-## Pricing
-
 <Price price="5" /> per 1,000 origin images. You are only charged for usage exceeding your subscription
 plan's quota.
 

apps/docs/content/guides/auth/server-side/creating-a-client.mdx

@@ -746,6 +746,6 @@ language="typescript"
 
 ## Next steps
 
-- Implement [Authentication using Email and Password](/docs/guides/auth/server-side/email-based-auth-with-pkce-flow-for-ssr)
+- Implement [Authentication using Email and Password](/docs/guides/auth/passwords)
 - Implement [Authentication using OAuth](/docs/guides/auth/social-login)
-- [Learn more about SSR](/docs/guides/auth/server-side-rendering)
+- [Learn more about SSR](/docs/guides/auth/server-side/advanced-guide)

apps/docs/content/guides/auth/server-side/migrating-to-ssr-from-auth-helpers.mdx

@@ -45,6 +45,6 @@ Check out the [Creating a client](/docs/guides/auth/server-side/creating-a-clien
 
 ## Next steps
 
-- Implement [Authentication using Email and Password](/docs/guides/auth/server-side/email-based-auth-with-pkce-flow-for-ssr)
-- Implement [Authentication using OAuth](/docs/guides/auth/server-side/oauth-with-pkce-flow-for-ssr)
-- [Learn more about SSR](/docs/guides/auth/server-side-rendering)
+- Implement [Authentication using Email and Password](/docs/guides/auth/passwords)
+- Implement [Authentication using OAuth](/docs/guides/auth/social-login)
+- [Learn more about SSR](/docs/guides/auth/server-side/advanced-guide)

apps/docs/content/guides/auth/social-login/auth-google.mdx

@@ -196,7 +196,7 @@ To use the Google provider in local development:
    ```env
    SUPABASE_AUTH_EXTERNAL_GOOGLE_CLIENT_SECRET="<client-secret>"
    ```
-2. Configure the provider:
+2. Configure the provider in `supabase/config.toml`:
    ```toml
    [auth.external.google]
    enabled = true

apps/docs/content/guides/deployment/branching/troubleshooting.mdx

@@ -45,7 +45,7 @@ These conflicts can be resolved in the same way as normal Git Conflicts: merge o
 
 ### Changing production branch
 
-It's not possible to change the Git branch used as the Production branch for Supabase Branching. The only way to change it is to disable and re-enable branching. See [Disable Branching](#disable-branching).
+You cannot change which project branch serves as the production branch — the base project that all branches are created from will always remain the production branch. However, you can update which GitHub branch is linked to your production branch. To do this, go to the [Integrations page](/dashboard/project/_/settings/integrations) and change the production branch name.
 
 ## Migration issues
 

apps/docs/content/guides/platform/manage-your-usage/storage-image-transformations.mdx

@@ -66,8 +66,6 @@ For simplicity, let's assume a package size of 1,000 and a charge of <Price pric
 
 Usage is shown as "Storage Image Transformations" on your invoice.
 
-## Pricing
-
 <$Partial path="billing/pricing/pricing_storage_image_transformations.mdx" />
 
 ## Billing examples

apps/docs/content/guides/realtime/broadcast.mdx

@@ -25,7 +25,7 @@ However, regardless of whether it's public or private, the Realtime service conn
 
 </Admonition>
 
-For Authorization we do insert a message and try to read it and then we it back as way to verify that the RLS policies set by the user are being respected by the user joining the channel but this messages won't be sent to the user. You can read more about it in the [Authorization](/docs/guides/realtime/authorization) docs
+For Authorization we insert a message and try to read it, and rollback the transaction to verify that the RLS policies set by the user are being respected by the user joining the channel, but this message isn't sent to the user. You can read more about it in the [Authorization docs](/docs/guides/realtime/authorization).
 
 ## Subscribe to messages