fixes broken link

supertokens · Jul 22, 2024 · 4d67e37 · 4d67e37
1 parent 16e66a9
commit 4d67e37
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/v2/emailpassword/nextjs/app-directory/about.mdx b/v2/emailpassword/nextjs/app-directory/about.mdx
@@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam
 
 Integrating SuperTokens with a Next.js app involves:
 - Calling the frontend and backend init functions
-- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend).
+- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend).
 - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default)
 - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page
 - Performing session verification:

diff --git a/v2/passwordless/nextjs/app-directory/about.mdx b/v2/passwordless/nextjs/app-directory/about.mdx
@@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam
 
 Integrating SuperTokens with a Next.js app involves:
 - Calling the frontend and backend init functions
-- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend).
+- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend).
 - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default)
 - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page
 - Performing session verification:

diff --git a/v2/thirdparty/nextjs/app-directory/about.mdx b/v2/thirdparty/nextjs/app-directory/about.mdx
@@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam
 
 Integrating SuperTokens with a Next.js app involves:
 - Calling the frontend and backend init functions
-- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend).
+- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend).
 - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default)
 - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page
 - Performing session verification:

diff --git a/v2/thirdpartyemailpassword/nextjs/app-directory/about.mdx b/v2/thirdpartyemailpassword/nextjs/app-directory/about.mdx
@@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam
 
 Integrating SuperTokens with a Next.js app involves:
 - Calling the frontend and backend init functions
-- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend).
+- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend).
 - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default)
 - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page
 - Performing session verification:

diff --git a/v2/thirdpartypasswordless/nextjs/app-directory/about.mdx b/v2/thirdpartypasswordless/nextjs/app-directory/about.mdx
@@ -40,7 +40,7 @@ npx create-supertokens-app@latest --frontend=next --recipe=^{codeImportRecipeNam
 
 Integrating SuperTokens with a Next.js app involves:
 - Calling the frontend and backend init functions
-- Building the various auth flows as per the [custom UI setup guide](../custom-ui/init/frontend).
+- Building the various auth flows as per the [custom UI setup guide](../../custom-ui/init/frontend).
 - Creating a serverless function to expose the auth related APIs which will be consumed by the frontend widgets (on `/api/auth/` by default)
 - Protecting website routes: Displaying them only when a user is logged in, else redirecting them to the login page
 - Performing session verification: