Upgrade

docs/config.md

@@ -86,7 +86,7 @@ For more information, see [Chrome v80 Cookie Behavior and the Impact on MicroStr
 
 ## The Partitioned Cookie Change
 
-Before MicroStrategy 2024 Update 6, when the Library server and the client website are in different domains, the Embedding SDK requires third-party cookies to be allowed to work correctly. In the past, Chrome's default setting was only "Block third-party cookies in Incognito mode", so the customer can use Embedding SDK without changing the Chrome settings.
+Before MicroStrategy ONE June 2024, when the Library server and the client website are in different domains, the Embedding SDK requires third-party cookies to be allowed to work correctly. In the past, Chrome's default setting was only "Block third-party cookies in Incognito mode", so the customer can use Embedding SDK without changing the Chrome settings.
 
 ![The default Chrome preference](./images/chrome-preference.png)
 
@@ -96,4 +96,4 @@ To avoid the changes of third-party cookies default setting breaking the Embeddi
 
 ![The partitioned cookie setting](./images/partitioned-cookie.png)
 
-After this change, the customer can use most of the Embedding SDK functionalities even if 3rd party cookies are blocked in the Chrome preference. But for the SAML/OIDC login, the old workflow changes, and the user need to do more to make it work. The details can be seen in [SAML or OIDC authentication after MicroStrategy 2024 Update 6](./support-for-different-authentication-environments/authentication-saml#for-microstrategy-2024-update-6-or-after).
+After this change, the customer can use most of the Embedding SDK functionalities even if 3rd party cookies are blocked in the Chrome preference. But for the SAML/OIDC login, the old workflow changes, and the user need to do more to make it work. The details can be seen in [SAML or OIDC authentication after MicroStrategy ONE June 2024](./support-for-different-authentication-environments/authentication-saml.md#for-microstrategy-2024-update-6-or-after).

docs/native-embedding-architecture/embed-bot-visualizations.md

@@ -3,7 +3,7 @@ title: Embed multiple bot visualizations on a page
 description: Embed multiple bot visualizations on a page
 ---
 
-<Available since="2024 Update 3"/>
+<Available since="MicroStrategy One March 2024"/>
 
 ## Purpose
 

docs/native-embedding-architecture/mstr-bot-visualization.md

@@ -3,7 +3,7 @@ title: MstrBotVisualization class
 description: MstrBotVisualization class
 ---
 
-<Available since="2024 Update 3"/>
+<Available since="MicroStrategy One March 2024"/>
 
 The object returned from the `MstrBot.renderVisualization()` function, which allows access to the MicroStrategy bot visualization object.
 

docs/native-embedding-architecture/mstr-bot.md

@@ -3,7 +3,7 @@ title: MstrBot class
 description: MstrBot class
 ---
 
-<Available since="2024 Update 3"/>
+<Available since="MicroStrategy One March 2024"/>
 
 The object returned from the `MstrEnvironment.loadBot()` function, which allows access to the MicroStrategy bot object.
 

docs/support-for-different-authentication-environments/authentication-saml.md

@@ -31,9 +31,9 @@ You may encounter some difficulties in this workflow:
   - This might be caused by your strict CSP settings. If your [COOP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy)(Cross-Origin-Opener-Policy) setting is [same-origin](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy#same-origin), the MicroStrategy Library Web login page can't get the Client Application window so can't send messages to it.
   - In this case, you need to change your COOP setting to [unsafe-none](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy#unsafe-none), which is the default value. Then the login process will work.
 
-## For MicroStrategy 2024 Update 6 or after
+## For MicroStrategy ONE June 2024 or after
 
-In MicroStrategy 2024 Update 6, we add the [partitioned cookie change](../config#the-partitioned-cookie-change) to enable the customer to use the Embedding SDK even if third-party cookies are blocked. But if third-party cookies are blocked, the old SAML or OIDC login process can't work.
+In MicroStrategy ONE June 2024, we add the [partitioned cookie change](../config#the-partitioned-cookie-change) to enable the customer to use the Embedding SDK even if third-party cookies are blocked. But if third-party cookies are blocked, the old SAML or OIDC login process can't work.
 
 You can unblock the third-party cookies manually to support the old workflow, but we recommend you use the new [embedding auth APIs](../support-for-different-authentication-environments/new-authentication-apis.md), which can work in the third-party cookies blocked case, and simplify the SAML or OIDC login logic. You can see the examples in the [playground](https://microstrategy.github.io/playground/?example=g17). A simple code piece would be like this:
 

docs/whats-new-in-the-embedding-sdk.md

@@ -5,7 +5,7 @@ description: In each release, changes are made to make the MicroStrategy SDK mor
 
 In each release, changes are made to make the MicroStrategy SDK more powerful and easier to use.
 
-## 2024 Update 6
+## MicroStrategy ONE June 2024
 
 - [Embed MicroStrategy bot consumption page.](./embed-bot-consumption-page/embed-bot-consumption-page.md)
   - Deprecate `botConsumption` object property `snapshot.enabled` to customize UI of the bot consumption page.
@@ -22,7 +22,7 @@ In each release, changes are made to make the MicroStrategy SDK more powerful an
 - [New OAuth APIs for SAML and OIDC login.](./support-for-different-authentication-environments/new-authentication-apis.md)
   - You can call the new APIs to simplify the original SAML or OIDC workflow.
 
-## 2024 Update 3
+## MicroStrategy One March 2024
 
 - Rename 'dossier' into 'dashboard'.
 - [Embed Bot Visualizations with Native Embedding SDK.](./native-embedding-architecture/embed-bot-visualizations.md)