small fixes

Author: rishabhpoddar

v2/emailpassword/nextjs/app-directory/protecting-route.mdx

@@ -33,10 +33,12 @@ export const HomeClientComponent = () => {
 }
 ```
 
-`SessionAuth` is a component exposed by the SuperTokens React SDK, it checks if a session exists and if it does not exist it will redirect the user to the login page.
+`SessionAuth` is a component exposed by the SuperTokens React SDK, it checks if a session exists and if it does not exist it will redirect the user to the login page. It also does session claim checking on the frontend and take appropriate action if the claim validators fail. For example, if you have set the email verification recipe to be `"REQUIRED"`, and the user's email is not verified, this component will redirect the user to the email verification page.
 
 :::caution
-At the moment the `SessionAuth` component does not support server side rendering and will only work on the client side. Refer to the <a href="#sessions-with-server-components">next section</a> of this page to learn how to use sessions on the server side.
+At the moment the `SessionAuth` component does not support server side rendering and will only work on the client side. On the server side, this component renders an empty screen. 
+
+Refer to the <a href="#sessions-with-server-components">next section</a> of this page to learn how to use sessions on the server side.
 :::
 
 ### Using `useSessionContext`
@@ -108,7 +110,7 @@ This is a client component that renders just its children on the server side and
 
 #### Creating the `TryRefreshComponent`
 
-This component will refres hthe user's session if their current session has expired.
+This component will refresh the user's session if their current session has expired.
 
 ```tsx title="app/components/tryRefreshClientComponent.tsx"
 "use client";

v2/emailpassword/nextjs/app-directory/session-helpers.mdx

