changes from docs review

auth-react/docs/emailpassword/email-password-auth.md

@@ -36,8 +36,7 @@ __HIGHLIGHT__        return (
 - `EmailPasswordAuth` will update the session, because it uses `SessionAuth` underneath. Read more about session updates in [SessionAuth guide](../session/session-auth).
 
 ## Handle session expiry
-If you pass function to `onSessionExpired` prop, it will be called whenever session expires. This will also prevent
-children from receiving `SessionContext` update, so that you can preserve the UI for authenticated user to improve UX.
+If you pass a function to `onSessionExpired` prop, it will be called whenever the session expires. This will also prevent children from receiving `SessionContext` update, so that you can preserve the UI for authenticated user.
 
 Example:
 ```tsx

auth-react/docs/session/session-auth.md

@@ -78,8 +78,7 @@ const App = () => {
 ```
 
 ### Respond to session expiry
-If you pass function as `onSessionExpired` prop, it will be called whenever session expires.
-**When session expires this will prevent `SessionContext` from updating**. This means you can still display the UI for authenticated user.
+If you pass a function as `onSessionExpired` prop, it will be called whenever session expires. **When session expires this will prevent `SessionContext` from updating**. This means you can still display the UI for authenticated user.
 
 Example:
 ```tsx

auth-react/docs/thirdparty/third-party-auth.md

@@ -38,8 +38,7 @@ __HIGHLIGHT__        return (
 - `ThirdPartyAuth` will update the session, because it uses `SessionAuth` underneath. Read more about session updates in [SessionAuth guide](../session/session-auth).
 
 ## Handle session expiry
-If you pass function to `onSessionExpired` prop, it will be called whenever session expires. This will also prevent
-children from receiving `SessionContext` update, so that you can preserve the UI for authenticated user to improve UX.
+If you pass a function to `onSessionExpired` prop, it will be called whenever the session expires. This will also prevent children from receiving `SessionContext` update, so that you can preserve the UI for authenticated user.
 
 Example:
 ```tsx

auth-react/docs/thirdpartyemailpassword/third-party-email-password-auth.md

@@ -39,8 +39,7 @@ __HIGHLIGHT__        return (
 - `ThirdPartyEmailPasswordAuth` will update the session, because it uses `SessionAuth` underneath. Read more about session updates in [SessionAuth guide](../session/session-auth).
 
 ## Handle session expiry
-If you pass function to `onSessionExpired` prop, it will be called whenever session expires. This will also prevent
-children from receiving `SessionContext` update, so that you can preserve the UI for authenticated user to improve UX.
+If you pass a function to `onSessionExpired` prop, it will be called whenever the session expires. This will also prevent children from receiving `SessionContext` update, so that you can preserve the UI for authenticated user.
 
 Example:
 ```tsx

emailpassword/docs/common-customizations/sessions/handling-session-expiry.md

@@ -18,28 +18,13 @@ you can pass function in `onSessionExpired` prop. This function will be called w
 ```tsx
 const App = () => {
     return (
-        <EmailPasswordAuth onSessionExpired={onSessionExpired}>
+        <EmailPasswordAuth onSessionExpired={showSessionExpiredPopup}>
             <MyComponent />
         </EmailPasswordAuth>
     );
 }
 ```
 
-### Preserving the UI on session expiry
-By passing `onSessionExpired` you are preventing the update to `SessionContext` that `MyComponent` would receive
-when session expires. This allows you to handle session expiry while still displaying UI for authenticated user to improve UX.
-
-Example:
-```tsx
-const App = () => {
-    return (
-        <EmailPasswordAuth onSessionExpired={displayLoginPopup}>
-            <MyComponent />
-        </EmailPasswordAuth>
-    );
-};
-```
-
-If you don't specify the `onSessionExpired`, the default behaviour is redirecting the user to where they might sign in.
+> You will need to either reload the current page or redirect the user to the sign in page if you provide this callback.
 
 Read more about `EmailPasswordAuth` and `onSessionExpired` in [its API reference](/docs/auth-react/docs/emailpassword/email-password-auth).

emailpassword/docs/common-customizations/sessions/securing-component.md

@@ -1,10 +1,10 @@
 ---
 id: securing-component
-title: Securing component
+title: Securing a website route / component
 hide_title: true
 ---
 
-# Securing a component
+# Securing a website route / component
 You may want to prevent rendering of some part of UI, or a route, when
 there's no session.
 

emailpassword/docs/common-customizations/sessions/user-information-front-end.md

@@ -48,19 +48,6 @@ render() {
      );
 }
 ```
-
-### Automatic context updates
-`SessionContext` will be updated for `EmailPasswordAuth` children whenever any of the following events happens:
-- App is loaded or reloaded
-- User signs in
-- User signs out
-- Session expires
-- Session is refreshed
-
-The only exception is when you use `onSessionExpired`, which is explained in [Handling session expiry](./handling-session-expiry).
-
-You can read more about `EmailPasswordAuth` in [its API guide](/docs/auth-react/docs/emailpassword/email-password-auth)
-
 ## Without React context 
 ```js
 import Session from 'supertokens-auth-react/recipe/session';

session/docs/advanced-customizations/frontend-hooks/handle-event.md

@@ -21,10 +21,7 @@ Session.init({
         } else if (context.action === "UNAUTHORISED") {
             // called when the session has expired
         } else if (context.action === "SESSION_CREATED") {
-            // Called when session is created.
-            //
-            // It means that if session previously existed
-            // and it only gets refreshed, this event will not be fired
+            // Called when session is created - post login / sign up.
         }
     }
 })

session/docs/common-customizations/sessions/handling-session-expiry.md

@@ -18,28 +18,13 @@ you can pass function in `onSessionExpired` prop. This function will be called w
 ```tsx
 const App = () => {
     return (
-        <SessionAuth onSessionExpired={onSessionExpired}>
+        <SessionAuth onSessionExpired={showSessionExpiredPopup}>
             <MyComponent />
         </SessionAuth>
     );
 }
 ```
 
-### Preserving the UI on session expiry
-By passing `onSessionExpired` you are preventing the update to `SessionContext` that `MyComponent` would receive
-when session expires. This allows you to handle session expiry while still displaying UI for authenticated user to improve UX.
-
-Example:
-```tsx
-const App = () => {
-    return (
-        <SessionAuth onSessionExpired={displayLoginPopup}>
-            <MyComponent />
-        </SessionAuth>
-    );
-};
-```
-
-If you don't specify the `onSessionExpired`, it will be handled by `redirectToLogin` by default.
+> You will need to either reload the current page or redirect the user to the sign in page if you provide this callback.
 
 Read more about `SessionAuth` and `onSessionExpired` in [its API reference](/docs/auth-react/docs/session/session-auth).

session/docs/common-customizations/sessions/securing-component.md

@@ -1,10 +1,10 @@
 ---
 id: securing-component
-title: Securing component
+title: Securing a website route / component
 hide_title: true
 ---
 
-# Securing a component
+# Securing a website route / component
 You may want to prevent rendering of some part of UI, or a route, when
 there's no session.
 

session/docs/common-customizations/sessions/user-information-front-end.md

@@ -49,16 +49,6 @@ render() {
 }
 ```
 
-### Automatic context updates
-`SessionContext` will be updated for `SessionAuth` children whenever any of the following events happens:
-- App is loaded or reloaded
-- User signs in
-- User signs out
-- Session expires
-- Session is refreshed
-
-The only exception is when you use `onSessionExpired`, which is explained in [Handling session expiry](./handling-session-expiry).
-
 ## Without React context 
 ```js
 import Session from 'supertokens-auth-react/recipe/session';

thirdparty/docs/common-customizations/sessions/handling-session-expiry.md

@@ -18,28 +18,13 @@ you can pass function in `onSessionExpired` prop. This function will be called w
 ```tsx
 const App = () => {
     return (
-        <ThirdPartyAuth onSessionExpired={onSessionExpired}>
+        <ThirdPartyAuth onSessionExpired={showSessionExpiredPopup}>
             <MyComponent />
         </ThirdPartyAuth>
     );
 }
 ```
 
-### Preserving the UI on session expiry
-By passing `onSessionExpired` you are preventing the update to `SessionContext` that `MyComponent` would receive
-when session expires. This allows you to handle session expiry while still displaying UI for authenticated user to improve UX.
-
-Example:
-```tsx
-const App = () => {
-    return (
-        <ThirdPartyAuth onSessionExpired={displayLoginPopup}>
-            <MyComponent />
-        </ThirdPartyAuth>
-    );
-};
-```
-
-If you don't specify the `onSessionExpired`, the default behaviour is redirecting the user to where they might sign in.
+> You will need to either reload the current page or redirect the user to the sign in page if you provide this callback.
 
 Read more about `ThirdPartyAuth` and `onSessionExpired` in [its API reference](/docs/auth-react/docs/thirdparty/third-party-auth).

thirdparty/docs/common-customizations/sessions/securing-component.md

@@ -1,10 +1,10 @@
 ---
 id: securing-component
-title: Securing component
+title: Securing a website route / component
 hide_title: true
 ---
 
-# Securing a component
+# Securing a website route / component
 You may want to prevent rendering of some part of UI, or a route, when
 there's no session.
 

thirdparty/docs/common-customizations/sessions/user-information-front-end.md

@@ -49,18 +49,6 @@ render() {
 }
 ```
 
-### Automatic context updates
-`SessionContext` will be updated for `ThirdPartyAuth` children whenever any of the following events happens:
-- App is loaded or reloaded
-- User signs in
-- User signs out
-- Session expires
-- Session is refreshed
-
-The only exception is when you use `onSessionExpired`, which is explained in [Handling session expiry](./handling-session-expiry).
-
-You can read more about `ThirdPartyAuth` in [its API guide](/docs/auth-react/docs/thirdparty/third-party-auth)
-
 ## Without React context 
 ```js
 import Session from 'supertokens-auth-react/recipe/session';

thirdpartyemailpassword/docs/common-customizations/sessions/handling-session-expiry.md

@@ -18,28 +18,13 @@ you can pass function in `onSessionExpired` prop. This function will be called w
 ```tsx
 const App = () => {
     return (
-        <ThirdPartyEmailPasswordAuth onSessionExpired={onSessionExpired}>
+        <ThirdPartyEmailPasswordAuth onSessionExpired={showSessionExpiredPopup}>
             <MyComponent />
         </ThirdPartyEmailPasswordAuth>
     );
 }
 ```
 
-### Preserving the UI on session expiry
-By passing `onSessionExpired` you are preventing the update to `SessionContext` that `MyComponent` would receive
-when session expires. This allows you to handle session expiry while still displaying UI for authenticated user to improve UX.
-
-Example:
-```tsx
-const App = () => {
-    return (
-        <ThirdPartyEmailPasswordAuth onSessionExpired={displayLoginPopup}>
-            <MyComponent />
-        </ThirdPartyEmailPasswordAuth>
-    );
-};
-```
-
-If you don't specify the `onSessionExpired`, the default behaviour is redirecting the user to where they might sign in.
+> You will need to either reload the current page or redirect the user to the sign in page if you provide this callback.
 
 Read more about `ThirdPartyEmailPasswordAuth` and `onSessionExpired` in [its API reference](/docs/auth-react/docs/thirdpartyemailpassword/third-party-email-password-auth).

thirdpartyemailpassword/docs/common-customizations/sessions/securing-component.md

@@ -1,10 +1,10 @@
 ---
 id: securing-component
-title: Securing component
+title: Securing a website route / component
 hide_title: true
 ---
 
-# Securing a component
+# Securing a website route / component
 You may want to prevent rendering of some part of UI, or a route, when
 there's no session.
 

website/docs/installation.md

@@ -13,13 +13,13 @@ This library provides a wrapper around ```fetch``` or ```axios``` to automatical
 ## Using ```npm```
 
 ```bash
-npm i --save supertokens-website@^8.0.0
+npm i --save supertokens-website@^8.1.0
 ```
 
 
 ## Using ```<script>```
 Put the following anywhere in your ```<head>``` tag
 
 ```html
-<script src="https://cdn.jsdelivr.net/gh/supertokens/supertokens-website@8.0/bundle/bundle.js"></script>
+<script src="https://cdn.jsdelivr.net/gh/supertokens/supertokens-website@8.1/bundle/bundle.js"></script>
 ```