diff --git a/apps/docs/content/guides/auth/server-side/creating-a-client.mdx b/apps/docs/content/guides/auth/server-side/creating-a-client.mdx index 06af1a56e1102..7a35b70fdccc6 100644 --- a/apps/docs/content/guides/auth/server-side/creating-a-client.mdx +++ b/apps/docs/content/guides/auth/server-side/creating-a-client.mdx @@ -747,5 +747,5 @@ 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 OAuth](/docs/guides/auth/server-side/oauth-with-pkce-flow-for-ssr) +- Implement [Authentication using OAuth](/docs/guides/auth/social-login) - [Learn more about SSR](/docs/guides/auth/server-side-rendering) diff --git a/apps/www/_blog/2025-07-15-analytics-buckets.mdx b/apps/www/_blog/2025-07-15-analytics-buckets.mdx index de22fb8bd671c..3b70a2ab85b25 100644 --- a/apps/www/_blog/2025-07-15-analytics-buckets.mdx +++ b/apps/www/_blog/2025-07-15-analytics-buckets.mdx @@ -103,7 +103,7 @@ Back in Studio, we can see the newly created our newly created Namespace with `0 src="/images/blog/launch-week-15/day-2-analytics-buckets/img5.png" /> -Click connect and select a `Target Schema` to map the Iceberg tables into. It is reccomended to create a standalone schema for your tables. Do not use the `public` schema because that would expose your table over the project's REST API. +Click connect and select a `Target Schema` to map the Iceberg tables into. It is recommended to create a standalone schema for your tables. Do not use the `public` schema because that would expose your table over the project's REST API.