@@ -156,10 +156,10 @@ export async function withSession(
 ```
 
 - `getSSRSession` will be used in our frontend routes to get session information when rendering on the server side. This function will:
-    - `{..., session: Object, hasToken: true}` is a session exists
+    - `{..., session: Object, hasToken: true}` if a session exists
     - `{..., session: undefined, hasToken: false}` if a session does not exist
-    - `{..., session: undefined, hasToken: true}` if the session is expired
-    - `{..., session: undefined, hasInvalidClaims: true}` If the session claims fail their validation. For example if email verification if required but the user's email has not been verified.
+    - `{..., session: undefined, hasToken: true, hasInvalidClaims: false}` if the session is expired
+    - `{..., session: undefined, hasToken: true, hasInvalidClaims: true}` If the session claims fail their validation. For example if email verification if required but the user's email has not been verified.
 
 - `withSession` will be used as a session guard for each of our API routes. If a session exists it will be passed to the callback, which is where we will write our API logic. If no session exists it will pass `undefined` to the callback. This function will:
     - Return status `401` if the session has expired

v2/emailpassword/nextjs/app-directory/session-verification-middleware.mdx

@@ -17,7 +17,7 @@ This method is an alternative method for using sessions in an API. If you are al
 
 In the middleware we check if a session exists using the `withSession` helper function we created [here](./session-helpers.mdx) and set the user's user id to the request headers using the session object. You can set other information in the same way.
 
-:::note
+:::caution
 You cannot pass the full session container through the middleware because the Next.js middleware does not allow objects to be passed. If you need to access the full session container in your APIs switch to using [session guards](./session-verification-session-guard.mdx).
 :::
 
@@ -65,9 +65,9 @@ export const config = {
 }
 ```
 
-## Using the middleware in APIs
+## Fetching the user ID in your APIs
 
-The middleware will run for all our routes, we can read information set by the middleware in our API routes:
+The middleware will run for all routes, we can read information set by the middleware in the API routes:
 
 ```tsx title="app/api/userid/route.ts"
 import { NextResponse, NextRequest } from "next/server";

v2/emailpassword/nextjs/app-directory/session-verification-session-guard.mdx

@@ -1,13 +1,13 @@
 ---
 id: session-verification-session-guard
-title: Adding a session guard to all API routes 
+title: Adding a session guard to each API route 
 hide_title: true
 ---
 
 <!-- COPY DOCS -->
 <!-- ./thirdpartyemailpassword/nextjs/app-directory/session-verification-session-guard.mdx -->
 
-# Adding a session guard to all API routes
+# Adding a session guard to each API route
 
 :::note
 This is applicable for when the frontend calls an API in the `/app/api` folder.
@@ -46,5 +46,5 @@ export function GET(request: NextRequest) {
 In the above snippet we are creating a `GET` handler for the `/api/user` route. We call the `withSession` helper function we created in a [previous step](./session-helpers.mdx), the function will pass the session object in the callback which we then use to read user information. If a session does not exist `undefined` will be passed intead.
 
 The `withSession` guard will return:
-    - Status `401` if the session does not exist or has expired
-    - Stauts `403` if the session claims fail their validation. For example if email verification is required but the user's email is not verified.
+- Status `401` if the session does not exist or has expired
+- Stauts `403` if the session claims fail their validation. For example if email verification is required but the user's email is not verified.

v2/passwordless/nextjs/app-directory/protecting-route.mdx

@@ -33,10 +33,12 @@ export const HomeClientComponent = () => {
 }
 ```
 
-`SessionAuth` is a component exposed by the SuperTokens React SDK, it checks if a session exists and if it does not exist it will redirect the user to the login page.
+`SessionAuth` is a component exposed by the SuperTokens React SDK, it checks if a session exists and if it does not exist it will redirect the user to the login page. It also does session claim checking on the frontend and take appropriate action if the claim validators fail. For example, if you have set the email verification recipe to be `"REQUIRED"`, and the user's email is not verified, this component will redirect the user to the email verification page.
 
 :::caution
-At the moment the `SessionAuth` component does not support server side rendering and will only work on the client side. Refer to the <a href="#sessions-with-server-components">next section</a> of this page to learn how to use sessions on the server side.
+At the moment the `SessionAuth` component does not support server side rendering and will only work on the client side. On the server side, this component renders an empty screen. 
+
+Refer to the <a href="#sessions-with-server-components">next section</a> of this page to learn how to use sessions on the server side.
 :::
 
 ### Using `useSessionContext`
@@ -108,7 +110,7 @@ This is a client component that renders just its children on the server side and
 
 #### Creating the `TryRefreshComponent`
 
-This component will refres hthe user's session if their current session has expired.
+This component will refresh the user's session if their current session has expired.
 
 ```tsx title="app/components/tryRefreshClientComponent.tsx"
 "use client";

v2/passwordless/nextjs/app-directory/session-helpers.mdx

@@ -156,10 +156,10 @@ export async function withSession(
 ```
 
 - `getSSRSession` will be used in our frontend routes to get session information when rendering on the server side. This function will:
-    - `{..., session: Object, hasToken: true}` is a session exists
+    - `{..., session: Object, hasToken: true}` if a session exists
     - `{..., session: undefined, hasToken: false}` if a session does not exist
-    - `{..., session: undefined, hasToken: true}` if the session is expired
-    - `{..., session: undefined, hasInvalidClaims: true}` If the session claims fail their validation. For example if email verification if required but the user's email has not been verified.
+    - `{..., session: undefined, hasToken: true, hasInvalidClaims: false}` if the session is expired
+    - `{..., session: undefined, hasToken: true, hasInvalidClaims: true}` If the session claims fail their validation. For example if email verification if required but the user's email has not been verified.
 
 - `withSession` will be used as a session guard for each of our API routes. If a session exists it will be passed to the callback, which is where we will write our API logic. If no session exists it will pass `undefined` to the callback. This function will:
     - Return status `401` if the session has expired

v2/passwordless/nextjs/app-directory/session-verification-middleware.mdx

@@ -17,7 +17,7 @@ This method is an alternative method for using sessions in an API. If you are al
 
 In the middleware we check if a session exists using the `withSession` helper function we created [here](./session-helpers.mdx) and set the user's user id to the request headers using the session object. You can set other information in the same way.
 
-:::note
+:::caution
 You cannot pass the full session container through the middleware because the Next.js middleware does not allow objects to be passed. If you need to access the full session container in your APIs switch to using [session guards](./session-verification-session-guard.mdx).
 :::
 
@@ -65,9 +65,9 @@ export const config = {
 }
 ```
 
-## Using the middleware in APIs
+## Fetching the user ID in your APIs
 
-The middleware will run for all our routes, we can read information set by the middleware in our API routes:
+The middleware will run for all routes, we can read information set by the middleware in the API routes:
 
 ```tsx title="app/api/userid/route.ts"
 import { NextResponse, NextRequest } from "next/server";

v2/passwordless/nextjs/app-directory/session-verification-session-guard.mdx

@@ -1,13 +1,13 @@
 ---
 id: session-verification-session-guard
-title: Adding a session guard to all API routes 
+title: Adding a session guard to each API route 
 hide_title: true
 ---
 
 <!-- COPY DOCS -->
 <!-- ./thirdpartyemailpassword/nextjs/app-directory/session-verification-session-guard.mdx -->
 
-# Adding a session guard to all API routes
+# Adding a session guard to each API route
 
 :::note
 This is applicable for when the frontend calls an API in the `/app/api` folder.
@@ -46,5 +46,5 @@ export function GET(request: NextRequest) {
 In the above snippet we are creating a `GET` handler for the `/api/user` route. We call the `withSession` helper function we created in a [previous step](./session-helpers.mdx), the function will pass the session object in the callback which we then use to read user information. If a session does not exist `undefined` will be passed intead.
 
 The `withSession` guard will return:
-    - Status `401` if the session does not exist or has expired
-    - Stauts `403` if the session claims fail their validation. For example if email verification is required but the user's email is not verified.
+- Status `401` if the session does not exist or has expired
+- Stauts `403` if the session claims fail their validation. For example if email verification is required but the user's email is not verified.

v2/thirdparty/nextjs/app-directory/protecting-route.mdx

@@ -33,10 +33,12 @@ export const HomeClientComponent = () => {
 }
 ```
 
-`SessionAuth` is a component exposed by the SuperTokens React SDK, it checks if a session exists and if it does not exist it will redirect the user to the login page.
+`SessionAuth` is a component exposed by the SuperTokens React SDK, it checks if a session exists and if it does not exist it will redirect the user to the login page. It also does session claim checking on the frontend and take appropriate action if the claim validators fail. For example, if you have set the email verification recipe to be `"REQUIRED"`, and the user's email is not verified, this component will redirect the user to the email verification page.
 
 :::caution
-At the moment the `SessionAuth` component does not support server side rendering and will only work on the client side. Refer to the <a href="#sessions-with-server-components">next section</a> of this page to learn how to use sessions on the server side.
+At the moment the `SessionAuth` component does not support server side rendering and will only work on the client side. On the server side, this component renders an empty screen. 
+
+Refer to the <a href="#sessions-with-server-components">next section</a> of this page to learn how to use sessions on the server side.
 :::
 
 ### Using `useSessionContext`
@@ -108,7 +110,7 @@ This is a client component that renders just its children on the server side and
 
 #### Creating the `TryRefreshComponent`
 
-This component will refres hthe user's session if their current session has expired.
+This component will refresh the user's session if their current session has expired.
 
 ```tsx title="app/components/tryRefreshClientComponent.tsx"
 "use client";

v2/thirdparty/nextjs/app-directory/session-helpers.mdx

@@ -156,10 +156,10 @@ export async function withSession(
 ```
 
 - `getSSRSession` will be used in our frontend routes to get session information when rendering on the server side. This function will:
-    - `{..., session: Object, hasToken: true}` is a session exists
+    - `{..., session: Object, hasToken: true}` if a session exists
     - `{..., session: undefined, hasToken: false}` if a session does not exist
-    - `{..., session: undefined, hasToken: true}` if the session is expired
-    - `{..., session: undefined, hasInvalidClaims: true}` If the session claims fail their validation. For example if email verification if required but the user's email has not been verified.
+    - `{..., session: undefined, hasToken: true, hasInvalidClaims: false}` if the session is expired
+    - `{..., session: undefined, hasToken: true, hasInvalidClaims: true}` If the session claims fail their validation. For example if email verification if required but the user's email has not been verified.
 
 - `withSession` will be used as a session guard for each of our API routes. If a session exists it will be passed to the callback, which is where we will write our API logic. If no session exists it will pass `undefined` to the callback. This function will:
     - Return status `401` if the session has expired

v2/thirdparty/nextjs/app-directory/session-verification-middleware.mdx

@@ -17,7 +17,7 @@ This method is an alternative method for using sessions in an API. If you are al
 
 In the middleware we check if a session exists using the `withSession` helper function we created [here](./session-helpers.mdx) and set the user's user id to the request headers using the session object. You can set other information in the same way.
 
-:::note
+:::caution
 You cannot pass the full session container through the middleware because the Next.js middleware does not allow objects to be passed. If you need to access the full session container in your APIs switch to using [session guards](./session-verification-session-guard.mdx).
 :::
 
@@ -65,9 +65,9 @@ export const config = {
 }
 ```
 
-## Using the middleware in APIs
+## Fetching the user ID in your APIs
 
-The middleware will run for all our routes, we can read information set by the middleware in our API routes:
+The middleware will run for all routes, we can read information set by the middleware in the API routes:
 
 ```tsx title="app/api/userid/route.ts"
 import { NextResponse, NextRequest } from "next/server";

v2/thirdparty/nextjs/app-directory/session-verification-session-guard.mdx

@@ -1,13 +1,13 @@
 ---
 id: session-verification-session-guard
-title: Adding a session guard to all API routes 
+title: Adding a session guard to each API route 
 hide_title: true
 ---
 
 <!-- COPY DOCS -->
 <!-- ./thirdpartyemailpassword/nextjs/app-directory/session-verification-session-guard.mdx -->
 
-# Adding a session guard to all API routes
+# Adding a session guard to each API route
 
 :::note
 This is applicable for when the frontend calls an API in the `/app/api` folder.
@@ -46,5 +46,5 @@ export function GET(request: NextRequest) {
 In the above snippet we are creating a `GET` handler for the `/api/user` route. We call the `withSession` helper function we created in a [previous step](./session-helpers.mdx), the function will pass the session object in the callback which we then use to read user information. If a session does not exist `undefined` will be passed intead.
 
 The `withSession` guard will return:
-    - Status `401` if the session does not exist or has expired
-    - Stauts `403` if the session claims fail their validation. For example if email verification is required but the user's email is not verified.
+- Status `401` if the session does not exist or has expired
+- Stauts `403` if the session claims fail their validation. For example if email verification is required but the user's email is not verified.

v2/thirdpartyemailpassword/nextjs/app-directory/protecting-route.mdx

@@ -33,10 +33,12 @@ export const HomeClientComponent = () => {
 }
 ```
 
-`SessionAuth` is a component exposed by the SuperTokens React SDK, it checks if a session exists and if it does not exist it will redirect the user to the login page.
+`SessionAuth` is a component exposed by the SuperTokens React SDK, it checks if a session exists and if it does not exist it will redirect the user to the login page. It also does session claim checking on the frontend and take appropriate action if the claim validators fail. For example, if you have set the email verification recipe to be `"REQUIRED"`, and the user's email is not verified, this component will redirect the user to the email verification page.
 
 :::caution
-At the moment the `SessionAuth` component does not support server side rendering and will only work on the client side. Refer to the <a href="#sessions-with-server-components">next section</a> of this page to learn how to use sessions on the server side.
+At the moment the `SessionAuth` component does not support server side rendering and will only work on the client side. On the server side, this component renders an empty screen. 
+
+Refer to the <a href="#sessions-with-server-components">next section</a> of this page to learn how to use sessions on the server side.
 :::
 
 ### Using `useSessionContext`
@@ -108,7 +110,7 @@ This is a client component that renders just its children on the server side and
 
 #### Creating the `TryRefreshComponent`
 
-This component will refres hthe user's session if their current session has expired.
+This component will refresh the user's session if their current session has expired.
 
 ```tsx title="app/components/tryRefreshClientComponent.tsx"
 "use client";

v2/thirdpartyemailpassword/nextjs/app-directory/session-helpers.mdx

@@ -156,10 +156,10 @@ export async function withSession(
 ```
 
 - `getSSRSession` will be used in our frontend routes to get session information when rendering on the server side. This function will:
-    - `{..., session: Object, hasToken: true}` is a session exists
+    - `{..., session: Object, hasToken: true}` if a session exists
     - `{..., session: undefined, hasToken: false}` if a session does not exist
-    - `{..., session: undefined, hasToken: true}` if the session is expired
-    - `{..., session: undefined, hasInvalidClaims: true}` If the session claims fail their validation. For example if email verification if required but the user's email has not been verified.
+    - `{..., session: undefined, hasToken: true, hasInvalidClaims: false}` if the session is expired
+    - `{..., session: undefined, hasToken: true, hasInvalidClaims: true}` If the session claims fail their validation. For example if email verification if required but the user's email has not been verified.
 
 - `withSession` will be used as a session guard for each of our API routes. If a session exists it will be passed to the callback, which is where we will write our API logic. If no session exists it will pass `undefined` to the callback. This function will:
     - Return status `401` if the session has expired