From 4bb5e0f65d19f56895ec18adb1d349f98494b870 Mon Sep 17 00:00:00 2001
From: zhe_mstr <zhe@microstrategy.com>
Date: Tue, 11 Feb 2025 11:52:44 +0800
Subject: [PATCH 1/5] rebrand

---
 CONTRIBUTING.md                               |  20 ++++-----
 LICENSE                                       |   4 +-
 README.md                                     |   2 +-
 contributing/content-style-guide.md           |   6 +--
 .../add-and-remove-datasource-from-project.md |  12 ++---
 ...ng-from-dsn-to-dsnless-for-a-datasource.md |  10 ++---
 .../datasource-management.md                  |   2 +-
 .../delete-a-datasource.md                    |   2 +-
 ...tasource-applicable-advanced-properties.md |   6 +--
 ...get-datasource-with-advanced-properties.md |   2 +-
 .../update-a-datasource.md                    |   6 +--
 .../update-datasource-advanced-property.md    |   2 +-
 .../update-job-priorities-for-datasource.md   |   4 +-
 .../create-and-get-a-subscription.md          |  14 +++---
 .../create-subscription-for-multi-content.md  |   8 ++--
 ...eate-subscription-with-prompted-content.md |  16 +++----
 .../manage-subscriptions.md                   |   2 +-
 .../mobile-subscriptions.md                   |   2 +-
 .../manage-application-general-settings.md    |   2 +-
 .../manage-bookmarks/manage-bookmarks.md      |   2 +-
 .../manage-drivers/manage-drivers.md          |   4 +-
 .../manage-drivers/retrieve-drivers.md        |   2 +-
 .../get-history-list/get-history-list.md      |  16 +++----
 .../manage-history-lists.md                   |   2 +-
 .../license-audit-compliance.md               |   6 +--
 .../manage-licensing/license-manipulation.md  |  20 ++++-----
 .../manage-runtime-objects/manage-runtimes.md |   2 +-
 .../retrieve-all-runtimes.md                  |   2 +-
 .../create-a-migration-package.md             |   4 +-
 .../create-and-import-migration-packages.md   |   4 +-
 .../import-a-migration-package.md             |   4 +-
 .../manage-content-group-packages.md          |   2 +-
 .../view-newly-created-package.md             |   4 +-
 .../view-uploaded-package.md                  |   4 +-
 .../edit-migrations-and-migration-groups.md   |  18 ++++----
 .../migrations-in-workstation.md              |   4 +-
 .../object-migration-between-environments.md  |  18 ++++----
 ...t-migration-groups-between-environments.md |   6 +--
 .../project-merge-between-environments.md     |  24 +++++-----
 .../upload-and-download-migration-packages.md |   8 ++--
 .../validate-migrations.md                    |  16 +++----
 .../manage-an-intelligence-server-cluster.md  |   6 +--
 .../administration/monitors/manage-caches.md  |  12 ++---
 .../monitor-and-manage-cube-caches.md         |  10 ++---
 .../monitors/project-administration.md        |  18 ++++----
 .../manage-fences/create-fence.md             |   8 ++--
 .../manage-fences/delete-specific-fence.md    |   2 +-
 .../manage-fences/manage-fences.md            |   4 +-
 .../manage-fences/retrieve-specific-fence.md  |   2 +-
 .../manage-fences/update-specific-fence.md    |   4 +-
 .../server-management/manage-languages.md     |   2 +-
 .../manage-quick-search-indices.md            |   4 +-
 .../manage-server-settings.md                 |  12 ++---
 .../manage-server-level-privileges.md         |   8 ++--
 .../server-level-privileges.md                |   2 +-
 .../watch-kpi-insight-service-privileges.md   |   2 +-
 .../create-and-update-user-groups.md          |   6 +--
 .../user-management/create-new-users.md       |   6 +--
 .../user-management/create-security-roles.md  |  10 ++---
 .../manage-user-and-user-groups.md            |   2 +-
 .../user-management/manage-users.md           |   6 +--
 .../analytics/export-to-pdf.md                |  14 +++---
 .../analytics/filter-data/filter-data.md      |   4 +-
 .../apply-filters-to-a-dossier.md             |  16 +++----
 .../filter-dossier-instances.md               |   2 +-
 ...-and-cube-instances-using-metric-limits.md |   4 +-
 .../supported-operators.md                    |  32 ++++++-------
 ...-cube-instances-using-requested-objects.md |   4 +-
 ...t-and-cube-instances-using-view-filters.md |   4 +-
 .../general-guidelines.md                     |   2 +-
 .../filter-report-and-cube-instances.md       |   2 +-
 ...ieve-filters-applied-to-a-visualization.md |   2 +-
 .../return-attribute-based-view-filters.md    |   2 +-
 .../return-metric-based-view-filters.md       |   2 +-
 .../return-metric-limit-criteria.md           |   2 +-
 .../return-template-limit-criteria.md         |   4 +-
 .../benefits.md                               |   2 +-
 ...et-incrementally-with-multiple-requests.md |   6 +--
 ...e-and-modify-a-dataset-with-one-request.md |  10 ++---
 .../make-external-data-available.md           |  14 +++---
 .../create-a-cube-object.md                   |   6 +--
 .../manage-cube-objects.md                    |   2 +-
 .../retrieve-a-cube-definition.md             |  18 ++++----
 .../update-a-cube-definition.md               |   6 +--
 .../get-document-list/get-document-list.md    |   4 +-
 .../manage-documents/manage-documents.md      |   2 +-
 .../retrieve-the-hierarchy-of-a-document.md   |   8 ++--
 .../create-instance/create-instance.md        |   2 +-
 .../manage-dossiers/manage-dossiers.md        |   2 +-
 .../analytics/manage-insights/get-kpi.md      |   2 +-
 .../create-an-irr.md                          |   4 +-
 .../manage-incremental-refresh-report.md      |   4 +-
 ...irr-definition-with-advanced-properties.md |   2 +-
 .../retrieve-an-irr-definition.md             |   2 +-
 ...erties-of-an-incremental-refresh-report.md |   6 +--
 .../update-an-irr-definition.md               |   2 +-
 .../manage-page-by-information.md             |   4 +-
 .../create-a-new-report.md                    |   2 +-
 .../manage-report-objects/execute-report.md   |   2 +-
 .../manage-report-objects.md                  |   2 +-
 ...a-derived-elements-definition-in-report.md |   2 +-
 .../retrieve-a-reports-definition.md          |   2 +-
 ...rieve-applicable-properties-of-a-report.md |   6 +--
 ...te-the-definition-of-an-existing-report.md |   2 +-
 .../manage-transaction-report-objects.md      |   4 +-
 .../retrieve-transaction-report-definition.md |   2 +-
 .../manage-selectors/manage-selectors.md      |  16 +++----
 .../data-lineage-analysis-via-rest-apis.md    |   4 +-
 .../object-discovery/folder-browsing.md       |  24 +++++-----
 .../object-discovery/search-for-objects.md    |  14 +++---
 ...project-load-settings-on-server-startup.md |  14 +++---
 .../manage-project-settings.md                |  12 ++---
 ...-project-applicable-advanced-properties.md |   8 ++--
 .../get-project-with-advanced-properties.md   |   8 ++--
 .../project-advanced-properties-management.md |   2 +-
 .../update-project-advanced-property.md       |  12 ++---
 ...ask-question-to-bots-in-the-application.md |   2 +-
 ...ted-question-to-bots-in-the-application.md |   2 +-
 .../get-image-of-answer.md                    |   2 +-
 ...t-question-from-bots-in-the-application.md |   2 +-
 .../question-api.md                           |   2 +-
 ...rieve-data-from-the-intelligence-server.md |   8 ++--
 ...rieve-data-from-the-intelligence-server.md |  42 +++++++++---------
 .../retrieve-dataset-sql.md                   |   4 +-
 .../retrieve-grid-or-graph-query-details.md   |   4 +-
 .../retrieve-report-or-card-sql.md            |   4 +-
 ...trieve-sql-statements-and-query-details.md |   2 +-
 .../retrieve-visualization-query-details.md   |   4 +-
 docs/common-workflows/analytics/sort-data.md  |   6 +--
 .../use-bot-api/ask-bot-instance-question.md  |   4 +-
 .../ask-bot-instance-suggested-question.md    |   4 +-
 .../use-bot-api/create-a-bot-instance.md      |   4 +-
 .../use-bot-api/delete-a-bot-instance.md      |   4 +-
 .../use-bot-api/get-a-bot-question.md         |   4 +-
 .../use-bot-api/get-bot-configuration.md      |   2 +-
 .../use-bot-api/get-bot-question-list.md      |   2 +-
 .../analytics/use-bot-api/use-bot-api.md      |   6 +--
 .../use-prompts-objects/answer-prompts.md     |   2 +-
 .../get-prompt-information.md                 |   4 +-
 .../prompt-types/attribute-element-prompts.md |   2 +-
 .../attribute-qualification-prompts.md        |   2 +-
 .../prompt-types/object-prompts.md            |   2 +-
 .../prompt-types/prompt-types.md              |   4 +-
 .../prompt-types/value-prompts.md             |   2 +-
 .../use-prompts-objects.md                    |   8 ++--
 docs/common-workflows/common-workflows.md     |   8 ++--
 .../change-ownership.md                       |   4 +-
 .../manage-object-acl.md                      |  10 ++---
 .../manage-object-translations.md             |   2 +-
 .../remove-add-object-translations.md         |   2 +-
 .../retrieve-object-translations.md           |   2 +-
 .../update-object-translations.md             |   2 +-
 .../manage-the-schema/lock-the-schema.md      |   4 +-
 .../manage-the-schema/manage-the-schema.md    |   2 +-
 .../reload-the-schema-asynchronously.md       |   4 +-
 .../reload-the-schema-synchronously.md        |   4 +-
 .../retrieve-the-schema-lock.md               |   4 +-
 .../manage-the-schema/unlock-the-schema.md    |   4 +-
 .../create-an-attribute-object.md             |   6 +--
 ...ttribute-applicable-advanced-properties.md |   2 +-
 .../get-attribute-with-advanced-properties.md |   2 +-
 .../manage-attribute-objects.md               |   2 +-
 ...ttributes-definition-within-a-changeset.md |   4 +-
 .../retrieve-an-attributes-definition.md      |   8 ++--
 .../update-an-attributes-definition.md        |   8 ++--
 .../update-attribute-advanced-property.md     |   2 +-
 .../manage-attribute-relationships.md         |   2 +-
 ...ibutes-relationships-within-a-changeset.md |   6 +--
 .../retrieve-an-attributes-relationships.md   |   4 +-
 .../update-an-attributes-relationships.md     |   6 +--
 ...-formulas-definition-within-a-changeset.md |   4 +-
 .../manage-base-formula-objects.md            |   4 +-
 ...-formulas-definition-within-a-changeset.md |   4 +-
 .../retrieve-a-base-formulas-definition.md    |   4 +-
 ...-formulas-definition-within-a-changeset.md |   2 +-
 .../manage-calendar-objects.md                |   2 +-
 .../create-a-consolidation-object.md          |   4 +-
 .../manage-consolidation-objects.md           |   2 +-
 .../retrieve-a-consolidations-definition.md   |   6 +--
 .../update-a-consolidation-object.md          |   4 +-
 ...ilter-elements-using-custom-expressions.md |   4 +-
 .../create-a-custom-group-object.md           |   4 +-
 .../manage-custom-group-objects.md            |   2 +-
 ...om-groups-definition-within-a-changeset.md |   4 +-
 .../retrieve-a-custom-groups-definition.md    |   8 ++--
 .../update-a-custom-groups-definition.md      |   4 +-
 .../execute-a-datamart.md                     |   2 +-
 .../manage-datamart-objects.md                |   4 +-
 .../retrieve-a-datamart-definition.md         |   2 +-
 ...eve-applicable-properties-of-a-datamart.md |   6 +--
 .../create-a-derived-element.md               |   4 +-
 .../manage-derived-element-objects.md         |   2 +-
 .../replace-an-existing-element.md            |   4 +-
 .../retrieve-a-derived-elements-definition.md |   6 +--
 .../manage-dossier-themes.md                  |   2 +-
 .../save-dossier-themes.md                    |   2 +-
 .../manage-drill-maps/create-a-drill-map.md   |   4 +-
 .../manage-drill-maps/manage-drill-maps.md    |   4 +-
 .../retrieve-a-drill-map-definition.md        |   6 +--
 .../retrieve-a-list-of-objects.md             |   2 +-
 .../manage-drill-maps/update-a-drill-map.md   |   4 +-
 .../create-a-fact-object.md                   |   6 +--
 .../manage-fact-objects.md                    |   2 +-
 ...e-a-facts-definition-within-a-changeset.md |   4 +-
 .../retrieve-a-facts-definition.md            |   8 ++--
 .../update-a-fact-object.md                   |   6 +--
 ...-filter-object-with-a-custom-expression.md |   4 +-
 .../create-a-filter-object.md                 |   4 +-
 .../manage-filter-objects.md                  |   2 +-
 ...a-filters-definition-within-a-changeset.md |   4 +-
 .../retrieve-a-filters-definition.md          |   8 ++--
 .../update-a-filters-definition.md            |   4 +-
 .../create-a-metric-within-a-changeset.md     |   2 +-
 .../manage-metric-objects.md                  |  34 +++++++-------
 ...etrieve-a-metrics-applicable-properties.md |   4 +-
 ...a-metrics-definition-within-a-changeset.md |   4 +-
 .../retrieve-a-metrics-definition.md          |   4 +-
 ...a-metrics-definition-within-a-changeset.md |   2 +-
 .../create-a-prompt-within-a-changeset.md     |   6 +--
 .../manage-prompt-objects.md                  |   2 +-
 .../prompt-types/attribute-element-prompts.md |   2 +-
 .../attribute-qualification-prompts.md        |   2 +-
 .../hierarchy-qualification-prompts.md        |   2 +-
 .../prompt-types/metric-expression-prompts.md |   2 +-
 .../prompt-types/object-prompts.md            |   2 +-
 .../prompt-types/prompt-types.md              |   4 +-
 .../prompt-types/value-prompts.md             |   2 +-
 .../retrieve-a-prompts-definition.md          |   4 +-
 ...a-prompts-definition-within-a-changeset.md |   2 +-
 ...filter-object-using-a-custom-expression.md |   2 +-
 .../create-a-security-filter-object.md        |   2 +-
 .../manage-security-filter-objects.md         |   2 +-
 .../modify-a-security-filters-member.md       |   2 +-
 .../retrieve-a-security-filter-definition.md  |  10 ++---
 .../create-a-subtotal-within-a-changeset.md   |   2 +-
 .../manage-subtotal-objects.md                |   4 +-
 ...subtotals-definition-within-a-changeset.md |   4 +-
 .../retrieve-a-subtotals-definition.md        |   4 +-
 .../update-a-subtotal-within-a-changeset.md   |   2 +-
 ...te-a-new-partition-mapping-table-object.md |   2 +-
 .../create-a-new-table-object.md              |   4 +-
 .../manage-table-objects.md                   |   2 +-
 ...list-of-all-available-table-definitions.md |   4 +-
 ...e-a-partition-mapping-tables-definition.md |  10 ++---
 .../retrieve-a-prompt-of-an-sap-hana-table.md |   8 ++--
 .../retrieve-a-tables-definition.md           |   6 +--
 ...e-a-partition-mapping-tables-definition.md |   2 +-
 .../update-a-prompt-of-an-sap-hana-table.md   |   8 ++--
 .../update-a-tables-definition.md             |   4 +-
 ...pdate-a-tables-physical-table-structure.md |   4 +-
 .../update-sap-hana-parameters.md             |   4 +-
 .../create-a-time-zone-object.md              |   2 +-
 .../manage-time-zone-objects.md               |   2 +-
 ...trieve-a-list-of-time-zones-definitions.md |   2 +-
 .../retrieve-a-time-zones-definition.md       |   2 +-
 .../update-a-time-zone-object.md              |   2 +-
 .../create-a-transformation-object.md         |   6 +--
 .../manage-transformation-objects.md          |   2 +-
 .../retrieve-a-transformations-definition.md  |  10 ++---
 .../update-a-transformations-definition.md    |   4 +-
 .../create-a-user-hierarchy.md                |   4 +-
 .../manage-user-hierarchy-objects.md          |   4 +-
 ...ve-a-list-of-available-user-hierarchies.md |   2 +-
 .../retrieve-a-user-hierarchys-definition.md  |   4 +-
 .../update-a-user-hierarchys-definition.md    |   2 +-
 docs/getting-started/authentication.md        |   6 +--
 .../configure-clustered-environments.md       |   6 +--
 docs/getting-started/embedding-sdk.md         |   4 +-
 docs/getting-started/getting-started.md       |   8 ++--
 .../handle-rest-api-exceptions.md             |  12 ++---
 ...r-data-api-v2-result-fetching-endpoints.md |  14 +++---
 ...mance-by-working-with-partial-resources.md |  16 +++----
 .../microstrategy-rest-api-explorer.md        |   8 ++--
 docs/getting-started/playground.md            |  10 ++---
 docs/getting-started/rest-api-architecture.md |   6 +--
 docs/getting-started/rest-api-families.md     |  16 +++----
 docs/index.md                                 |  12 ++---
 .../create-reports-on-the-fly.md              |   6 +--
 .../microstrategy-rest-api-samples.md         |   2 +-
 docs/whats-new.md                             |  30 ++++++-------
 docusaurus.config.js                          |   2 +-
 postman.json                                  |   8 ++--
 scripts/convert_title_to_sentence_case.py     |  10 ++---
 sidebars.js                                   |   2 +-
 src/css/custom.css                            |   4 +-
 static/img/dev-docs-logo.png                  | Bin 21682 -> 10610 bytes
 static/img/favicon.ico                        | Bin 977 -> 15406 bytes
 287 files changed, 788 insertions(+), 788 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d4ff2fe4c..de358aeb7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -10,7 +10,7 @@
   - [Open a pull request](#open-a-pull-request)
   - [Submit your PR & get it reviewed](#submit-your-pr--get-it-reviewed)
   - [Your PR is merged](#your-pr-is-merged)
-  - [Keep contributing as you use MicroStrategy Docs](#keep-contributing-as-you-use-microstrategy-docs)
+  - [Keep contributing as you use Strategy Docs](#keep-contributing-as-you-use-strategy-docs)
 
 ## Getting started
 
@@ -44,7 +44,7 @@ Fork using GitHub Desktop:
 
 ### Make your update
 
-Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-microstrategyrest-api-docs-repository).
+Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-strategyrest-api-docs-repository).
 
 - Are you making changes to the application code? You'll need **Node.js v16** to run the site locally. See [contributing/development.md](contributing/development.md).
 - Are you contributing to markdown? We use [Markdown](https://www.markdownguide.org/basic-syntax/).
@@ -60,13 +60,13 @@ When you're done making changes and you'd like to propose them for review, use t
 
 ### Your PR is merged
 
-Congratulations! The whole MicroStrategy community thanks you. :sparkles:
+Congratulations! The whole Strategy community thanks you. :sparkles:
 
 Once your PR is merged, you will be proudly listed as a contributor in the [contributor chart](https://github.com/MicroStrategy/rest-api-docs/graphs/contributors) and at the bottom of the page you contributed to.
 
-### Keep contributing as you use MicroStrategy Docs
+### Keep contributing as you use Strategy Docs
 
-Now that you're a part of the MicroStrategy Docs community, you can keep participating in many ways.
+Now that you're a part of the Strategy Docs community, you can keep participating in many ways.
 
 **Learn more about contributing:**
 
@@ -77,7 +77,7 @@ Now that you're a part of the MicroStrategy Docs community, you can keep partici
   - [:earth_asia: Translations](#earth_asia-translations)
 - [Starting with an issue](#starting-with-an-issue)
 - [Opening a pull request](#opening-a-pull-request)
-- [Working in the MicroStrategy/rest-api-docs repository](#working-in-the-microstrategyrest-api-docs-repository)
+- [Working in the Strategy/rest-api-docs repository](#working-in-the-strategyrest-api-docs-repository)
 - [Reviewing](#reviewing)
   - [Self review](#self-review)
   - [Test it locally](#test-it-locally)
@@ -87,7 +87,7 @@ Now that you're a part of the MicroStrategy Docs community, you can keep partici
 
 ## :memo: Types of contributions
 
-You can contribute to the REST API Docs content and site in several ways. This repo is a place to discuss and collaborate on MicroStrategy REST API Docs! Our small, but mighty :muscle: docs team is maintaining this repo, to preserve our bandwidth, off topic conversations will be closed.
+You can contribute to the REST API Docs content and site in several ways. This repo is a place to discuss and collaborate on Strategy REST API Docs! Our small, but mighty :muscle: docs team is maintaining this repo, to preserve our bandwidth, off topic conversations will be closed.
 
 ### :beetle: Issues
 
@@ -101,7 +101,7 @@ When we merge those changes, they should be deployed to the live site within 24
 
 ### :question: Support
 
-We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with MicroStrategy, unrelated to our documentation, please [contact MicroStrategy Support directly](https://www.microstrategy.com/support). Any issues, or pull requests opened here requesting support will be given information about how to contact MicroStrategy Support, then closed and locked.
+We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with Strategy, unrelated to our documentation, please [contact Strategy Support directly](https://www.microstrategy.com/support). Any issues, or pull requests opened here requesting support will be given information about how to contact Strategy Support, then closed and locked.
 
 ### :earth_asia: Translations
 
@@ -117,7 +117,7 @@ You can browse existing issues to find something that needs help!
 
 You can use the GitHub user interface :pencil2: for some small changes, like fixing a typo or updating a readme. You can also fork the repo and then clone it locally, to view changes and run your tests on your machine.
 
-## Working in the MicroStrategy/rest-api-docs repository
+## Working in the Strategy/rest-api-docs repository
 
 Here's some information that might be helpful while working on a Docs PR:
 
@@ -126,7 +126,7 @@ Here's some information that might be helpful while working on a Docs PR:
 
 ## Reviewing
 
-We (usually the docs team, but sometimes MicroStrategy product managers, engineers, or supportocats too!) review every single PR. The purpose of reviews is to create the best content we can for people who use MicroStrategy.
+We (usually the docs team, but sometimes Strategy product managers, engineers, or supportocats too!) review every single PR. The purpose of reviews is to create the best content we can for people who use Strategy.
 
 :yellow_heart: Reviews are always respectful, acknowledging that everyone did the best possible job with the knowledge they had at the time.
 
diff --git a/LICENSE b/LICENSE
index 3156bafaa..f8c2a2c05 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,4 +1,4 @@
-Copyright 2023, MicroStrategy Incorporated. All rights reserved.
+Copyright 2023, Strategy Incorporated. All rights reserved.
 
                                  Apache License
                            Version 2.0, January 2004
@@ -188,7 +188,7 @@ Copyright 2023, MicroStrategy Incorporated. All rights reserved.
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2023, MicroStrategy Incorporated.
+   Copyright 2023, Strategy Incorporated.
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
diff --git a/README.md b/README.md
index 978e0655a..1d0ce72e8 100644
--- a/README.md
+++ b/README.md
@@ -61,7 +61,7 @@ pull request. For more details about this process, please check out
 
 #### And that's it
 
-That's how you can get started easily as a member of the MicroStrategy Embedding SDK Documentation
+That's how you can get started easily as a member of the Strategy Embedding SDK Documentation
 community. :sparkles:
 
 If you want to know more, or you're making a more complex contribution, check out
diff --git a/contributing/content-style-guide.md b/contributing/content-style-guide.md
index 48bb9197d..ebad5abc5 100644
--- a/contributing/content-style-guide.md
+++ b/contributing/content-style-guide.md
@@ -135,7 +135,7 @@ The list below shows the usage of emojis in our Docs site:
 
 - Titles, sidebar labels, and headers
 
-  - These should use **sentence case**. For example, prefer "This is the title from MicroStrategy" over "This Is The Title From MicroStrategy".
+  - These should use **sentence case**. For example, prefer "This is the title from Strategy" over "This Is The Title From Strategy".
   - `sidebar_label` should only be used if you want a different title in the sidebar than the `title` in front matter. (Note: For folders, `label` in sidebars.js takes priority over `sidebar_label`)
 
 ## Tables
@@ -209,7 +209,7 @@ For the root of a collection of workflows, please use the template below:
 
 You can try these workflows with [REST API Playground]().
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 ```
@@ -221,7 +221,7 @@ For the workflow page, please use the template below:
 
 You can try out this workflow at [REST API Playground]().
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 ```
diff --git a/docs/common-workflows/administration/datasource-management/add-and-remove-datasource-from-project.md b/docs/common-workflows/administration/datasource-management/add-and-remove-datasource-from-project.md
index 7c6a133e7..72857332a 100644
--- a/docs/common-workflows/administration/datasource-management/add-and-remove-datasource-from-project.md
+++ b/docs/common-workflows/administration/datasource-management/add-and-remove-datasource-from-project.md
@@ -8,13 +8,13 @@ This workflow sample demonstrates how to add a datasource to a project. To see h
 1. [Get list of datasources based on project.](#get-list-of-datasources-based-on-project) `GET /api/projects/{projectId}/datasources`
 1. [Add a datasource to a project.](#add-datasource-to-project) `PATCH /api/projects/{projectId}/datasources`
 
-A detailed description of each step of this request is listed down below. For this sample we are using the MicroStrategy Tutorial project with project ID B7CA92F04B9FAE8D941C3E9B7E0CD754. You can obtain the project ID from `GET /api/projects`.
+A detailed description of each step of this request is listed down below. For this sample we are using the Strategy Tutorial project with project ID B7CA92F04B9FAE8D941C3E9B7E0CD754. You can obtain the project ID from `GET /api/projects`.
 
 ## Get list of datasources based on project
 
 Endpoint: [GET /api/projects/\{projectId}/datasources](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/getProjectDatasources)
 
-This endpoint allows the caller to get the datasources associated with a specific project with the MicroStrategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing the datasources for a project.
+This endpoint allows the caller to get the datasources associated with a specific project with the Strategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing the datasources for a project.
 
 Sample Request
 
@@ -114,13 +114,13 @@ Sample Response
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2d0b3eac-9704-42a7-9481-fec12557b752?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 Endpoint: [PATCH /api/projects/\{projectId}/datasources](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/updateProjectDatasources)
 
-This endpoint allows the caller to add and remove a datasource to a specific project with the MicroStrategy REST Server. In this request we will add a datasource. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. For this sample we will be adding the Act! Essentials datasource to the MicroStrategy Tutorial project. You can find the datasourceId using the endpoint `GET /api/datasources` and the projectId using `GET /api/projects`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the project's datasources.
+This endpoint allows the caller to add and remove a datasource to a specific project with the Strategy REST Server. In this request we will add a datasource. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. For this sample we will be adding the Act! Essentials datasource to the Strategy Tutorial project. You can find the datasourceId using the endpoint `GET /api/datasources` and the projectId using `GET /api/projects`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the project's datasources.
 
 Sample Request
 
@@ -242,13 +242,13 @@ Sample Response Code: 200 (Add datasource to project.)
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-577baae8-f1b6-4ed2-8819-bc3aed5ec5c7?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 Endpoint: [PATCH /api/projects/\{projectId}/datasources](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/updateProjectDatasources)
 
-This endpoint allows the caller to add and remove a datasource to a specific project with the MicroStrategy REST Server. In this request we will remove a datasource. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. For this sample we will be removing the Act! Essentials datasource from the MicroStrategy Tutorial project. You can find the datasourceId using the endpoint `GET /api/datasources` and the projectId using `GET /api/projects`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the project's datasources.
+This endpoint allows the caller to add and remove a datasource to a specific project with the Strategy REST Server. In this request we will remove a datasource. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. For this sample we will be removing the Act! Essentials datasource from the Strategy Tutorial project. You can find the datasourceId using the endpoint `GET /api/datasources` and the projectId using `GET /api/projects`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the project's datasources.
 
 Sample Request
 
diff --git a/docs/common-workflows/administration/datasource-management/convert-connection-string-from-dsn-to-dsnless-for-a-datasource.md b/docs/common-workflows/administration/datasource-management/convert-connection-string-from-dsn-to-dsnless-for-a-datasource.md
index 818439a24..d76880e3c 100644
--- a/docs/common-workflows/administration/datasource-management/convert-connection-string-from-dsn-to-dsnless-for-a-datasource.md
+++ b/docs/common-workflows/administration/datasource-management/convert-connection-string-from-dsn-to-dsnless-for-a-datasource.md
@@ -9,7 +9,7 @@ description: This workflow sample demonstrates how to convert connection string
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-737e03ad-a41a-46d5-bf7a-00e68963b08b?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -141,7 +141,7 @@ Sample Response
 After conversion, you should be able to see the DSN-less format connection string in the response by calling the API to get the datasource definition.
 
 ```json
-"connectionString": "DRIVER={MicroStrategy ODBC Driver for PostgreSQL Wire Protocol};APPLICATIONUSINGTHREADS=1;DATABASE=test;DEFAULTLONGDATABUFFLEN=1024;DESCRIPTION=MicroStrategy ODBC Driver for PostgreSQL Wire Protocol;ENABLEDESCRIBEPARAM=1;ENCRYPTIONMETHOD=1;FETCHTSWTZASTIMESTAMP=1;FETCHTWFSASTIME=1;HOSTNAME=xx.xx.xx.xx;HOSTNAMEINCERTIFICATE=xx.xx.xx.xx;PORTNUMBER=5432;TRANSACTIONERRORBEHAVIOR=0;UID=uid;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;"
+"connectionString": "DRIVER={Strategy ODBC Driver for PostgreSQL Wire Protocol};APPLICATIONUSINGTHREADS=1;DATABASE=test;DEFAULTLONGDATABUFFLEN=1024;DESCRIPTION=Strategy ODBC Driver for PostgreSQL Wire Protocol;ENABLEDESCRIBEPARAM=1;ENCRYPTIONMETHOD=1;FETCHTSWTZASTIMESTAMP=1;FETCHTWFSASTIME=1;HOSTNAME=xx.xx.xx.xx;HOSTNAMEINCERTIFICATE=xx.xx.xx.xx;PORTNUMBER=5432;TRANSACTIONERRORBEHAVIOR=0;UID=uid;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;"
 ```
 
 Sample Request
@@ -188,7 +188,7 @@ Sample Response
         "charEncodingWindows": "multibyte",
         "charEncodingUnix": "utf8",
         "tablePrefix": "",
-        "connectionString": "DRIVER={MicroStrategy ODBC Driver for PostgreSQL Wire Protocol};APPLICATIONUSINGTHREADS=1;DATABASE=test;DEFAULTLONGDATABUFFLEN=1024;DESCRIPTION=MicroStrategy ODBC Driver for PostgreSQL Wire Protocol;ENABLEDESCRIBEPARAM=1;ENCRYPTIONMETHOD=1;FETCHTSWTZASTIMESTAMP=1;FETCHTWFSASTIME=1;HOSTNAME=xx.xx.xx.xx;HOSTNAMEINCERTIFICATE=xx.xx.xx.xx;PORTNUMBER=5432;TRANSACTIONERRORBEHAVIOR=0;UID=uid;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;",
+        "connectionString": "DRIVER={Strategy ODBC Driver for PostgreSQL Wire Protocol};APPLICATIONUSINGTHREADS=1;DATABASE=test;DEFAULTLONGDATABUFFLEN=1024;DESCRIPTION=Strategy ODBC Driver for PostgreSQL Wire Protocol;ENABLEDESCRIBEPARAM=1;ENCRYPTIONMETHOD=1;FETCHTSWTZASTIMESTAMP=1;FETCHTWFSASTIME=1;HOSTNAME=xx.xx.xx.xx;HOSTNAMEINCERTIFICATE=xx.xx.xx.xx;PORTNUMBER=5432;TRANSACTIONERRORBEHAVIOR=0;UID=uid;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;",
         "parameterizedQueries": false,
         "extendedFetch": false,
         "login": {
@@ -315,7 +315,7 @@ Sample Response
 After conversion, you should be able to see the DSN-less format connection string in the response by calling the API to get the datasource connection definition.
 
 ```json
-"connectionString": "DRIVER={MicroStrategy ODBC Driver for SQL Server Wire Protocol};DATABASE=tpch;HOSTNAME=10.27.69.102;KEEPALIVE=0;KEEPCONNECTIONACTIVE=0;LOADBALANCETIMEOUT=0;LOADBALANCING=0;LOGINTIMEOUT=15;MAXPOOLSIZE=100;MINPOOLSIZE=0;MULTISUBNETFAILOVER=0 - FALSE;PORTNUMBER=1433;PROXYMODE=0;QUERYTIMEOUT=0;REPORTCODEPAGECONVERSIONERRORS=0;SNAPSHOTSERIALIZABLE=0;SOCKETIDLETIMECHECKINTERVAL=1500;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;"
+"connectionString": "DRIVER={Strategy ODBC Driver for SQL Server Wire Protocol};DATABASE=tpch;HOSTNAME=10.27.69.102;KEEPALIVE=0;KEEPCONNECTIONACTIVE=0;LOADBALANCETIMEOUT=0;LOADBALANCING=0;LOGINTIMEOUT=15;MAXPOOLSIZE=100;MINPOOLSIZE=0;MULTISUBNETFAILOVER=0 - FALSE;PORTNUMBER=1433;PROXYMODE=0;QUERYTIMEOUT=0;REPORTCODEPAGECONVERSIONERRORS=0;SNAPSHOTSERIALIZABLE=0;SOCKETIDLETIMECHECKINTERVAL=1500;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;"
 ```
 
 Sample Request
@@ -346,7 +346,7 @@ Sample Response
     "charEncodingWindows": "multibyte",
     "charEncodingUnix": "utf8",
     "tablePrefix": "",
-    "connectionString": "DRIVER={MicroStrategy ODBC Driver for SQL Server Wire Protocol};DATABASE=tpch;HOSTNAME=10.27.69.102;KEEPALIVE=0;KEEPCONNECTIONACTIVE=0;LOADBALANCETIMEOUT=0;LOADBALANCING=0;LOGINTIMEOUT=15;MAXPOOLSIZE=100;MINPOOLSIZE=0;MULTISUBNETFAILOVER=0 - FALSE;PORTNUMBER=1433;PROXYMODE=0;QUERYTIMEOUT=0;REPORTCODEPAGECONVERSIONERRORS=0;SNAPSHOTSERIALIZABLE=0;SOCKETIDLETIMECHECKINTERVAL=1500;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;",
+    "connectionString": "DRIVER={Strategy ODBC Driver for SQL Server Wire Protocol};DATABASE=tpch;HOSTNAME=10.27.69.102;KEEPALIVE=0;KEEPCONNECTIONACTIVE=0;LOADBALANCETIMEOUT=0;LOADBALANCING=0;LOGINTIMEOUT=15;MAXPOOLSIZE=100;MINPOOLSIZE=0;MULTISUBNETFAILOVER=0 - FALSE;PORTNUMBER=1433;PROXYMODE=0;QUERYTIMEOUT=0;REPORTCODEPAGECONVERSIONERRORS=0;SNAPSHOTSERIALIZABLE=0;SOCKETIDLETIMECHECKINTERVAL=1500;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;",
     "parameterizedQueries": true,
     "extendedFetch": false,
     "database": {
diff --git a/docs/common-workflows/administration/datasource-management/datasource-management.md b/docs/common-workflows/administration/datasource-management/datasource-management.md
index 3aaf68dca..1ed91b91c 100644
--- a/docs/common-workflows/administration/datasource-management/datasource-management.md
+++ b/docs/common-workflows/administration/datasource-management/datasource-management.md
@@ -7,7 +7,7 @@ description: You can use REST API requests to manage datasources.
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-fe63e329-ca17-40e6-9263-8f451b95e06e?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/datasource-management/delete-a-datasource.md b/docs/common-workflows/administration/datasource-management/delete-a-datasource.md
index 977584933..111d431ae 100644
--- a/docs/common-workflows/administration/datasource-management/delete-a-datasource.md
+++ b/docs/common-workflows/administration/datasource-management/delete-a-datasource.md
@@ -13,7 +13,7 @@ The workflow for deleting and cleaning up a datasource includes the following se
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2da893be-a6e9-449a-95ae-749b5906bb27?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/datasource-management/get-datasource-applicable-advanced-properties.md b/docs/common-workflows/administration/datasource-management/get-datasource-applicable-advanced-properties.md
index c26b305f2..346ed4a10 100644
--- a/docs/common-workflows/administration/datasource-management/get-datasource-applicable-advanced-properties.md
+++ b/docs/common-workflows/administration/datasource-management/get-datasource-applicable-advanced-properties.md
@@ -10,7 +10,7 @@ description: Get applicable properties for a datasource.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-585d42d1-fbdc-4d1d-afbb-c4e872753709?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -65,8 +65,8 @@ You can view the applicable properties in the body of the response.
       "showSqlPreview": true,
       "options": [
         {
-          "value": "Choosing this option keeps the backward compatibility with MicroStrategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
-          "sqlPreview": "OBSOLETE - Keep backward compatibility with MicroStrategy 2019."
+          "value": "Choosing this option keeps the backward compatibility with Strategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
+          "sqlPreview": "OBSOLETE - Keep backward compatibility with Strategy 2019."
         },
         {
           "value": "Cancel execution of cartesian join for SQL, MDX, In-Memory queries.",
diff --git a/docs/common-workflows/administration/datasource-management/get-datasource-with-advanced-properties.md b/docs/common-workflows/administration/datasource-management/get-datasource-with-advanced-properties.md
index 913ba4c15..ffb415774 100644
--- a/docs/common-workflows/administration/datasource-management/get-datasource-with-advanced-properties.md
+++ b/docs/common-workflows/administration/datasource-management/get-datasource-with-advanced-properties.md
@@ -9,7 +9,7 @@ description: The workflow involves getting datasource definition along with its
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c8ec1165-e5d3-4b9a-bc68-df3d71d493f7?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/datasource-management/update-a-datasource.md b/docs/common-workflows/administration/datasource-management/update-a-datasource.md
index e9dde0ebf..bab29a98b 100644
--- a/docs/common-workflows/administration/datasource-management/update-a-datasource.md
+++ b/docs/common-workflows/administration/datasource-management/update-a-datasource.md
@@ -15,7 +15,7 @@ A detailed description of each step of this request is listed down below.
 
 Endpoint: [PATCH /api/datasources/\{datasourceId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/updateDatasource)
 
-This endpoint allows the caller to update a database source with the MicroStrategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the datasourceId using the endpoint `GET /api/datasources`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a info for the updated database source.
+This endpoint allows the caller to update a database source with the Strategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the datasourceId using the endpoint `GET /api/datasources`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a info for the updated database source.
 
 Sample Request
 
@@ -100,7 +100,7 @@ Sample Response
 
 Endpoint: [PATCH /api/datasources/connections/\{connectionId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/updateDatasourceConnection)
 
-This endpoint allows the caller to update a datasource connection with the MicroStrategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the connectionId using the endpoint `GET /api/datasources/connections`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing info for the updated datasource connection.
+This endpoint allows the caller to update a datasource connection with the Strategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the connectionId using the endpoint `GET /api/datasources/connections`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing info for the updated datasource connection.
 
 Sample Request
 
@@ -183,7 +183,7 @@ Sample Response
 
 Endpoint: [PATCH /api/datasources/logins/\{loginId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/updateDatasourceLogin)
 
-This endpoint allows the caller to update a datasource login with the MicroStrategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the loginId using the endpoint `GET /api/datasources/logins`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing info for the updated datasource login.
+This endpoint allows the caller to update a datasource login with the Strategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the loginId using the endpoint `GET /api/datasources/logins`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing info for the updated datasource login.
 
 Sample Request
 
diff --git a/docs/common-workflows/administration/datasource-management/update-datasource-advanced-property.md b/docs/common-workflows/administration/datasource-management/update-datasource-advanced-property.md
index 3b6342b76..19035aeec 100644
--- a/docs/common-workflows/administration/datasource-management/update-datasource-advanced-property.md
+++ b/docs/common-workflows/administration/datasource-management/update-datasource-advanced-property.md
@@ -9,7 +9,7 @@ description: The workflow involves modifying datasource's advanced properties va
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-689ad52e-2dee-4582-92a1-679dc0fda692?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/datasource-management/update-job-priorities-for-datasource.md b/docs/common-workflows/administration/datasource-management/update-job-priorities-for-datasource.md
index 8a84cdd63..e7da69462 100644
--- a/docs/common-workflows/administration/datasource-management/update-job-priorities-for-datasource.md
+++ b/docs/common-workflows/administration/datasource-management/update-job-priorities-for-datasource.md
@@ -14,7 +14,7 @@ A detailed description of each step of this request is listed down below.
 
 Endpoint: [GET /api/datasources/\{datasourceId}/jobPriorities](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/getJobPrioritization)
 
-This endpoint allows the caller to get job prioritization info for a specific database source with the MicroStrategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the datasourceId using the endpoint `GET /api/datasources`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing info regarding the job priorities for the datasource.
+This endpoint allows the caller to get job prioritization info for a specific database source with the Strategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the datasourceId using the endpoint `GET /api/datasources`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing info regarding the job priorities for the datasource.
 
 Sample Request
 
@@ -99,7 +99,7 @@ Sample Response
 
 Endpoint: [PATCH /api/datasources/\{datasourceId}/jobPriorities](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/updateJobPrioritization)
 
-This endpoint allows the caller to update job prioritization info for a specific database source with the MicroStrategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the datasourceId using the endpoint `GET /api/datasources`. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a empty response body.
+This endpoint allows the caller to update job prioritization info for a specific database source with the Strategy REST Server. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. You can find the datasourceId using the endpoint `GET /api/datasources`. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a empty response body.
 
 Sample Request
 
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
index 502c6bee0..7a7735ba4 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to retrieve a subscription, a
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-da43d1b1-a332-4452-829f-e07a041abc8f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -32,7 +32,7 @@ A detailed description of each step of this workflow is listed down below.
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
 
 Sample Request
 
@@ -88,7 +88,7 @@ The authorization token "`x-mstr-authtoken`" is returned in the response header.
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the MicroStrategy REST Server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 Sample Request
 
@@ -115,9 +115,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "alias": "",
-      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -321,7 +321,7 @@ Sample Request
 
   ```bash
   curl -X GET -b ~/cookie-jar.txt --header 'Accept: application/json'
-  --header 'X-MSTR-AuthToken: lb15fie86urdnsldk71a02gls2' https://demo.microstrategy.com/MicroStrategyLibrary/api/users?nameBegins=MicroStrategy Web User&fields=name,id
+  --header 'X-MSTR-AuthToken: lb15fie86urdnsldk71a02gls2' https://demo.microstrategy.com/MicroStrategyLibrary/api/users?nameBegins=Strategy Web User&fields=name,id
   ```
 
 Sample Response
@@ -332,7 +332,7 @@ Sample Response
   [
     {
       "id": "C1E141E611D603A2100086B3A5E8F8A4",
-      "name": "MicroStrategy Web User"
+      "name": "Strategy Web User"
     }
   ]
   ```
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
index 1722fe212..7c6382a69 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to create email subscriptions
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-b83f6f30-6232-4e88-9d90-aee4837da5e7?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ This workflow sample demonstrates how to create email subscriptions with multipl
 1. [Create multi-content subscription.](#create-a-multi-content-subscription)
 1. [Delete subscription.](#delete-the-subscription)
 
-A detailed description of the critical steps in this workflow are listed down below. For a full list of API calls in the workflow, you can look at the workflow in the MicroStrategy POSTMAN collection.
+A detailed description of the critical steps in this workflow are listed down below. For a full list of API calls in the workflow, you can look at the workflow in the Strategy POSTMAN collection.
 
 ## Get a list of available schedules
 
@@ -147,7 +147,7 @@ Sample Response
         "name": "Shared Drive",
         "deliveryMode": "EMAIL",
         "deviceId": "18F9613B681E4E4FA671D1AED6B7B375",
-        "value": "C:\\Program Files\\MicroStrategy\\Analytics Modules",
+        "value": "C:\\Program Files\\Strategy\\Analytics Modules",
         "isDefault": true
       }
     ]
@@ -358,7 +358,7 @@ Sample Response
     "recipients": [
       {
         "id": "C1E141E611D603A2100086B3A5E8F8A4",
-        "name": "MicroStrategy Web User",
+        "name": "Strategy Web User",
         "isGroup": false,
         "type": "user",
         "includeType": "TO",
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
index f580739bb..1b2868828 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to create a prompted subscrip
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-4fce986e-f37b-4fb8-94ff-b0978d1ef849?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -30,7 +30,7 @@ A detailed description of each step of this workflow is listed down below.
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
 
 Sample Request
 
@@ -86,7 +86,7 @@ The authorization token "`x-mstr-authtoken`" is returned in the response header.
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the MicroStrategy REST Server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 Sample Request
 
@@ -113,9 +113,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "alias": "",
-      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -159,7 +159,7 @@ Sample Request
 
   ```bash
   curl -X GET -b ~/cookie-jar.txt --header 'Accept: application/json'
-  --header 'X-MSTR-AuthToken: {AuthToken}' https://demo.microstrategy.com/MicroStrategyLibrary/api/users?nameBegins=MicroStrategy Web User&fields=name,id
+  --header 'X-MSTR-AuthToken: {AuthToken}' https://demo.microstrategy.com/MicroStrategyLibrary/api/users?nameBegins=Strategy Web User&fields=name,id
   ```
 
 Sample Response
@@ -170,7 +170,7 @@ Sample Response
   [
     {
       "id": "",
-      "name": "MicroStrategy Web User"
+      "name": "Strategy Web User"
     }
   ]
   ```
@@ -236,7 +236,7 @@ Sample Response
         "name": "Shared Drive",
         "deliveryMode": "EMAIL",
         "deviceId": "18F9613B681E4E4FA671D1AED6B7B375",
-        "value": "C:\\Program Files\\MicroStrategy\\Analytics Modules",
+        "value": "C:\\Program Files\\Strategy\\Analytics Modules",
         "isDefault": true
       }
     ]
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/manage-subscriptions.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/manage-subscriptions.md
index 4c85d3adc..94d144d57 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/manage-subscriptions.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/manage-subscriptions.md
@@ -7,7 +7,7 @@ description: You can use REST API requests to retrieve and create different type
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-73ce0581-5c01-4d8f-8e4b-a1c53c6e59b1?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/mobile-subscriptions.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/mobile-subscriptions.md
index 793b6ba79..007909384 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/mobile-subscriptions.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/mobile-subscriptions.md
@@ -14,7 +14,7 @@ This workflow sample demonstrates how to create and update a mobile subscription
 
 This workflow follows the general steps described in [Create and get a subscription](create-and-get-a-subscription.md). You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-da43d1b1-a332-4452-829f-e07a041abc8f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/manage-application-objects/manage-application-general-settings.md b/docs/common-workflows/administration/manage-application-objects/manage-application-general-settings.md
index b4c3b8893..e29187231 100644
--- a/docs/common-workflows/administration/manage-application-objects/manage-application-general-settings.md
+++ b/docs/common-workflows/administration/manage-application-objects/manage-application-general-settings.md
@@ -891,7 +891,7 @@ Sample Response Body:
         "showMobileButton": true,
         "showReminder": true,
         "showSentBy": true,
-        "sentByText": "MicroStrategy Inc.",
+        "sentByText": "Strategy Inc.",
         "showSocialMedia": true
       }
     }
diff --git a/docs/common-workflows/administration/manage-bookmarks/manage-bookmarks.md b/docs/common-workflows/administration/manage-bookmarks/manage-bookmarks.md
index 0418b3a4e..9a958629c 100644
--- a/docs/common-workflows/administration/manage-bookmarks/manage-bookmarks.md
+++ b/docs/common-workflows/administration/manage-bookmarks/manage-bookmarks.md
@@ -1,6 +1,6 @@
 ---
 title: Manage Bookmarks
-Description: Manage bookmarks using the MicroStrategy REST API.
+Description: Manage bookmarks using the Strategy REST API.
 ---
 
 You can use REST API requests to manage bookmarks:
diff --git a/docs/common-workflows/administration/manage-drivers/manage-drivers.md b/docs/common-workflows/administration/manage-drivers/manage-drivers.md
index 12cdbf0ba..5322a3a2e 100644
--- a/docs/common-workflows/administration/manage-drivers/manage-drivers.md
+++ b/docs/common-workflows/administration/manage-drivers/manage-drivers.md
@@ -1,6 +1,6 @@
 ---
 title: Manage drivers
-description: Driver is a new object type added since MicroStrategy 2021 Update 8. This page contains a summary of REST APIs of "drivers" endpoint. You can use REST API requests to retrieve a driver's definition or retrieve a list of drivers' definitions or update a driver's definition.
+description: Driver is a new object type added since Strategy 2021 Update 8. This page contains a summary of REST APIs of "drivers" endpoint. You can use REST API requests to retrieve a driver's definition or retrieve a list of drivers' definitions or update a driver's definition.
 ---
 
 <Available since="2021 Update 9" />
@@ -11,7 +11,7 @@ The feature flag "Disable or enable gateways and drivers" should be turned on. T
 
 :::
 
-Driver is a new object type added since MicroStrategy 2021 Update 8. Each driver object is corresponding to a physical driver (used to fetch data from data sources) installed in IServer. By changing the "enabled" status of a driver object, customer can control whehter to block usage of corresponding physical driver or not.
+Driver is a new object type added since Strategy 2021 Update 8. Each driver object is corresponding to a physical driver (used to fetch data from data sources) installed in IServer. By changing the "enabled" status of a driver object, customer can control whehter to block usage of corresponding physical driver or not.
 
 This page contains a summary of REST APIs of "drivers" endpoint. You can use REST API requests to retrieve a driver's definition or retrieve a list of drivers' definitions or update a driver's definition.
 
diff --git a/docs/common-workflows/administration/manage-drivers/retrieve-drivers.md b/docs/common-workflows/administration/manage-drivers/retrieve-drivers.md
index d8cf83088..69f7e687a 100644
--- a/docs/common-workflows/administration/manage-drivers/retrieve-drivers.md
+++ b/docs/common-workflows/administration/manage-drivers/retrieve-drivers.md
@@ -57,7 +57,7 @@ You can get all the driver objects in the body of the response.
       "enabled": true,
       "id": "43A6758EF9CE9BBB12AD13C2636B162D",
       "isODBC": true,
-      "name": "MicroStrategy ODBC Driver for SQL Server Wire Protocol"
+      "name": "Strategy ODBC Driver for SQL Server Wire Protocol"
     }
   }
 }
diff --git a/docs/common-workflows/administration/manage-history-lists/get-history-list/get-history-list.md b/docs/common-workflows/administration/manage-history-lists/get-history-list/get-history-list.md
index 05185fde6..2590bb542 100644
--- a/docs/common-workflows/administration/manage-history-lists/get-history-list/get-history-list.md
+++ b/docs/common-workflows/administration/manage-history-lists/get-history-list/get-history-list.md
@@ -1,11 +1,11 @@
 ---
 title: Retrieve history lists
-Description: Retrieve history lists using the MicroStrategy REST API.
+Description: Retrieve history lists using the Strategy REST API.
 ---
 
 <Available since="2021 Update 8" />
 
-This workflow sample demonstrates how to retrieve messages from the history list using the MicroStrategy REST API.
+This workflow sample demonstrates how to retrieve messages from the history list using the Strategy REST API.
 
 :::info
 
@@ -72,7 +72,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
       "status": "reserved",
       "sequenceNumber": 10,
       "parentId": "00000000000000000000000000000000",
-      "clientType": "MicroStrategyWeb",
+      "clientType": "StrategyWeb",
       "requestType": "document",
       "requestStatus": "job_running",
       "startTime": "2022-06-30T06:10:50Z",
@@ -88,7 +88,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
         "folderName": "HLCodeCoverage"
       },
       "projectId": "9DE876B611E7C33BF65B0080EF45D3E8",
-      "projectName": "MicroStrategy Tutorial",
+      "projectName": "Strategy Tutorial",
       "resultFlags": 0,
       "cacheId": null,
       "messageText": "User request is completed.",
@@ -108,7 +108,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
           "status": "new_message",
           "sequenceNumber": 11,
           "parentId": "0A6B683C4AF5FECC365F4CA18C11710A",
-          "clientType": "MicroStrategyWeb",
+          "clientType": "StrategyWeb",
           "requestType": "report",
           "requestStatus": 1,
           "startTime": "2022-06-30T06:10:51Z",
@@ -123,7 +123,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
             "folderId": "D6253070472AA691A4E9C88E72B7AC64",
             "folderName": "HLCodeCoverage"
           },
-          "projectName": "MicroStrategy Tutorial",
+          "projectName": "Strategy Tutorial",
           "resultFlags": "dtls_expr_nothing",
           "messageText": "User request is completed.",
           "displayName": "1.NormalReport",
@@ -143,7 +143,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
       "status": "new_message",
       "sequenceNumber": 9,
       "parentId": "00000000000000000000000000000000",
-      "clientType": "MicroStrategyWeb",
+      "clientType": "StrategyWeb",
       "requestType": "report",
       "requestStatus": "loading_prompt",
       "startTime": "2022-07-30T06:10:51Z",
@@ -159,7 +159,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
         "folderName": "_Chun"
       },
       "projectId": "9DE876B611E7C33BF65B0080EF45D3E8",
-      "projectName": "MicroStrategy Tutorial",
+      "projectName": "Strategy Tutorial",
       "resultFlags": "dtls_expr_nothing",
       "messageText": "User request is completed.",
       "displayName": "3Ms",
diff --git a/docs/common-workflows/administration/manage-history-lists/manage-history-lists.md b/docs/common-workflows/administration/manage-history-lists/manage-history-lists.md
index 2e7477b4e..ccb94d1ac 100644
--- a/docs/common-workflows/administration/manage-history-lists/manage-history-lists.md
+++ b/docs/common-workflows/administration/manage-history-lists/manage-history-lists.md
@@ -1,6 +1,6 @@
 ---
 title: Manage History Lists
-Description: Manage History Lists using the MicroStrategy REST API.
+Description: Manage History Lists using the Strategy REST API.
 ---
 
 <Available since="2021 Update 8" />
diff --git a/docs/common-workflows/administration/manage-licensing/license-audit-compliance.md b/docs/common-workflows/administration/manage-licensing/license-audit-compliance.md
index 93473bb8e..8e50655ac 100644
--- a/docs/common-workflows/administration/manage-licensing/license-audit-compliance.md
+++ b/docs/common-workflows/administration/manage-licensing/license-audit-compliance.md
@@ -158,11 +158,11 @@ Sample Response Body:
   "auditTime": "2023-05-04T10:47:46.766Z",
   "contactLicenses": [],
   "userGroups": [
-    ["3D0F5EF8978D4AE086012C196BF01EBA", "MicroStrategy Groups"],
+    ["3D0F5EF8978D4AE086012C196BF01EBA", "Strategy Groups"],
     ["5F3FAFE011D2D8CC6000CC8E67019608", "System Monitors"],
     ["5F3FAFE111D2D8CC6000CC8E67019608", "System Administrators"],
     ["C82C6B1011D2894CC0009D9F29718E4F", "Everyone"],
-    ["5B6C1434431D99F9A8230191FE5F6849", "MicroStrategy Service Accounts"],
+    ["5B6C1434431D99F9A8230191FE5F6849", "Strategy Service Accounts"],
     ["FB5CDCCE4D0E70EDE48110A0FDCFD370", "Platform Support Administrators"]
   ],
   "userLicenses": [
@@ -267,7 +267,7 @@ Sample Response Body:
       "privilege": {
         "id": "266",
         "name": "Use Application",
-        "description": "Provide the ability for organizations to connect to the MicroStrategy Intelligence Server through custom applications.",
+        "description": "Provide the ability for organizations to connect to the Strategy Intelligence Server through custom applications.",
         "level": "project"
       },
       "sources": [
diff --git a/docs/common-workflows/administration/manage-licensing/license-manipulation.md b/docs/common-workflows/administration/manage-licensing/license-manipulation.md
index 697155ecc..e61c88ecb 100644
--- a/docs/common-workflows/administration/manage-licensing/license-manipulation.md
+++ b/docs/common-workflows/administration/manage-licensing/license-manipulation.md
@@ -264,7 +264,7 @@ Sample request body
         "installationUse": "production",
         "contact": {
           "customer": {
-            "company": "MicroStrategy",
+            "company": "Strategy",
             "department": "TEC",
             "firstName": "John",
             "lastName": "Doe",
@@ -279,7 +279,7 @@ Sample request body
             "usePersonalInfo": true
           },
           "installer": {
-            "company": "NotMicroStrategy",
+            "company": "NotStrategy",
             "department": "NotTEC",
             "firstName": "John",
             "lastName": "Doe",
@@ -316,7 +316,7 @@ curl --location --request PATCH 'https://demo.microstrategy.com/MicroStrategyLib
    "installationUse": "production",
    "contact": {
     "customer": {
-     "company": "MicroStrategy",
+     "company": "Strategy",
      "department": "TEC",
      "firstName": "John",
      "lastName": "Doe",
@@ -331,7 +331,7 @@ curl --location --request PATCH 'https://demo.microstrategy.com/MicroStrategyLib
      "usePersonalInfo": true
     },
     "installer": {
-     "company": "NotMicroStrategy",
+     "company": "NotStrategy",
      "department": "NotTEC",
      "firstName": "John",
      "lastName": "Doe",
@@ -421,24 +421,24 @@ Sample Response Body:
 <default_locale>9</default_locale>\n
 <products>\n
     <product>\n
-        <name>MicroStrategy Intelligence Server Universal</name>\n
+        <name>Strategy Intelligence Server Universal</name>\n
         <version>Unknown</version>\n
         <prompted_cpus>2</prompted_cpus>\n
     </product>\n
     <product>\n
-        <name>MicroStrategy OLAP Services Universal</name>\n
+        <name>Strategy OLAP Services Universal</name>\n
         <version>1.1.111.111</version>\n
     </product>\n
     <product>\n
-        <name>MicroStrategy Transaction Services Universal</name>\n
+        <name>Strategy Transaction Services Universal</name>\n
         <version>1.1.111.111</version>\n
     </product>\n
     <product>\n
-        <name>MicroStrategy Report Services Universal</name>\n
+        <name>Strategy Report Services Universal</name>\n
         <version>1.1.111.111</version>\n
     </product>\n
     <product>\n
-        <name>MicroStrategy Distribution Services</name>\n
+        <name>Strategy Distribution Services</name>\n
         <version>1.1.111.111</version>\n
     </product>\n
 </products>\n
@@ -484,7 +484,7 @@ Sample Response Body:
 <last_name>Doe</last_name>\n
 <email>johndoe@microstrategy.com</email>\n
 <phone>9998889999</phone>\n
-<company>NotMicroStrategy</company>\n
+<company>NotStrategy</company>\n
 <department>NotTEC</department>\n
 <title>Not Software Engineer</title>\n
 <street_address>1851 Towers Crescent Plaza</street_address>\n
diff --git a/docs/common-workflows/administration/manage-runtime-objects/manage-runtimes.md b/docs/common-workflows/administration/manage-runtime-objects/manage-runtimes.md
index dd1fca0aa..16a290a5e 100644
--- a/docs/common-workflows/administration/manage-runtime-objects/manage-runtimes.md
+++ b/docs/common-workflows/administration/manage-runtime-objects/manage-runtimes.md
@@ -5,7 +5,7 @@ description: You can use REST API requests to retrieve, create, update, and dele
 
 <Available since="2021 Update 7" />
 
-Starting in MicroStrategy 2021 Update 7, you can use REST API requests to retrieve, create, update, and delete runtime objects through the REST API.
+Starting in Strategy 2021 Update 7, you can use REST API requests to retrieve, create, update, and delete runtime objects through the REST API.
 
 The runtime object defines the detailed configuration for the virtual runtime, the virtual runtime is used for Python scripts remote execution.
 
diff --git a/docs/common-workflows/administration/manage-runtime-objects/retrieve-all-runtimes.md b/docs/common-workflows/administration/manage-runtime-objects/retrieve-all-runtimes.md
index 9ff2db03d..54910f3bb 100644
--- a/docs/common-workflows/administration/manage-runtime-objects/retrieve-all-runtimes.md
+++ b/docs/common-workflows/administration/manage-runtime-objects/retrieve-all-runtimes.md
@@ -44,7 +44,7 @@ You can get al the runtime objects in the body of the response.
 {
   "runtimes": [
     {
-      "name": "(Default) MicroStrategy",
+      "name": "(Default) Strategy",
       "id": "0F35652CA7D041978BF0CBCB67531203",
       "type": 80,
       "description": "A default server configuration used to execute Python scripts on IServer. It includes the latest versions of both Python and mstrio packages, as well as a default network access configuration. Allows for network access customization.",
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-a-migration-package.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-a-migration-package.md
index 9633dae81..a06b3e165 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-a-migration-package.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-a-migration-package.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a migration package
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c4f8860a-cb20-4e14-a7c8-16d450c167c5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -24,7 +24,7 @@ This workflow sample demonstrates how to create a migration package using REST A
 
 ## Creating a project package
 
-In this workflow sample, you want to create a project package that contains a `"Year"` object with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4` and all its dependents in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. Use `"replace"` as a conflict rule for all these objects.
+In this workflow sample, you want to create a project package that contains a `"Year"` object with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4` and all its dependents in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. Use `"replace"` as a conflict rule for all these objects.
 
 :::info
 
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-and-import-migration-packages.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-and-import-migration-packages.md
index c1e097fff..5b04ab8fc 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-and-import-migration-packages.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-and-import-migration-packages.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to create and import migration packag
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-e4a2caff-1aef-4724-be48-4635fff1133f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,6 +21,6 @@ You can use REST API requests to create and import migration packages.
 - [View content from an uploaded package](view-uploaded-package.md)
 - [Manage content group packages](manage-content-group-packages.md)
 
-See [KB34475](https://community.microstrategy.com/s/article/KB34475-How-to-migrate-Security-Roles-and-Security-Filters?language=en_US) for more information about how to migrate security roles and security filters between projects using MicroStrategy Object Manager. You can use the above REST API workflows to do the same thing.
+See [KB34475](https://community.microstrategy.com/s/article/KB34475-How-to-migrate-Security-Roles-and-Security-Filters?language=en_US) for more information about how to migrate security roles and security filters between projects using Strategy Object Manager. You can use the above REST API workflows to do the same thing.
 
 See [KB485076](https://community.microstrategy.com/s/article/Troubleshoot-object-migration-RESTful-API-issues) for more information about how to troubleshoot object migration issues.
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/import-a-migration-package.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/import-a-migration-package.md
index edfb78f88..a24d96bd0 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/import-a-migration-package.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/import-a-migration-package.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to import a migration package
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-7a6ff268-6e87-449b-a51f-30f134ab54d4?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -27,7 +27,7 @@ This workflow sample demonstrates how to import a migration package using REST A
 
 ## Import a project package
 
-You want to import a project package that contains a `"Year"` object, with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4`, and all its dependents in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You are using the `"Demo Project"`, which has a project ID of `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to import a project package that contains a `"Year"` object, with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4`, and all its dependents in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You are using the `"Demo Project"`, which has a project ID of `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/manage-content-group-packages.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/manage-content-group-packages.md
index 22f5460a1..3c625330e 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/manage-content-group-packages.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/manage-content-group-packages.md
@@ -14,7 +14,7 @@ Create a content group package using REST APIs:
 1. In the source metadata, create a configuration package where the input is the content group object. This package includes the content group object and recipient list.
 1. In the source metadata, create a project package, where the input is the content group object, for each project. This project package includes the configuration content bundle object as well as its contents (dashboards, documents, and reports that are included in the content group in this project).
 1. In the destination metadata, first import the configuration package and then the project package, one by one.
-1. In MicroStrategy Workstation, enable the content bundle feature. If the user in the destination metadata has the same GUID with the source metadata, then the recipient (user or user group) link will migrate over. However, if the user has the same name with a different GUID, then the recipient link will not migrate anymore.
+1. In Strategy Workstation, enable the content bundle feature. If the user in the destination metadata has the same GUID with the source metadata, then the recipient (user or user group) link will migrate over. However, if the user has the same name with a different GUID, then the recipient link will not migrate anymore.
 
 ## Object package requirements
 
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-newly-created-package.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-newly-created-package.md
index 48686957d..0858c7e2a 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-newly-created-package.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-newly-created-package.md
@@ -15,7 +15,7 @@ This workflow sample demonstrates how to view a newly created migration package
 1. [Download the package and save it as a binary file](#download-the-package-and-save-it-as-a-binary-file)
 1. [Delete the package](#delete-the-package)
 
-In this workflow sample, you want to create a project package that contains a `"Year"` object with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4` and all its dependents in the MicroStrategy Tutorial project. You also want to view the detailed definition of the `"Year"` object. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. Use `"replace"` as a conflict rule for all these objects.
+In this workflow sample, you want to create a project package that contains a `"Year"` object with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4` and all its dependents in the Strategy Tutorial project. You also want to view the detailed definition of the `"Year"` object. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. Use `"replace"` as a conflict rule for all these objects.
 
 :::info
 
@@ -204,7 +204,7 @@ Use [GET /api/packages/\{packageId}/objects](https://demo.microstrategy.com/Micr
 
 :::tip
 
-In MicroStrategy 2021 Update 3, we only support four types of objects, it is "Attribute(12)", "Fact(13)", "Hierarchy(14)", and "Table(15)" in project package. Configuration package is not supported for now.
+In Strategy 2021 Update 3, we only support four types of objects, it is "Attribute(12)", "Fact(13)", "Hierarchy(14)", and "Table(15)" in project package. Configuration package is not supported for now.
 
 :::
 
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-uploaded-package.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-uploaded-package.md
index 0009b7a3a..d8b00a751 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-uploaded-package.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-uploaded-package.md
@@ -14,7 +14,7 @@ This workflow sample demonstrates how to view an uploaded migration package usin
 1. [Get the package detailed definition](#get-the-package-detailed-definition)
 1. [Delete the package](#delete-the-package)
 
-You have a project package that contains a `Year` object, with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4`, and all its dependents in the MicroStrategy Tutorial project. You want to view the readable definitions of objects from this package for this project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You are also using the `"Demo Project"`, which has a project ID of `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You have a project package that contains a `Year` object, with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4`, and all its dependents in the Strategy Tutorial project. You want to view the readable definitions of objects from this package for this project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You are also using the `"Demo Project"`, which has a project ID of `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -148,7 +148,7 @@ Use [GET /api/packages/\{packageId}/objects](https://demo.microstrategy.com/Micr
 
 :::tip
 
-In MicroStrategy 2021 Update 3, only the following types of objects are supported in the project package: "Attribute(12)", "Fact(13)", "Hierarchy(14)", and "Table(15)". The configuration package is not currently supported.
+In Strategy 2021 Update 3, only the following types of objects are supported in the project package: "Attribute(12)", "Fact(13)", "Hierarchy(14)", and "Table(15)". The configuration package is not currently supported.
 
 :::
 
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/edit-migrations-and-migration-groups.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/edit-migrations-and-migration-groups.md
index 705001cda..9fa24c62c 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/edit-migrations-and-migration-groups.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/edit-migrations-and-migration-groups.md
@@ -5,7 +5,7 @@ description: You can edit migration and migration group before importing.
 
 <Available since="2021 Update 9" />
 
-Starting in MicroStrategy 2021 Update 9, you can edit migrations and migration groups before importing. You can edit the names of migrations or migration groups and the objects within them, but not their type or purpose. You can edit migrations and migration groups for all types and purposes, except for uploaded migrations. However, you must pay attention to a migration's package and import statuses. You cannot edit migrations with a package status of 'creating' or 'locked'. You also cannot edit migrations with an import status of 'approved' or 'requested'. As expected, a migration group containing such a migration also cannot be edited.
+Starting in Strategy 2021 Update 9, you can edit migrations and migration groups before importing. You can edit the names of migrations or migration groups and the objects within them, but not their type or purpose. You can edit migrations and migration groups for all types and purposes, except for uploaded migrations. However, you must pay attention to a migration's package and import statuses. You cannot edit migrations with a package status of 'creating' or 'locked'. You also cannot edit migrations with an import status of 'approved' or 'requested'. As expected, a migration group containing such a migration also cannot be edited.
 
 ## APIs
 
@@ -67,7 +67,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -380,7 +380,7 @@ Sample Response Body:
     "storage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "creating",
     "message": "",
@@ -748,7 +748,7 @@ Use the response body you saved in step 1 and change `name`, `treeView`, and `mi
         "purpose": "migration_group",
         "project": {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "MicroStrategy Tutorial"
+          "name": "Strategy Tutorial"
         },
         "tocView": {
           "settings": {
@@ -770,7 +770,7 @@ Use the response body you saved in step 1 and change `name`, `treeView`, and `mi
       "importInfo": {
         "project": {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "MicroStrategy Tutorial"
+          "name": "Strategy Tutorial"
         }
       }
     },
@@ -780,7 +780,7 @@ Use the response body you saved in step 1 and change `name`, `treeView`, and `mi
         "purpose": "migration_group",
         "project": {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "MicroStrategy Tutorial"
+          "name": "Strategy Tutorial"
         },
         "tocView": {
           "settings": {
@@ -802,7 +802,7 @@ Use the response body you saved in step 1 and change `name`, `treeView`, and `mi
       "importInfo": {
         "project": {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "MicroStrategy Tutorial"
+          "name": "Strategy Tutorial"
         }
       }
     },
@@ -1134,7 +1134,7 @@ When the API call is successful, it returns response code `204` with no response
 
 ## Performance
 
-To improve performance, MicroStrategy suggests you edit one migration or migration group per session and time.
+To improve performance, Strategy suggests you edit one migration or migration group per session and time.
 
 ## Compatibility
 
@@ -1150,7 +1150,7 @@ A migration or migration group created in an earlier platform version can be edi
 ## Troubleshooting
 
 - If the Library server cannot connect to the database, you may receive the following error:
-  - The API requires MicroStrategy Storage Service. Please contact your administrator.
+  - The API requires Strategy Storage Service. Please contact your administrator.
   - This can occur due to the following reasons:
     - Database is not running
     - Database version is lower than required
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/migrations-in-workstation.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/migrations-in-workstation.md
index 5c99a97dc..70857e825 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/migrations-in-workstation.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/migrations-in-workstation.md
@@ -1,11 +1,11 @@
 ---
 title: Migrations in Workstation
-description: You can use REST API requests to create and import migration packages just as the Workstations does. This way all packages are managed by the MicroStrategy Storage Service and the migration processes can be monitored in Workstation.
+description: You can use REST API requests to create and import migration packages just as the Workstations does. This way all packages are managed by the Strategy Storage Service and the migration processes can be monitored in Workstation.
 ---
 
 <Available since="2021 Update 6" />
 
-You can use REST API requests to create and import migration packages just as the Workstations does. This way all packages are managed by the [MicroStrategy Storage Service](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service.htm) and the migration processes can be monitored in Workstation.
+You can use REST API requests to create and import migration packages just as the Workstations does. This way all packages are managed by the [Strategy Storage Service](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service.htm) and the migration processes can be monitored in Workstation.
 
 - [Object migration between environments](object-migration-between-environments.md)
 - [Project merge between environments](project-merge-between-environments.md)
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-between-environments.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-between-environments.md
index 4aefe3ceb..90ca2c3d7 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-between-environments.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-between-environments.md
@@ -5,7 +5,7 @@ description: You can move packages of objects between environments within Workst
 
 <Available since="2021 Update 6" />
 
-Starting in MicroStrategy 2021 Update 6, you can move packages of objects between environments within Workstation. These packages are all maintained by the [MicroStrategy Storage Service](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service.htm), instead of you having to manage the packages yourself.
+Starting in Strategy 2021 Update 6, you can move packages of objects between environments within Workstation. These packages are all maintained by the [Strategy Storage Service](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service.htm), instead of you having to manage the packages yourself.
 
 You must [configure the package storage location in Workstation](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service_config_workstation.htm) to use this feature.
 
@@ -87,7 +87,7 @@ Sample Request Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     }
   }
 }
@@ -152,7 +152,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -177,7 +177,7 @@ Sample Response Body:
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   },
@@ -298,7 +298,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "locked",
     "message": "",
@@ -356,7 +356,7 @@ Copy the response body from step 4 and change `"replicated": false`, to `true`.
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "locked",
     "message": "",
@@ -417,7 +417,7 @@ Since the package import is asynchronously processing, this call checks the impo
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   }
@@ -545,7 +545,7 @@ Sample Request Header
 
 ## Performance
 
-For performance concerns, MicroStrategy suggests you create or import one package per session and time.
+For performance concerns, Strategy suggests you create or import one package per session and time.
 
 ## Compatibility
 
@@ -586,7 +586,7 @@ A package created in an earlier platform version can be imported to a newer plat
 ## Troubleshooting
 
 - If the Library Server cannot connect to the database, you may receive the following error response:
-  - The API requires MicroStrategy Storage Service. Please contact your administrator.
+  - The API requires Strategy Storage Service. Please contact your administrator.
   - This can occur due to the following reasons:
     - Database not running
     - Database version is lower than required
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-groups-between-environments.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-groups-between-environments.md
index c1bb1125d..a6423b0f7 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-groups-between-environments.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-groups-between-environments.md
@@ -5,7 +5,7 @@ description: You can move a group of object packages between environments within
 
 <Available since="2021 Update 7" />
 
-Starting in MicroStrategy 2021 Update 7, you can move a group of object packages between environments within Workstation. These groups of packages are all maintained by the [MicroStrategy Storage Service](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service.htm), instead of you having to manage the packages yourself.
+Starting in Strategy 2021 Update 7, you can move a group of object packages between environments within Workstation. These groups of packages are all maintained by the [Strategy Storage Service](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service.htm), instead of you having to manage the packages yourself.
 
 You must [configure the package storage location in Workstation](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service_config_workstation.htm) to use this feature.
 
@@ -1267,7 +1267,7 @@ Sample Request Header
 
 ## Performance
 
-For performance concerns, MicroStrategy suggests you create or import one package group per session and time.
+For performance concerns, Strategy suggests you create or import one package group per session and time.
 
 ## Compatibility
 
@@ -1312,7 +1312,7 @@ A package group created in an earlier platform version can be imported to a newe
 ## Troubleshooting
 
 - If the Library Server cannot connect to the database, you may receive the following error response:
-  - The API requires MicroStrategy Storage Service. Please contact your administrator.
+  - The API requires Strategy Storage Service. Please contact your administrator.
   - This can occur due to the following reasons:
   - Database not running
   - Database version is lower than required
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/project-merge-between-environments.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/project-merge-between-environments.md
index fc9054d15..6d943ec53 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/project-merge-between-environments.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/project-merge-between-environments.md
@@ -5,7 +5,7 @@ description: You can create migrations to merge all objects in a source project
 
 <Available since="2021 Update 6" />
 
-Starting in MicroStrategy 2021 Update 6, you can create migrations to merge all objects in a source project into another target project.
+Starting in Strategy 2021 Update 6, you can create migrations to merge all objects in a source project into another target project.
 
 You must [configure the package storage location in Workstation](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service_config_workstation.htm) to use this feature.
 
@@ -108,7 +108,7 @@ Provide the correct `environment` and `project` in `packageInfo` of the request
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     }
   }
 }
@@ -182,7 +182,7 @@ The value of `packageInfo.status` could be `creating`, and you should keep pulli
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -207,7 +207,7 @@ The value of `packageInfo.status` could be `creating`, and you should keep pulli
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   },
@@ -323,7 +323,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "locked",
     "message": "",
@@ -382,7 +382,7 @@ Sample Response Body:
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   },
@@ -431,7 +431,7 @@ Copy the response body from step 4 and change `"replicated": false"`, to `true`.
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "locked",
     "message": "",
@@ -490,7 +490,7 @@ Copy the response body from step 4 and change `"replicated": false"`, to `true`.
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   },
@@ -553,7 +553,7 @@ The value of `packageInfo.status` could be `creating`, and you should keep pulli
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -618,7 +618,7 @@ The value of `packageInfo.status` could be `creating`, and you should keep pulli
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   },
@@ -749,7 +749,7 @@ Sample Request Header:
 
 ## Performance
 
-For performance concerns, MicroStrategy suggests you create or import one package per session and time.
+For performance concerns, Strategy suggests you create or import one package per session and time.
 
 ## Compatibility
 
@@ -776,7 +776,7 @@ A package created in an earlier platform version can be imported to a newer plat
 ## Troubleshooting
 
 - If the Library Server cannot connect to the database, you may receive the following error response:
-  - The API requires MicroStrategy Storage Service. Please contact your administrator.
+  - The API requires Strategy Storage Service. Please contact your administrator.
   - This can occur due to the following reasons:
     - Database not running
     - Database version is lower than required
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/upload-and-download-migration-packages.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/upload-and-download-migration-packages.md
index 40fd3dd7f..8d38d0adb 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/upload-and-download-migration-packages.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/upload-and-download-migration-packages.md
@@ -5,7 +5,7 @@ description: You can upload and download migration packages in Workstation.
 
 <Available since="2021 Update 7" />
 
-Starting in MicroStrategy 2021 Update 7, you can upload and download migration packages in Workstation. These packages are all maintained by the [MicroStrategy Storage Service](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service.htm), users can download these packages from one storage service and then upload to another the storage service.
+Starting in Strategy 2021 Update 7, you can upload and download migration packages in Workstation. These packages are all maintained by the [Strategy Storage Service](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service.htm), users can download these packages from one storage service and then upload to another the storage service.
 
 This feature is usually used in the following two scenarios:
 
@@ -212,7 +212,7 @@ Sample Request Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     }
   }
 }
@@ -300,7 +300,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   },
@@ -353,7 +353,7 @@ A package created in an earlier platform version can be downloaded, uploaded and
 ## Troubleshooting
 
 - If the Library Server cannot connect to the database, you may receive the following error responses:
-  - The API requires MicroStrategy Storage Service. Please contact your administrator.
+  - The API requires Strategy Storage Service. Please contact your administrator.
   - This can occur due to the following reasons:
     - Database version is lower than required
     - Database configuration is missing or invalid in `configOverride.properties` file
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/validate-migrations.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/validate-migrations.md
index 65447a34c..9bd4dfb45 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/validate-migrations.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/validate-migrations.md
@@ -5,7 +5,7 @@ description: You can validate migrations between environments within Workstation
 
 <Available since="2021 Update 6" />
 
-Starting in MicroStrategy 2021 Update 6, you can validate migrations between environments within Workstation. When you validate a migration, you are performing all merges without committing any changes to the metadata. If a migration fails to be validated in a target environment, the migration also fails when being migrated to the same target. Administrator users can only validate migrations prior to migration.
+Starting in Strategy 2021 Update 6, you can validate migrations between environments within Workstation. When you validate a migration, you are performing all merges without committing any changes to the metadata. If a migration fails to be validated in a target environment, the migration also fails when being migrated to the same target. Administrator users can only validate migrations prior to migration.
 
 You must [configure the package storage location in Workstation](https://www2.microstrategy.com/producthelp/Current/Workstation/WebHelp/Lang_1033/Content/storage_service_config_workstation.htm) to use this feature.
 
@@ -132,7 +132,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -157,7 +157,7 @@ Sample Response Body:
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   },
@@ -310,7 +310,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -335,7 +335,7 @@ Sample Response Body:
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     },
     "deleted": false
   },
@@ -352,7 +352,7 @@ Sample Response Body:
 
 ## Performance
 
-For performance concerns, MicroStrategy suggests you validate one package per session and time.
+For performance concerns, Strategy suggests you validate one package per session and time.
 
 ## Compatibility
 
@@ -368,7 +368,7 @@ A package validated in an earlier platform version can be validated to a newer p
 ## Troubleshooting
 
 - If the Library Server cannot connect to the database, you may receive the following error response:
-  - The API requires MicroStrategy Storage Service. Please contact your administrator.
+  - The API requires Strategy Storage Service. Please contact your administrator.
   - This can occur due to the following reasons:
     - Database not running
     - Database version is lower than required
@@ -381,6 +381,6 @@ A package validated in an earlier platform version can be validated to a newer p
   - Cannot create or modify the shared file. It may be temporarily unavailable for accessing the storage location.
   - The shared file cannot be accessed. It may be deleted or the storage location cannot be accessed.
 
-- MicroStrategy advises setting the **Maximum tolerance for computer clock synchronization** to a value of five minutes. See [Maximum tolerance for computer clock synchronization](https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/maximum-tolerance-for-computer-clock-synchronization) on the [Microsoft technical documentation](https://docs.microsoft.com/en-us/) site for more information about modifying this setting. After making this change, if your environment times differ by more than five minutes, you receive the following message:
+- Strategy advises setting the **Maximum tolerance for computer clock synchronization** to a value of five minutes. See [Maximum tolerance for computer clock synchronization](https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/maximum-tolerance-for-computer-clock-synchronization) on the [Microsoft technical documentation](https://docs.microsoft.com/en-us/) site for more information about modifying this setting. After making this change, if your environment times differ by more than five minutes, you receive the following message:
 
   The time difference between the source and target environments should be five minutes or less. Please modify the environment system time and try again.
diff --git a/docs/common-workflows/administration/monitors/manage-an-intelligence-server-cluster.md b/docs/common-workflows/administration/monitors/manage-an-intelligence-server-cluster.md
index 54c1f9c41..dfaa012ec 100644
--- a/docs/common-workflows/administration/monitors/manage-an-intelligence-server-cluster.md
+++ b/docs/common-workflows/administration/monitors/manage-an-intelligence-server-cluster.md
@@ -7,11 +7,11 @@ description: Intelligence Server provides you the functionality to cluster a gro
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-7f67e2a1-9eb5-45b1-8e4c-4fcec18a998a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-Intelligence Server provides you the functionality to cluster a group of Intelligence Server machines to take advantage of the many benefits available in a clustered environment. MicroStrategy REST exposes a set of APIs for viewing and editing members of connected Intelligence Server cluster:
+Intelligence Server provides you the functionality to cluster a group of Intelligence Server machines to take advantage of the many benefits available in a clustered environment. Strategy REST exposes a set of APIs for viewing and editing members of connected Intelligence Server cluster:
 
 - View member nodes and projects of the connected cluster
 - Adding a node to the connected cluster
@@ -69,7 +69,7 @@ This operation requires the "Monitor cluster" privilege.
       "projects": [
         {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "MicroStrategy Tutorial",
+          "name": "Strategy Tutorial",
           "status": "loaded"
         }
       ],
diff --git a/docs/common-workflows/administration/monitors/manage-caches.md b/docs/common-workflows/administration/monitors/manage-caches.md
index 29464b708..4e842eeea 100644
--- a/docs/common-workflows/administration/monitors/manage-caches.md
+++ b/docs/common-workflows/administration/monitors/manage-caches.md
@@ -10,11 +10,11 @@ sidebar_label: Purge object and element caches
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-7238f434-a209-45b1-a227-cba9887c20b4?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-When a user works with MicroStrategy, cache data is created. The data stored in the cache allows to increase system performance and improve user’s experience. Instead of loading the data required by system from some database, i.e., meta-data database, the data is retrieved from a cache memory. However, Platform Administrator or Analytics Architect may decide to purge the caches periodically. Currently, the REST API allows to delete cache data for objects and elements using a following endpoint:
+When a user works with Strategy, cache data is created. The data stored in the cache allows to increase system performance and improve user’s experience. Instead of loading the data required by system from some database, i.e., meta-data database, the data is retrieved from a cache memory. However, Platform Administrator or Analytics Architect may decide to purge the caches periodically. Currently, the REST API allows to delete cache data for objects and elements using a following endpoint:
 
 - `DELETE /api/monitors/projects/{projectId}/cache/{cacheType}`
 
@@ -31,7 +31,7 @@ The sections below present Cache Management REST API usage.
 ### Header
 
 - `X-MSTR-AuthToken`
-  - (Required) MicroStrategy authorization token.
+  - (Required) Strategy authorization token.
   - Data Type: `string`
   - Allowable Values: valid authorization token.
 
@@ -73,10 +73,10 @@ The X-MSTR-AuthToken is an authentication token which you receive during authent
   {
     "acg": 255,
     "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-    "name": "MicroStrategy Tutorial",
+    "name": "Strategy Tutorial",
     "status": 0,
     "alias": "",
-    "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+    "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
     "dateCreated": "2015-06-30T21:55:35.000+0000",
     "dateModified": "2022-06-25T12:48:15.000+0000",
     "owner": {
@@ -102,7 +102,7 @@ The X-MSTR-AuthToken is an authentication token which you receive during authent
 ]
 ```
 
-Please find the `id` for the desired project. For example, `id` of the project: “MicroStrategy Tutorial” is `B7CA92F04B9FAE8D941C3E9B7E0CD75`. We will use it in the next step.
+Please find the `id` for the desired project. For example, `id` of the project: “Strategy Tutorial” is `B7CA92F04B9FAE8D941C3E9B7E0CD75`. We will use it in the next step.
 
 ### Step 2 – Deleting the cache
 
diff --git a/docs/common-workflows/administration/monitors/monitor-and-manage-cube-caches.md b/docs/common-workflows/administration/monitors/monitor-and-manage-cube-caches.md
index be652918f..ddbec4302 100644
--- a/docs/common-workflows/administration/monitors/monitor-and-manage-cube-caches.md
+++ b/docs/common-workflows/administration/monitors/monitor-and-manage-cube-caches.md
@@ -10,7 +10,7 @@ description: The status of a cube tells you how the cube is currently being used
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-736d23cb-1247-49fc-99dc-83365a1502e6?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ The status of a cube tells you how the cube is currently being used and whether
 
 ## Instructions to access the cube cache monitor in Developer
 
-1. Open MicroStrategy Developer.
+1. Open Strategy Developer.
 1. In the left pane, navigate to **Administration** > **System Monitors** > **Caches** > **Intelligent Cubes** to access the cube cache list.
 
    ![cube_cache_list](../../../images/cube_cache_list.png)
@@ -162,7 +162,7 @@ Fill in the sample below to design your own output.
       "openViewCount": 0,
       "creationTime": "2018-02-12 07:15:17",
       "historicHitCount": 121,
-      "fileName": "C:\\Program Files (x86)\\MicroStrategy\\Intelligence Server\\Cube\\serverdefinition\\Server_tec-w-004832_PB19DEDCC11D4E0EFC000EB9495D0F44F\\363249D447A5EF245AD51AB916CA4904.cube",
+      "fileName": "C:\\Program Files (x86)\\Strategy\\Intelligence Server\\Cube\\serverdefinition\\Server_tec-w-004832_PB19DEDCC11D4E0EFC000EB9495D0F44F\\363249D447A5EF245AD51AB916CA4904.cube",
       "rowCount": 39,
       "columnCount": 8
     }
@@ -290,7 +290,7 @@ Fill in the sample below to design your own output.
   "openViewCount": 0,
   "creationTime": "2018-02-12 07:15:17",
   "historicHitCount": 121,
-  "fileName": "C:\\Program Files (x86)\\MicroStrategy\\Intelligence Server\\Cube\\serverdefinition\\Server_tec-w-004832_PB19DEDCC11D4E0EFC000EB9495D0F44F\\363249D447A5EF245AD51AB916CA4904.cube",
+  "fileName": "C:\\Program Files (x86)\\Strategy\\Intelligence Server\\Cube\\serverdefinition\\Server_tec-w-004832_PB19DEDCC11D4E0EFC000EB9495D0F44F\\363249D447A5EF245AD51AB916CA4904.cube",
   "rowCount": 39,
   "columnCount": 8,
   "jobExecutionStatistics": {
@@ -385,7 +385,7 @@ Fill in the sample below to design your own output. We recommend you specify all
   "aggregatedCacheUsages": [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "currentUsage": 178000,
       "capacity": 280000 // Capacity just for project level, not for user level
     },
diff --git a/docs/common-workflows/administration/monitors/project-administration.md b/docs/common-workflows/administration/monitors/project-administration.md
index b910b5220..f606eb1cd 100644
--- a/docs/common-workflows/administration/monitors/project-administration.md
+++ b/docs/common-workflows/administration/monitors/project-administration.md
@@ -7,7 +7,7 @@ description: The workflow below allows an administrator to manage project distri
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-b8adf359-7841-499a-8197-bcbe15c06add?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -23,7 +23,7 @@ The following sequence of REST API requests allows an administrator to manage pr
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. Provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting response returns a status code of 204 and a response header containing X-MSTR-AuthToken, the authorization token that will be used by subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. Provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting response returns a status code of 204 and a response header containing X-MSTR-AuthToken, the authorization token that will be used by subsequent requests.
 
 ### Sample request
 
@@ -96,7 +96,7 @@ This operation requires the "Monitor cluster" privilege.
         "projects": [
           {
             "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-            "name": "MicroStrategy Tutorial",
+            "name": "Strategy Tutorial",
             "status": "unloaded"
           },
           {
@@ -115,7 +115,7 @@ This operation requires the "Monitor cluster" privilege.
         "projects": [
           {
             "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-            "name": "MicroStrategy Tutorial",
+            "name": "Strategy Tutorial",
             "status": "loaded"
           },
           {
@@ -152,7 +152,7 @@ To apply a filter on project id and node name, you can use the filter option of
         "projects": [
           {
             "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-            "name": "MicroStrategy Tutorial",
+            "name": "Strategy Tutorial",
             "status": "unloaded"
           }
         ],
@@ -209,7 +209,7 @@ This operation requires the "Load and Unload project" and "Idle and Resume proje
   ```json
   {
     "project": {
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
       "status": "pending"
     }
@@ -278,7 +278,7 @@ This operation requires the "Load and Unload project" and "Idle and Resume proje
 
 Endpoint: [GET /api/monitors/iServer/nodes](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Monitors/getClusterNodes)
 
-In the example above, the project status of `"MicroStrategy Tutorial"` was changed from unloaded to loaded on the cluster node named env-160560laio1use1. You can view the updated status through this API. Here, you can use the filter option on project id "B7CA92F04B9FAE8D941C3E9B7E0CD754" and/or on node name `"env-160560laio1use1"` to get information about the node.
+In the example above, the project status of `"Strategy Tutorial"` was changed from unloaded to loaded on the cluster node named env-160560laio1use1. You can view the updated status through this API. Here, you can use the filter option on project id "B7CA92F04B9FAE8D941C3E9B7E0CD754" and/or on node name `"env-160560laio1use1"` to get information about the node.
 
 - Curl:
 
@@ -299,7 +299,7 @@ In the example above, the project status of `"MicroStrategy Tutorial"` was chang
         "projects": [
           {
             "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-            "name": "MicroStrategy Tutorial",
+            "name": "Strategy Tutorial",
             "status": "loaded"
           }
         ],
@@ -335,7 +335,7 @@ The project status can be changed using the `PATCH /api/monitors/iServer/nodes/{
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST Server. In this example, you close the active user session by providing the authorization token, X-MSTR-AuthToken, generated by `POST /api/auth/login`. If the call is successful, the resulting response returns the status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST Server. In this example, you close the active user session by providing the authorization token, X-MSTR-AuthToken, generated by `POST /api/auth/login`. If the call is successful, the resulting response returns the status code 204.
 
 - Curl:
 
diff --git a/docs/common-workflows/administration/server-management/manage-fences/create-fence.md b/docs/common-workflows/administration/server-management/manage-fences/create-fence.md
index cda684dfe..bf2abe7ed 100644
--- a/docs/common-workflows/administration/server-management/manage-fences/create-fence.md
+++ b/docs/common-workflows/administration/server-management/manage-fences/create-fence.md
@@ -9,7 +9,7 @@ description: This workflow sample demonstrates how to create a new user or workl
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-5aef5846-6a6a-4d65-a91d-b3ebf5d96520?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -65,7 +65,7 @@ The `name`, `rank` and `nodes` are mandatory fields for both types of fences. Th
   "projects": [
     {
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     }
   ]
 }
@@ -99,7 +99,7 @@ curl -X POST \
   "projects": [
     {
      "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-     "name": "MicroStrategy Tutorial"
+     "name": "Strategy Tutorial"
     }
   ]
 }'
@@ -136,7 +136,7 @@ You can view the detailed information of new created `administrator_user_fence`
   "projects": [
     {
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     }
   ],
   "id": "YWRtaW5pc3RyYXRvcl91c2VyX2ZlbmNl"
diff --git a/docs/common-workflows/administration/server-management/manage-fences/delete-specific-fence.md b/docs/common-workflows/administration/server-management/manage-fences/delete-specific-fence.md
index 18214f65b..cab25f730 100644
--- a/docs/common-workflows/administration/server-management/manage-fences/delete-specific-fence.md
+++ b/docs/common-workflows/administration/server-management/manage-fences/delete-specific-fence.md
@@ -9,7 +9,7 @@ description: This workflow sample demonstrates how to delete a specific user or
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-977138df-2f06-40ae-87f3-8af880b7a336?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/server-management/manage-fences/manage-fences.md b/docs/common-workflows/administration/server-management/manage-fences/manage-fences.md
index eacf8d8b0..1583e0077 100644
--- a/docs/common-workflows/administration/server-management/manage-fences/manage-fences.md
+++ b/docs/common-workflows/administration/server-management/manage-fences/manage-fences.md
@@ -9,7 +9,7 @@ description: Within a cluster, fences allows an administrator or a user with Dss
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2564e447-4b77-42c9-99a4-97d7979b348c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -31,7 +31,7 @@ Manage User and Workload Fences REST APIs were released in 2021 Update 6
 
 :::
 
-You can use REST API requests to retrieve, create, update, and delete the user and workload fences with [DssXmlPrivilegesConfigureServerBasic](https://www2.microstrategy.com/producthelp/Current/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPrivilegeTypes.html#DssXmlPrivilegesConfigureServerBasic) and [DssXmlPrivilegesUseClusterMonitor](https://www2.microstrategy.com/producthelp/Current/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPrivilegeTypes.html#DssXmlPrivilegesUseClusterMonitor) privileges across all nodes without restarting the clustered MicroStrategy Intelligence Servers.
+You can use REST API requests to retrieve, create, update, and delete the user and workload fences with [DssXmlPrivilegesConfigureServerBasic](https://www2.microstrategy.com/producthelp/Current/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPrivilegeTypes.html#DssXmlPrivilegesConfigureServerBasic) and [DssXmlPrivilegesUseClusterMonitor](https://www2.microstrategy.com/producthelp/Current/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPrivilegeTypes.html#DssXmlPrivilegesUseClusterMonitor) privileges across all nodes without restarting the clustered Strategy Intelligence Servers.
 
 - [Create a new fence](create-fence.md)
 - [Retrieve the list of fences](retrieve-list-of-fences.md)
diff --git a/docs/common-workflows/administration/server-management/manage-fences/retrieve-specific-fence.md b/docs/common-workflows/administration/server-management/manage-fences/retrieve-specific-fence.md
index 04cab6bfe..9225584b1 100644
--- a/docs/common-workflows/administration/server-management/manage-fences/retrieve-specific-fence.md
+++ b/docs/common-workflows/administration/server-management/manage-fences/retrieve-specific-fence.md
@@ -70,7 +70,7 @@ You can view the detailed information of `administrator_user_fence` user fence i
   "projects": [
     {
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-      "name": "MicroStrategy Tutorial"
+      "name": "Strategy Tutorial"
     }
   ],
   "id": "YWRtaW5pc3RyYXRvcl91c2VyX2ZlbmNl"
diff --git a/docs/common-workflows/administration/server-management/manage-fences/update-specific-fence.md b/docs/common-workflows/administration/server-management/manage-fences/update-specific-fence.md
index 668c845ea..1809e6182 100644
--- a/docs/common-workflows/administration/server-management/manage-fences/update-specific-fence.md
+++ b/docs/common-workflows/administration/server-management/manage-fences/update-specific-fence.md
@@ -9,7 +9,7 @@ description: This workflow sample demonstrates how to update a specific fence.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2b48c198-0938-4578-ae8c-9ab957f046f2?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -118,7 +118,7 @@ You can view the detailed information of updated `administrator_user_fence` user
   "projects": [
     {
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-      "name": "MicroStrategy Tutorials"
+      "name": "Strategy Tutorials"
     }
   ],
   "id": "YWRtaW5pc3RyYXRvcl91c2VyX2ZlbmNl"
diff --git a/docs/common-workflows/administration/server-management/manage-languages.md b/docs/common-workflows/administration/server-management/manage-languages.md
index bf1cb65bf..c43bd779c 100644
--- a/docs/common-workflows/administration/server-management/manage-languages.md
+++ b/docs/common-workflows/administration/server-management/manage-languages.md
@@ -9,7 +9,7 @@ description: This section covers creating, updating and deleting language object
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d97007d2-a5be-4748-913d-c243b1b21663?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/server-management/manage-quick-search-indices.md b/docs/common-workflows/administration/server-management/manage-quick-search-indices.md
index dd343ddff..c45d028a4 100644
--- a/docs/common-workflows/administration/server-management/manage-quick-search-indices.md
+++ b/docs/common-workflows/administration/server-management/manage-quick-search-indices.md
@@ -9,7 +9,7 @@ description: The Manage Quick Search Indices API family allows you to view the s
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-75d970f5-31b8-4fda-93cc-1aabe3f7441d?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -71,7 +71,7 @@ Sample Response Body:
       "machineName": "aws-amazonlinux-base-template"
     },
     {
-      "projectName": "MicroStrategy Tutorial",
+      "projectName": "Strategy Tutorial",
       "projectId": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
       "status": "completed_on",
       "percentComplete": 1.0,
diff --git a/docs/common-workflows/administration/server-management/manage-server-settings.md b/docs/common-workflows/administration/server-management/manage-server-settings.md
index dbea0bc15..9a1389e54 100644
--- a/docs/common-workflows/administration/server-management/manage-server-settings.md
+++ b/docs/common-workflows/administration/server-management/manage-server-settings.md
@@ -9,7 +9,7 @@ description: A high-level workflow sample for managing server settings is shown
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-f79f1c3f-2313-4f26-8c5c-7b38a686c921?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -27,7 +27,7 @@ A detailed explanation of each step is provided below.
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the user to authenticate with the MicroStrategy REST Server. You can provide the information used to create the session in the body of the request. In this example, you can use standard authentication, so you need to provide the username and password. If the call is successful, the resulting response returns a status code of 204 and a response header containing X-MSTR-AuthToken. This authorization token is used by all subsequent requests.
+This endpoint allows the user to authenticate with the Strategy REST Server. You can provide the information used to create the session in the body of the request. In this example, you can use standard authentication, so you need to provide the username and password. If the call is successful, the resulting response returns a status code of 204 and a response header containing X-MSTR-AuthToken. This authorization token is used by all subsequent requests.
 
 In the following example, standard authentication uses a username of administrator and a blank password.
 
@@ -66,7 +66,7 @@ Response Code: 204 (Success: No Content)
 
 Endpoint: [GET /api/v2/iserver/settings/config](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System%20Administration/getIserverSettingsProperties)
 
-This endpoint allows the user to retrieve information on all Intelligence Server settings that are available in MicroStrategy REST API. The information includes the setting description, type, options, unit, minimum value, maximum value, and reboot rule. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
+This endpoint allows the user to retrieve information on all Intelligence Server settings that are available in Strategy REST API. The information includes the setting description, type, options, unit, minimum value, maximum value, and reboot rule. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
 
 :::tip
 
@@ -137,7 +137,7 @@ Response Code: 200 (Success: OK)
 
 Endpoint: [GET /api/v2/iserver/settings](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System%20Administration/getIserverSettings)
 
-This endpoint allows you to retrieve all Intelligence Server setting values that are available in MicroStrategy REST API. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
+This endpoint allows you to retrieve all Intelligence Server setting values that are available in Strategy REST API. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
 
 ### Sample request
 
@@ -255,7 +255,7 @@ Response Code: 200 (Success: OK)
 
 Endpoint: [PUT /api/v2/iserver/settings](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System%20Administration/setAllIserverSettings)
 
-This endpoint allows you to access all of the Intelligence Server setting values that are available in MicroStrategy REST API. In this endpoint, you must provide a complete list of Intelligence Server settings, which is the different from the `PATCH /api/v2/iserver/settings` endpoint. You can find a list of Intelligence Server settings exposed in REST API via `GET /api/v2/iserver/settings/config`. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
+This endpoint allows you to access all of the Intelligence Server setting values that are available in Strategy REST API. In this endpoint, you must provide a complete list of Intelligence Server settings, which is the different from the `PATCH /api/v2/iserver/settings` endpoint. You can find a list of Intelligence Server settings exposed in REST API via `GET /api/v2/iserver/settings/config`. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
 
 :::tip
 
@@ -347,7 +347,7 @@ Response Code: 200 (Success: OK)
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out the authenticated user from the MicroStrategy REST server. In this example, you close the active user session by providing the `X-MSTR-AuthToken` authorization token, which is generated by `POST /api/auth/login`. If the call is successful, the resulting response returns a status code of 204.
+This endpoint allows the caller to log out the authenticated user from the Strategy REST server. In this example, you close the active user session by providing the `X-MSTR-AuthToken` authorization token, which is generated by `POST /api/auth/login`. If the call is successful, the resulting response returns a status code of 204.
 
 ### Sample request
 
diff --git a/docs/common-workflows/administration/server-management/server-level-privileges/manage-server-level-privileges.md b/docs/common-workflows/administration/server-management/server-level-privileges/manage-server-level-privileges.md
index 0308176c7..ef5ee8ea5 100644
--- a/docs/common-workflows/administration/server-management/server-level-privileges/manage-server-level-privileges.md
+++ b/docs/common-workflows/administration/server-management/server-level-privileges/manage-server-level-privileges.md
@@ -7,7 +7,7 @@ description: A high-level workflow sample for managing server-level privileges i
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-27dd7275-e91a-4fe8-900b-0590e0de37b6?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -25,7 +25,7 @@ A detailed explanation of each step is provided below:
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication, so you need to provide the username, password, and loginMode. The loginMode specifies the authentication mode to use. If you omit an optional field, the REST server uses the default value. If the call is successful, the resulting HTTP response returns a status code of 204 and a response header containing X-MSTR-AuthToken. This authorization token is used by all subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication, so you need to provide the username, password, and loginMode. The loginMode specifies the authentication mode to use. If you omit an optional field, the REST server uses the default value. If the call is successful, the resulting HTTP response returns a status code of 204 and a response header containing X-MSTR-AuthToken. This authorization token is used by all subsequent requests.
 
 In the following example, standard authentication uses a username of administrator and a blank password.
 
@@ -344,7 +344,7 @@ The REST server returns a JSON object that contains the updated information for
     },
     {
       "id": "C2E4DA4A411B972B063FE8A583989959",
-      "name": "MicroStrategy Web Professional",
+      "name": "Strategy Web Professional",
       "source": {
         "type": ["MSTR"]
       }
@@ -383,7 +383,7 @@ The response is irrelevant to the privilege update. This is expected behavior. R
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out the authenticated user from the MicroStrategy REST server. In this example, you close the active user session by providing the X-MSTR-AuthToken authorization token, which is generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code of 204.
+This endpoint allows the caller to log out the authenticated user from the Strategy REST server. In this example, you close the active user session by providing the X-MSTR-AuthToken authorization token, which is generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code of 204.
 
 ### Sample request
 
diff --git a/docs/common-workflows/administration/server-management/server-level-privileges/server-level-privileges.md b/docs/common-workflows/administration/server-management/server-level-privileges/server-level-privileges.md
index c51fb5a82..1f355f694 100644
--- a/docs/common-workflows/administration/server-management/server-level-privileges/server-level-privileges.md
+++ b/docs/common-workflows/administration/server-management/server-level-privileges/server-level-privileges.md
@@ -7,7 +7,7 @@ description: Privileges are assigned to users and user groups to authorize what
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-27dd7275-e91a-4fe8-900b-0590e0de37b6?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/server-management/server-level-privileges/watch-kpi-insight-service-privileges.md b/docs/common-workflows/administration/server-management/server-level-privileges/watch-kpi-insight-service-privileges.md
index 8fc696608..51f736f31 100644
--- a/docs/common-workflows/administration/server-management/server-level-privileges/watch-kpi-insight-service-privileges.md
+++ b/docs/common-workflows/administration/server-management/server-level-privileges/watch-kpi-insight-service-privileges.md
@@ -7,7 +7,7 @@ description: A high-level workflow sample for managing Watch KPI and Insight ser
 
 A high-level workflow sample for managing Watch KPI and Insight service privileges is shown below. The sequence of REST API requests in the following procedure allows an administrative user to assign server-level privilege for a specific user or user group to use Watch KPI and Insight service.
 
-For the privileges to use Watch KPI and Insight service, please refer to [Assign privileges to MicroStrategy Insight](https://www2.microstrategy.com/producthelp/2021/Library/en-us/Content/insights_privileges.htm).
+For the privileges to use Watch KPI and Insight service, please refer to [Assign privileges to Strategy Insight](https://www2.microstrategy.com/producthelp/2021/Library/en-us/Content/insights_privileges.htm).
 
 A detailed explanation of each step is provided below:
 
diff --git a/docs/common-workflows/administration/user-management/create-and-update-user-groups.md b/docs/common-workflows/administration/user-management/create-and-update-user-groups.md
index 530deb77e..76ed1755e 100644
--- a/docs/common-workflows/administration/user-management/create-and-update-user-groups.md
+++ b/docs/common-workflows/administration/user-management/create-and-update-user-groups.md
@@ -8,7 +8,7 @@ description: A workflow sample for managing user groups in the metadata is provi
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-19b75da6-a5cf-47a0-a202-a4248e893d7c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -34,7 +34,7 @@ A detailed explanation of each step is provided below:
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide `username`, `password`, and `loginMode` (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns a status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used by subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide `username`, `password`, and `loginMode` (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns a status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used by subsequent requests.
 
 In this example, you will use Standard authentication and log in as "administrator" with no password.
 
@@ -360,7 +360,7 @@ Sample Response
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ![swagger_POST_auth_logout_940x208](../../../images/swagger_POST_auth_logout_940x208.png)
 
diff --git a/docs/common-workflows/administration/user-management/create-new-users.md b/docs/common-workflows/administration/user-management/create-new-users.md
index ef3a1172d..d66e7570e 100644
--- a/docs/common-workflows/administration/user-management/create-new-users.md
+++ b/docs/common-workflows/administration/user-management/create-new-users.md
@@ -8,7 +8,7 @@ description: A workflow sample for creating a new user, a process often called o
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-be8db67e-6743-49ef-beb5-9efb96e01e4b?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -29,7 +29,7 @@ A detailed explanation of each step is provided below:
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns a status code 204 and a response header containing X-MSTR-AuthToken, the authorization token that will be used by subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns a status code 204 and a response header containing X-MSTR-AuthToken, the authorization token that will be used by subsequent requests.
 
 ![swagger_POST_auth_login_1003x508](../../../images/swagger_POST_auth_login_1003x508.png)
 
@@ -408,7 +408,7 @@ Sample Response
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ![swagger_POST_auth_logout_1010x223](../../../images/swagger_POST_auth_logout_1010x223.png)
 
diff --git a/docs/common-workflows/administration/user-management/create-security-roles.md b/docs/common-workflows/administration/user-management/create-security-roles.md
index 6ea66db9a..aced91565 100644
--- a/docs/common-workflows/administration/user-management/create-security-roles.md
+++ b/docs/common-workflows/administration/user-management/create-security-roles.md
@@ -8,7 +8,7 @@ description: A security role is a set of privileges that can be assigned to user
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-ff1b1eae-77f6-461b-85cd-d63709d4b747?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -68,7 +68,7 @@ To make it easy for you to test this workflow in your environment, [download the
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication, so you need to provide `username`, `password`, and `loginMode` (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns a status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used by subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication, so you need to provide `username`, `password`, and `loginMode` (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns a status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used by subsequent requests.
 
 In this example, standard authentication and log in credentials "administrator" with `<blank>` password is used.
 
@@ -500,7 +500,7 @@ Two examples are provided below. In the first example to make security role assi
         "members": []
       },
       {
-        "name": "MicroStrategy Tutorial",
+        "name": "Strategy Tutorial",
         "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
         "members": []
       }
@@ -629,7 +629,7 @@ Get information for a specific security role using the security role id. You obt
         "members": []
       },
       {
-        "name": "MicroStrategy Tutorial",
+        "name": "Strategy Tutorial",
         "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
         "members": []
       }
@@ -758,7 +758,7 @@ This API endpoint is used to get information for all security roles. A security
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST Server. In this example, you close the active user session by providing the authorization token, X-MSTR-AuthToken, generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST Server. In this example, you close the active user session by providing the authorization token, X-MSTR-AuthToken, generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ### Sample request
 
diff --git a/docs/common-workflows/administration/user-management/manage-user-and-user-groups.md b/docs/common-workflows/administration/user-management/manage-user-and-user-groups.md
index 10759a566..f0161593b 100644
--- a/docs/common-workflows/administration/user-management/manage-user-and-user-groups.md
+++ b/docs/common-workflows/administration/user-management/manage-user-and-user-groups.md
@@ -7,7 +7,7 @@ description: Administrators can make REST API calls to manage users and user gro
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-dc9e5266-db8c-4842-9c44-16b5dd614f47).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/administration/user-management/manage-users.md b/docs/common-workflows/administration/user-management/manage-users.md
index e72b14ee1..24b4e7207 100644
--- a/docs/common-workflows/administration/user-management/manage-users.md
+++ b/docs/common-workflows/administration/user-management/manage-users.md
@@ -8,7 +8,7 @@ description: A workflow sample for managing users in the metadata is provided be
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-be8db67e-6743-49ef-beb5-9efb96e01e4b?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -28,7 +28,7 @@ A detailed explanation of each step is provided below:
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide `username`, `password`, and `loginMode` (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns a status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used by subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide `username`, `password`, and `loginMode` (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns a status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used by subsequent requests.
 
 ![swagger_POST_auth_login](../../../images/swagger_POST_auth_login.png)
 
@@ -308,7 +308,7 @@ Sample Response
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated by `POST /api/auth/login`. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ![swagger_POST_auth_logout](../../../images/swagger_POST_auth_logout.png)
 
diff --git a/docs/common-workflows/analytics/export-to-pdf.md b/docs/common-workflows/analytics/export-to-pdf.md
index 0fb461acf..4baae6bab 100644
--- a/docs/common-workflows/analytics/export-to-pdf.md
+++ b/docs/common-workflows/analytics/export-to-pdf.md
@@ -7,7 +7,7 @@ description: The workflow for exporting a document to PDF includes the following
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-3835f147-fc3e-4e94-bc73-af51f57f7e83?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -25,7 +25,7 @@ A detailed explanation of each step is provided below:
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
 
 ![swagger_POST_auth_login](../../images/swagger_POST_auth_login.png)
 
@@ -85,7 +85,7 @@ Sample Response
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the MicroStrategy REST Server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 ![swagger_GET_projects](../../images/swagger_GET_projects.png)
 
@@ -116,9 +116,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "alias": "",
-      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -137,7 +137,7 @@ Sample Response
 
 Endpoint: [POST /api/documents/\{id}/instances](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Dossiers%20and%20Documents/createDocumentInstance)
 
-This endpoint allows the caller to execute a specific document in a specific project and create an instance of that document. In this example, you execute a document called "Casino Analysis" (located in MicroStrategy Tutorial>Shared Reports>MicroStrategy Platform Capabilities>MicroStrategy Report Services>Visual Insight). You use the authorization token returned in step 1 as the value for `X-MSTR-AuthToken` and provide the project ID and the document ID. In this example, you leave the request body empty. The resulting HTTP response returns an HTTP status 201 and a JSON object containing the instance ID ("mid") of the document.
+This endpoint allows the caller to execute a specific document in a specific project and create an instance of that document. In this example, you execute a document called "Casino Analysis" (located in Strategy Tutorial>Shared Reports>Strategy Platform Capabilities>Strategy Report Services>Visual Insight). You use the authorization token returned in step 1 as the value for `X-MSTR-AuthToken` and provide the project ID and the document ID. In this example, you leave the request body empty. The resulting HTTP response returns an HTTP status 201 and a JSON object containing the instance ID ("mid") of the document.
 
 ![swagger_POST_documents](../../images/swagger_POST_documents.png)
 
@@ -259,7 +259,7 @@ Sample Response
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ![swagger_POST_auth_logout](../../images/swagger_POST_auth_logout.png)
 
diff --git a/docs/common-workflows/analytics/filter-data/filter-data.md b/docs/common-workflows/analytics/filter-data/filter-data.md
index 7c71d4b5a..31cbc9120 100644
--- a/docs/common-workflows/analytics/filter-data/filter-data.md
+++ b/docs/common-workflows/analytics/filter-data/filter-data.md
@@ -7,7 +7,7 @@ description: You can use REST API requests to filter data that is returned and t
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-b0a16367-8997-447d-8731-2d6281d4f9bc?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -39,7 +39,7 @@ You can use the following REST APIs to [filter the data that is returned when yo
 
 We have provided a [workflow sample](filter-dossier-instances/apply-filters-to-a-dossier.md) that illustrates how to create an instance of a dashboard with an existing filter applied, and then re-execute the same dashboard instance with updated selections for the same filter.
 
-For detailed information about filtering data in dashboards, see the [MicroStrategy product help](https://www2.microstrategy.com/producthelp/Current/MSTRWeb/WebHelp/Lang_1033/Content/filter_data.htm).
+For detailed information about filtering data in dashboards, see the [Strategy product help](https://www2.microstrategy.com/producthelp/Current/MSTRWeb/WebHelp/Lang_1033/Content/filter_data.htm).
 
 ### Retrieve filters applied in dashboard chapters
 
diff --git a/docs/common-workflows/analytics/filter-data/filter-dossier-instances/apply-filters-to-a-dossier.md b/docs/common-workflows/analytics/filter-data/filter-dossier-instances/apply-filters-to-a-dossier.md
index 85f94ccef..7c61f5a3f 100644
--- a/docs/common-workflows/analytics/filter-data/filter-dossier-instances/apply-filters-to-a-dossier.md
+++ b/docs/common-workflows/analytics/filter-data/filter-dossier-instances/apply-filters-to-a-dossier.md
@@ -8,7 +8,7 @@ description: In this workflow, you create an instance of a dashboard using the f
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d6462995-9003-4187-b121-47a5fb31436a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -28,7 +28,7 @@ Call `POST /api/auth/login` to authenticate into the environment with standard a
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
 
 Sample Request
 
@@ -86,7 +86,7 @@ Call `GET /api/projects` to obtain the list of available projects.
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects that the user session has access to. You use the authorization token returned during login as the value for **X-MSTR-AuthToken**. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to. The information returned for each project includes the project ID, which will be used by a later endpoint. In this example, you get the list of projects in the MicroStrategy Tutorial metadata.
+This endpoint allows the caller to get the list of projects that the user session has access to. You use the authorization token returned during login as the value for **X-MSTR-AuthToken**. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to. The information returned for each project includes the project ID, which will be used by a later endpoint. In this example, you get the list of projects in the Strategy Tutorial metadata.
 
 To execute this API, you need to provide the value for the following parameter in the request header:
 
@@ -121,9 +121,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "alias": "",
-      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -303,7 +303,7 @@ This endpoint allows the caller to execute a specific dashboard in a specific pr
 - **id** Dashboard ID generated by `GET /api/dossiers dossiers/{dossierId}/definition` or other endpoints
 - **body** Filter definition for the filter key/name generated by `GET /api/dossiers dossiers/{dossierId}/definition`
 
-In this example, you execute a dashboard called "Filters" (located in MicroStrategy Tutorial>Shared Reports. You use the authorization token returned by `POST /api/auth/login` as the value for X-MSTR-AuthToken, a project ID returned by `GET /api/projects`, a dashboard ID returned by `GET /api/dossiers`, and a filter definition. The request body contains the definition of the existing filter that was created for the dashboard; it is applied when the dashboard is executed. The resulting HTTP response returns an HTTP status 201, indicating that the dashboard instance has been created, and a JSON object containing the instance ID ("mid") of the dashboard.
+In this example, you execute a dashboard called "Filters" (located in Strategy Tutorial>Shared Reports. You use the authorization token returned by `POST /api/auth/login` as the value for X-MSTR-AuthToken, a project ID returned by `GET /api/projects`, a dashboard ID returned by `GET /api/dossiers`, and a filter definition. The request body contains the definition of the existing filter that was created for the dashboard; it is applied when the dashboard is executed. The resulting HTTP response returns an HTTP status 201, indicating that the dashboard instance has been created, and a JSON object containing the instance ID ("mid") of the dashboard.
 
 Sample Request
 
@@ -431,7 +431,7 @@ This has to be the same filter that was originally applied, but with different v
 
 :::
 
-In this example, you execute a dashboard called "Filters" (located in MicroStrategy Tutorial>Shared Reports. You use the authorization token returned during login as the value for `X-MSTR-AuthToken` and provide the project ID, dashboard ID, dashboard instance ID, and filter definition. In the request body, you modify the values for the filter to be applied to the dashboard when it is executed. The resulting HTTP response returns an HTTP status 204.
+In this example, you execute a dashboard called "Filters" (located in Strategy Tutorial>Shared Reports. You use the authorization token returned during login as the value for `X-MSTR-AuthToken` and provide the project ID, dashboard ID, dashboard instance ID, and filter definition. In the request body, you modify the values for the filter to be applied to the dashboard when it is executed. The resulting HTTP response returns an HTTP status 204.
 
 Sample Request
 
@@ -544,7 +544,7 @@ Call `POST /api/logout` to close the session.
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 Sample Request
 
diff --git a/docs/common-workflows/analytics/filter-data/filter-dossier-instances/filter-dossier-instances.md b/docs/common-workflows/analytics/filter-data/filter-dossier-instances/filter-dossier-instances.md
index b3bf8ee24..04858fe1e 100644
--- a/docs/common-workflows/analytics/filter-data/filter-dossier-instances/filter-dossier-instances.md
+++ b/docs/common-workflows/analytics/filter-data/filter-dossier-instances/filter-dossier-instances.md
@@ -10,4 +10,4 @@ You can use the following REST APIs to filter the data that is returned when you
 
 We have provided a [workflow sample](apply-filters-to-a-dossier.md) that illustrates how to create an instance of a dashboard with an existing filter applied, and then re-execute the same dashboard instance with updated selections for the same filter.
 
-For detailed information about filtering data in dashboards, see the [MicroStrategy product help](https://www2.microstrategy.com/producthelp/current/MSTRWeb/WebHelp/Lang_1033/Content/filter_data.htm).
+For detailed information about filtering data in dashboards, see the [Strategy product help](https://www2.microstrategy.com/producthelp/current/MSTRWeb/WebHelp/Lang_1033/Content/filter_data.htm).
diff --git a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-metric-limits/filter-report-and-cube-instances-using-metric-limits.md b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-metric-limits/filter-report-and-cube-instances-using-metric-limits.md
index 8276e804d..4b402fcea 100644
--- a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-metric-limits/filter-report-and-cube-instances-using-metric-limits.md
+++ b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-metric-limits/filter-report-and-cube-instances-using-metric-limits.md
@@ -7,11 +7,11 @@ description: How to filter report and cube instances using metric limits.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-621fc29f-e7e3-4065-9084-5bbdb0d81267?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-When you create a MicroStrategy report or cube instance using the following REST API endpoints, you can use a parameter called `metricLimits` in the body parameter of the request to filter the data that is returned:
+When you create a Strategy report or cube instance using the following REST API endpoints, you can use a parameter called `metricLimits` in the body parameter of the request to filter the data that is returned:
 
 - `POST /api/cubes/{cubeId}/instances`
 - `POST /api/reports/{reportId}/instances`
diff --git a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-metric-limits/supported-operators.md b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-metric-limits/supported-operators.md
index dd8052a27..8fde6d42b 100644
--- a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-metric-limits/supported-operators.md
+++ b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-metric-limits/supported-operators.md
@@ -5,19 +5,19 @@ description: The supported operators for metric limits.
 
 The table below lists the operators/functions that can be used to define metric limits when you are creating reports and cube instances with REST APIs (sometimes referred to as JSON Data API).
 
-| MicroStrategy Web Functions | REST API Operators | Function | Operands Count |
-| --------------------------- | ------------------ | -------- | -------------- |
-| Equals                      | Equals             | =        | 2              |
-| Does not equal              | NotEqual           | !=       | 2              |
-| Greater than                | Greater            | >        | 2              |
-| Less than                   | Less               | \<       | 2              |
-| Greater than or equal to    | GreaterEqual       | >=       | 2              |
-| Less than or equal to       | LessEqual          | \<=      | 2              |
-| Between                     | Between            |          | 3              |
-| Not between                 | NotBetween         |          | 3              |
-| Is null                     | IsNull             | null     | 1              |
-| Is not null                 | IsNotNull          | notnull  | 1              |
-| Highest                     | Rant.Top           |          | 2              |
-| Lowest                      | Rank.Bottom        |          | 2              |
-| Highest (%)                 | Percent.Top        |          | 2              |
-| Lowest (%)                  | Percent.Bottom     |          | 2              |
+| Strategy Web Functions   | REST API Operators | Function | Operands Count |
+| ------------------------ | ------------------ | -------- | -------------- |
+| Equals                   | Equals             | =        | 2              |
+| Does not equal           | NotEqual           | !=       | 2              |
+| Greater than             | Greater            | >        | 2              |
+| Less than                | Less               | \<       | 2              |
+| Greater than or equal to | GreaterEqual       | >=       | 2              |
+| Less than or equal to    | LessEqual          | \<=      | 2              |
+| Between                  | Between            |          | 3              |
+| Not between              | NotBetween         |          | 3              |
+| Is null                  | IsNull             | null     | 1              |
+| Is not null              | IsNotNull          | notnull  | 1              |
+| Highest                  | Rant.Top           |          | 2              |
+| Lowest                   | Rank.Bottom        |          | 2              |
+| Highest (%)              | Percent.Top        |          | 2              |
+| Lowest (%)               | Percent.Bottom     |          | 2              |
diff --git a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-requested-objects/filter-report-and-cube-instances-using-requested-objects.md b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-requested-objects/filter-report-and-cube-instances-using-requested-objects.md
index 5714b0913..8d4b6d4ed 100644
--- a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-requested-objects/filter-report-and-cube-instances-using-requested-objects.md
+++ b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-requested-objects/filter-report-and-cube-instances-using-requested-objects.md
@@ -7,11 +7,11 @@ description: How to filter report and cube instances using requestedObjects.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2650c93b-4797-4fa7-86cc-f38d0c43971e?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-When you create a MicroStrategy report or cube instance using the following REST API endpoints, you can use a parameter called `requestedObjects` in the body parameter of the request to specify the data that should be returned:
+When you create a Strategy report or cube instance using the following REST API endpoints, you can use a parameter called `requestedObjects` in the body parameter of the request to specify the data that should be returned:
 
 - `POST /api/cubes/{cubeId}/instances`
 - `POST /api/reports/{reportId}/instances`
diff --git a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-view-filters/filter-report-and-cube-instances-using-view-filters.md b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-view-filters/filter-report-and-cube-instances-using-view-filters.md
index 5aae154be..b89f1e37f 100644
--- a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-view-filters/filter-report-and-cube-instances-using-view-filters.md
+++ b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-view-filters/filter-report-and-cube-instances-using-view-filters.md
@@ -7,11 +7,11 @@ description: How to filter report and cube instances using view filters.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-eb1fcb00-e3b5-4a0c-bef9-4639e04c675c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-When you create a MicroStrategy report or cube instance using the following REST API endpoints, you can use a parameter called viewFilter in the body parameter of the request to filter the data that is returned:
+When you create a Strategy report or cube instance using the following REST API endpoints, you can use a parameter called viewFilter in the body parameter of the request to filter the data that is returned:
 
 - `POST /api/cubes/{cubeId}/instances`
 - `POST /api/reports/{reportId}/instances`
diff --git a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-view-filters/general-guidelines.md b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-view-filters/general-guidelines.md
index 8090f5697..b241972b3 100644
--- a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-view-filters/general-guidelines.md
+++ b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances-using-view-filters/general-guidelines.md
@@ -51,7 +51,7 @@ When you use a view filter to refine the data returned in a report or cube insta
   - Page by
   - Prompt
 - Features that may not work well with view filters include:
-  - Derived elements and other objects that cannot be qualified on in MicroStrategy Web
+  - Derived elements and other objects that cannot be qualified on in Strategy Web
   - Other REST API unsupported features
 - Attribute / element / form / metric IDs must be valid, which means:
 
diff --git a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances.md b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances.md
index 3ce5fdfb0..e460cc60b 100644
--- a/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances.md
+++ b/docs/common-workflows/analytics/filter-data/filter-report-and-cube-instances/filter-report-and-cube-instances.md
@@ -7,7 +7,7 @@ description: You can filter data that is returned by the following REST API requ
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-aba744e4-751e-410a-b5c1-4ad7d0db7b67?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/retrieve-filters-applied-to-a-visualization.md b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/retrieve-filters-applied-to-a-visualization.md
index e068dbbc9..39cdc3d62 100644
--- a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/retrieve-filters-applied-to-a-visualization.md
+++ b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/retrieve-filters-applied-to-a-visualization.md
@@ -7,7 +7,7 @@ description: You can use the following REST API endpoint to return information a
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-9468e98f-f4e6-4dcd-b63e-17cb724fa3be?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-attribute-based-view-filters.md b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-attribute-based-view-filters.md
index ef21f3d6e..9c606ea48 100644
--- a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-attribute-based-view-filters.md
+++ b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-attribute-based-view-filters.md
@@ -41,4 +41,4 @@ Attribute-based view filters can be applied in a number of ways. For example, th
    1. Click **OK**.
    1. Click **Save**.
 
-Refer to the MicroStrategy product manuals for a detailed explanation of attribute-based view filters and how they can be applied.
+Refer to the Strategy product manuals for a detailed explanation of attribute-based view filters and how they can be applied.
diff --git a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-metric-based-view-filters.md b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-metric-based-view-filters.md
index 5145fe564..46afc031b 100644
--- a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-metric-based-view-filters.md
+++ b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-metric-based-view-filters.md
@@ -43,4 +43,4 @@ Metric-based view filters can be applied in a number of ways. For example, they
    1. Click **OK**.
    1. Click **Save**.
 
-Refer to the MicroStrategy product manuals for a detailed explanation of metric-based view filters and how they can be applied.
+Refer to the Strategy product manuals for a detailed explanation of metric-based view filters and how they can be applied.
diff --git a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-metric-limit-criteria.md b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-metric-limit-criteria.md
index 2cb9ec5ee..224359fd7 100644
--- a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-metric-limit-criteria.md
+++ b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-metric-limit-criteria.md
@@ -36,4 +36,4 @@ Metric limits can be applied in a number of ways. For example, they can be appli
 1. Click **OK**.
 1. Click **Save**.
 
-Refer to the MicroStrategy product manuals for a detailed explanation of metric limits and how they can be applied.
+Refer to the Strategy product manuals for a detailed explanation of metric limits and how they can be applied.
diff --git a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-template-limit-criteria.md b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-template-limit-criteria.md
index a6d42294a..bedb101b7 100644
--- a/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-template-limit-criteria.md
+++ b/docs/common-workflows/analytics/filter-data/retrieve-filters-applied-to-a-visualization/return-template-limit-criteria.md
@@ -11,7 +11,7 @@ You use the following REST API endpoint to return information about the template
 
 - `GET /api/dossiers/{dossierId}/instances/{instanceId}/chapters/{chapterKey/visualizations/{visualizationKey}`
 
-Template limits correspond to Keep Only and Exclude filters in MicroStrategy Web. They can include multiple criteria, joined by the AND and OR operators. Complex template limit filtering criteria might look like this:
+Template limits correspond to Keep Only and Exclude filters in Strategy Web. They can include multiple criteria, joined by the AND and OR operators. Complex template limit filtering criteria might look like this:
 
 AND [((Accounts = Property, Plant, Equipment) Or (Accounts = Construction In Progress) Or (Accounts = Leasehold Improvements) Or (Accounts = Office Furniture & Equipment) Or (Accounts = Machinery & Equipment) Or (Accounts = Buildings & Improvements) Or (Accounts = Land & Improvements)) And (Departments = Sales and Marketing)]
 
@@ -35,4 +35,4 @@ Template limits can be applied in a number of ways. For example, they can be app
 1. Right-click an attribute or metric in the visualization.
 1. Choose **Keep Only** or Exclude from the drop-down menu.
 
-Refer to the MicroStrategy product manuals for a detailed explanation of template limits and how they can be applied.
+Refer to the Strategy product manuals for a detailed explanation of template limits and how they can be applied.
diff --git a/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/benefits.md b/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/benefits.md
index 3c4fb2d9c..a70d6f216 100644
--- a/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/benefits.md
+++ b/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/benefits.md
@@ -3,7 +3,7 @@ title: Benefits of creating a dataset incrementally with multiple requests
 description: The benefits of creating a dataset incrementally with multiple requests.
 ---
 
-The incremental approach to making external data available to MicroStrategy, using multiple requests, has a variety of benefits:
+The incremental approach to making external data available to Strategy, using multiple requests, has a variety of benefits:
 
 - You can create multiple tables in a dataset, rather than being limited to a single table.
 - The actions for uploading data and publishing the dataset have been separated, and data can be uploaded in separate chunks. This provides scalability and better performance and is very important when you are working with very large datasets.
diff --git a/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/workflow-create-a-dataset-incrementally-with-multiple-requests.md b/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/workflow-create-a-dataset-incrementally-with-multiple-requests.md
index e97eab2b3..5d4955e0e 100644
--- a/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/workflow-create-a-dataset-incrementally-with-multiple-requests.md
+++ b/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/workflow-create-a-dataset-incrementally-with-multiple-requests.md
@@ -8,7 +8,7 @@ description: The steps below illustrate the workflow for defining a dataset with
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2f45d89b-a009-455b-b181-f5e529be9121?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -39,7 +39,7 @@ A detailed explanation of each step, with code samples, is provided below:
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST server. You provide the information used to create the session in the body of the request; in this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST server. You provide the information used to create the session in the body of the request; in this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing the authorization token that will be used in subsequent requests.
 
 Sample Request Header:
 
@@ -770,7 +770,7 @@ This endpoint allows the caller to delete the upload session after the dataset i
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user, using the MicroStrategy REST server. You close the active user session by providing the authorization token generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user, using the Strategy REST server. You close the active user session by providing the authorization token generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ### Request
 
diff --git a/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-with-one-request/workflow-create-and-modify-a-dataset-with-one-request.md b/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-with-one-request/workflow-create-and-modify-a-dataset-with-one-request.md
index 0c5beae0e..eaaab3ea5 100644
--- a/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-with-one-request/workflow-create-and-modify-a-dataset-with-one-request.md
+++ b/docs/common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-with-one-request/workflow-create-and-modify-a-dataset-with-one-request.md
@@ -8,7 +8,7 @@ description: The steps below illustrate the workflow for creating and modifying
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-eccc2471-3af4-44c0-b4aa-9c98a1443823?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -37,7 +37,7 @@ A detailed explanation of each step is provided below.
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing X-MSTR-AuthToken, the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing X-MSTR-AuthToken, the authorization token that will be used in subsequent requests.
 
 Sample Request Header:
 
@@ -90,7 +90,7 @@ Response Body: Empty
 
 Endpoint: [POST /api/datasets](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasets/createDICube)
 
-This endpoint allows the caller to create a dataset with the MicroStrategy REST server. You use the authorization token returned in step 1 as the value for `X-MSTR-AuthToken` and a project ID for `X-MSTR-ProjectID`.
+This endpoint allows the caller to create a dataset with the Strategy REST server. You use the authorization token returned in step 1 as the value for `X-MSTR-AuthToken` and a project ID for `X-MSTR-ProjectID`.
 
 The dataset is created from the data in the `body` parameter of the request. The `body` parameter defines the data you want to upload to the Intelligence Server.
 
@@ -358,7 +358,7 @@ A dataset named SALES_TABLE is created under the My Reports folder. The dataset
 
 Endpoint: [PATCH /api/datasets/\{datasetId}/tables/\{tableId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasets/updateDICube)
 
-This endpoint allows the caller to update and republish a dataset that was created by the MicroStrategy REST server (using `POST /api/datasets`). To update and republish a specific dataset, you provide the authorization token, `X-MSTR-AuthToken`, generated in step 1, the dataset ID and table ID to identify the dataset to be updated, the type of update action that should be performed, and the data to be applied. If successful, the resulting HTTP response returns an HTTP status 200.
+This endpoint allows the caller to update and republish a dataset that was created by the Strategy REST server (using `POST /api/datasets`). To update and republish a specific dataset, you provide the authorization token, `X-MSTR-AuthToken`, generated in step 1, the dataset ID and table ID to identify the dataset to be updated, the type of update action that should be performed, and the data to be applied. If successful, the resulting HTTP response returns an HTTP status 200.
 
 Request Parameters
 
@@ -447,7 +447,7 @@ The dataset named SALES_TABLE, under the My Reports folder, is updated and repub
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST server. In this example, you close the active user session by providing the authorization token, X-MSTR-AuthToken, generated in step 1. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST server. In this example, you close the active user session by providing the authorization token, X-MSTR-AuthToken, generated in step 1. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 Sample Request Header:
 
diff --git a/docs/common-workflows/analytics/manage-datasets/make-external-data-available/make-external-data-available.md b/docs/common-workflows/analytics/manage-datasets/make-external-data-available/make-external-data-available.md
index f1335a045..2ce8e6ba8 100644
--- a/docs/common-workflows/analytics/manage-datasets/make-external-data-available/make-external-data-available.md
+++ b/docs/common-workflows/analytics/manage-datasets/make-external-data-available/make-external-data-available.md
@@ -1,23 +1,23 @@
 ---
 title: Make external data available using the Push Data API
-description: The Push Data API, which belongs to the Dataset API family, lets you make external data easily available for analysis in MicroStrategy. You use REST APIs to create and modify datasets using external data uploaded directly to the Intelligence Server.
+description: The Push Data API, which belongs to the Dataset API family, lets you make external data easily available for analysis in Strategy. You use REST APIs to create and modify datasets using external data uploaded directly to the Intelligence Server.
 ---
 
 :::tip
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-724e8a71-2d94-4887-af80-f57d62503f46?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-The Push Data API, which belongs to the Dataset API family, lets you make external data easily available for analysis in MicroStrategy. You use REST APIs to create and modify datasets using external data uploaded directly to the Intelligence Server.
+The Push Data API, which belongs to the Dataset API family, lets you make external data easily available for analysis in Strategy. You use REST APIs to create and modify datasets using external data uploaded directly to the Intelligence Server.
 
-- By providing a simpler, quicker way to get data out and add data back in, the Push Data API makes it easier to use MicroStrategy as a high-performance data storage and retrieval mechanism and supports predictive workflow by machine learning, artificial intelligence, and data scientist teams.
-- The ability to make external data easily available extends MicroStrategy's reach to new and complex data sources where code, rather than end-users, manages the data modeling/mapping flow.
-- The Push Data API supports close integration with the ecosystem of third-party ETL tools because it allows them to push data directly into MicroStrategy while allowing the most optimal utilization of MicroStrategy's cube capabilities. The Push Data API provides these tools, whether they are analyst or IT-oriented, with the option to create and update datasets on the MicroStrategy Intelligence Server without requiring an intermediate step of pushing the data into a warehouse.
+- By providing a simpler, quicker way to get data out and add data back in, the Push Data API makes it easier to use Strategy as a high-performance data storage and retrieval mechanism and supports predictive workflow by machine learning, artificial intelligence, and data scientist teams.
+- The ability to make external data easily available extends Strategy's reach to new and complex data sources where code, rather than end-users, manages the data modeling/mapping flow.
+- The Push Data API supports close integration with the ecosystem of third-party ETL tools because it allows them to push data directly into Strategy while allowing the most optimal utilization of Strategy's cube capabilities. The Push Data API provides these tools, whether they are analyst or IT-oriented, with the option to create and update datasets on the Strategy Intelligence Server without requiring an intermediate step of pushing the data into a warehouse.
 
-When the Push Data API was introduced in MicroStrategy 10.11, it supported only a single table and data was uploaded and published in the same request. This single request workflow works well for small, simple dataset creation scenarios, but a newer multiple request workflow supports more complex scenarios where a large number of columns/metrics need to be managed at a different update/load/refresh schedule. This workflow separates dataset definition, data upload, and dataset creation, using multiple requests to incrementally add data before publication.
+When the Push Data API was introduced in Strategy 10.11, it supported only a single table and data was uploaded and published in the same request. This single request workflow works well for small, simple dataset creation scenarios, but a newer multiple request workflow supports more complex scenarios where a large number of columns/metrics need to be managed at a different update/load/refresh schedule. This workflow separates dataset definition, data upload, and dataset creation, using multiple requests to incrementally add data before publication.
 
 - [Creating a dataset with one request](create-a-dataset-with-one-request/workflow-create-and-modify-a-dataset-with-one-request.md)
 
diff --git a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/create-a-cube-object.md b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/create-a-cube-object.md
index e07627aa3..e98b5598a 100644
--- a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/create-a-cube-object.md
+++ b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/create-a-cube-object.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to create a new cube object t
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-ef6003b3-abe9-40ee-abf7-ff72de088f22?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to create a new cube object through the Modeling service and publish it through Library server.
 
-You want to create a new `Year, Category Analysis` cube object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new `Year, Category Analysis` cube object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -301,7 +301,7 @@ Sample Response Code: 201 (A cube is created successfully.)
 
 <Available since="2021 Update 6" />
 
-You want to create a new `Actual vs Forecast Performance Cube` cube object under the `Public Objects` folder in the `MicroStrategy Tutorial` project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new `Actual vs Forecast Performance Cube` cube object under the `Public Objects` folder in the `Strategy Tutorial` project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 Sample Curl:
 
diff --git a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/manage-cube-objects.md b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/manage-cube-objects.md
index 4d09b5c29..abd6545ae 100644
--- a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/manage-cube-objects.md
+++ b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/manage-cube-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and update cube
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c00a4cc5-d401-4786-8a6d-dba31f6af81f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/retrieve-a-cube-definition.md b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/retrieve-a-cube-definition.md
index dcc45f81f..5ce99778b 100644
--- a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/retrieve-a-cube-definition.md
+++ b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/retrieve-a-cube-definition.md
@@ -10,7 +10,7 @@ description: This topic cover several workflows for retrieving a cube's definiti
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-585d42d1-fbdc-4d1d-afbb-c4e872753709?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -22,7 +22,7 @@ This topic cover several workflows for retrieving a cube's definition.
 
 This workflow sample demonstrates how to retrieve the definition of a cube through the Modeling service.
 
-You want to get the definition of the `Year, Category Analysis` cube object. The object ID of the cube is `A7D792D54B58C6CB68F192A4A73E317F` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `Year, Category Analysis` cube object. The object ID of the cube is `A7D792D54B58C6CB68F192A4A73E317F` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -186,7 +186,7 @@ Response Code: 200 (The cube’s definition was returned successfully.)
 
 This workflow sample demonstrates how to retrieve the definition of a FFSQL cube through the Modeling service.
 
-You want to get the definition of the `Year, Category Analysis` cube object. The object ID of the cube is `A7D792D54B58C6CB68F192A4A73E317F` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `Year, Category Analysis` cube object. The object ID of the cube is `A7D792D54B58C6CB68F192A4A73E317F` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -439,7 +439,7 @@ Response Code: 200 (The cube’s definition was returned successfully.)
 
 This workflow sample demonstrates how to retrieve the definition of a cube with its filter in tokens format through the Modeling service. Unlike the first workflow, you want to enable the `showFilterTokens` parameter to retrieve the filter's definition in tokens format as well.
 
-Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a filter expression is `Revenue > Cost`. When the filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: `("Revenue", Revenue_ID)`, `(">", GreaterThan_ID)`, `("Cost", Cost_ID)`.
+Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a filter expression is `Revenue > Cost`. When the filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: `("Revenue", Revenue_ID)`, `(">", GreaterThan_ID)`, `("Cost", Cost_ID)`.
 
 A filter's "qualification" is presented in the following formats:
 
@@ -631,7 +631,7 @@ In this workflow sample, you want to get the definition cube when its filter con
 
 If custom expressions are used in a filter, this parameter specifies the format in the which they are returned in the response.
 
-Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a filter expression is `Revenue > Cost`. When the filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: `("Revenue", Revenue_ID)`, `(">", GreaterThan_ID)`, `("Cost", Cost_ID)`.
+Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a filter expression is `Revenue > Cost`. When the filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: `("Revenue", Revenue_ID)`, `(">", GreaterThan_ID)`, `("Cost", Cost_ID)`.
 
 A filter's "qualification" is presented in the following formats:
 
@@ -1001,7 +1001,7 @@ Sample Response Code: 200 (Cube’s definition is returned successfully.)
 
 This workflow sample demonstrates how to retrieve the definition of a cube with advanced properties through the Modeling service.
 
-You want to get the definition of the Actual vs Forecast Performance Cube cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the Actual vs Forecast Performance Cube cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 This workflow is similar to [Retrieve a cube definition](#retrieve-a-cubes-definition), except with `showAdvancedProperties=true`.
 
@@ -1142,7 +1142,7 @@ Response Code: 200 (The cube definition is returned successfully.)
 
 This workflow sample demonstrates how to retrieve all the applicable properties of a cube through the Modeling service.
 
-You want to get the applicable properties of the Actual vs Forecast Performance Cube cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD75`4.
+You want to get the applicable properties of the Actual vs Forecast Performance Cube cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD75`4.
 
 Retrieve the applicable properties of a cube using [GET /api/model/cubes/\{cubeId}/applicableVldbProperties](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Cubes/ms-getCubeApplicableVldbProperties).
 
@@ -1173,8 +1173,8 @@ You can view the cube definition in the body of the response. The example below
       "showSqlPreview": true,
       "options": [
         {
-          "value": "Choosing this option keeps the backward compatibility with MicroStrategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
-          "sqlPreview": "OBSOLETE - Keep backward compatibility with MicroStrategy 2019."
+          "value": "Choosing this option keeps the backward compatibility with Strategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
+          "sqlPreview": "OBSOLETE - Keep backward compatibility with Strategy 2019."
         },
         {
           "value": "Cancel execution of cartesian join for SQL, MDX, In-Memory queries.",
diff --git a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/update-a-cube-definition.md b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/update-a-cube-definition.md
index b774788b6..6c3c39466 100644
--- a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/update-a-cube-definition.md
+++ b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/update-a-cube-definition.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to update a cube’s definiti
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-ef6003b3-abe9-40ee-abf7-ff72de088f22?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to update a cube’s definition through the Modeling service and Publish it through Library Server.
 
-You want to update the `Year, Category Analysis` cube object definition in the MicroStrategy Tutorial project. The cube ID is `2F15C95D934175CBC9B915915D485B0E`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the `Year, Category Analysis` cube object definition in the Strategy Tutorial project. The cube ID is `2F15C95D934175CBC9B915915D485B0E`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -302,7 +302,7 @@ Sample Response Code: 200 (The cube's definition is updated successfully.)
 
 <Available since="2021 Update 6" />
 
-You want to update the value of advanced properties of the `Actual vs Forecast Performance Cube` cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the `MicroStrategy Tutorial` project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the value of advanced properties of the `Actual vs Forecast Performance Cube` cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the `Strategy Tutorial` project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 Sample Curl:
 
diff --git a/docs/common-workflows/analytics/manage-documents/get-document-list/get-document-list.md b/docs/common-workflows/analytics/manage-documents/get-document-list/get-document-list.md
index 8dd2596ed..842837bdf 100644
--- a/docs/common-workflows/analytics/manage-documents/get-document-list/get-document-list.md
+++ b/docs/common-workflows/analytics/manage-documents/get-document-list/get-document-list.md
@@ -1,11 +1,11 @@
 ---
 title: Retrieve documents
-Description: Retrieve a list of documents using the MicroStrategy REST API.
+Description: Retrieve a list of documents using the Strategy REST API.
 ---
 
 <Available since="2021 Update 10" />
 
-This workflow sample demonstrates how to retrieve a list of documents using the MicroStrategy REST API.
+This workflow sample demonstrates how to retrieve a list of documents using the Strategy REST API.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-documents/manage-documents.md b/docs/common-workflows/analytics/manage-documents/manage-documents.md
index 4ce73b15b..2e625f449 100644
--- a/docs/common-workflows/analytics/manage-documents/manage-documents.md
+++ b/docs/common-workflows/analytics/manage-documents/manage-documents.md
@@ -1,6 +1,6 @@
 ---
 title: Manage documents
-Description: Manage documents using the MicroStrategy REST API.
+Description: Manage documents using the Strategy REST API.
 ---
 
 <Available since="2021 Update 10" />
diff --git a/docs/common-workflows/analytics/manage-documents/retrieve-document/retrieve-the-hierarchy-of-a-document.md b/docs/common-workflows/analytics/manage-documents/retrieve-document/retrieve-the-hierarchy-of-a-document.md
index beceab2ed..932d9a487 100644
--- a/docs/common-workflows/analytics/manage-documents/retrieve-document/retrieve-the-hierarchy-of-a-document.md
+++ b/docs/common-workflows/analytics/manage-documents/retrieve-document/retrieve-the-hierarchy-of-a-document.md
@@ -1,19 +1,19 @@
 ---
  title: Retrieve the hierarchy of document
- Description: Retrieve the hierarchy of document using the MicroStrategy REST API.
+ Description: Retrieve the hierarchy of document using the Strategy REST API.
 ---
 
  <Available since="2021 Update 10" />
 
 :::tip
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-This workflow sample demonstrates how to retrieve the document definition directly using the MicroStrategy REST API.
+This workflow sample demonstrates how to retrieve the document definition directly using the Strategy REST API.
 
-You want to retrieve the document's definition from “MicroStrategy Tutorial“ project. The document ID is `643209B54CC84199C48A238ACB6CB621`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to retrieve the document's definition from “Strategy Tutorial“ project. The document ID is `643209B54CC84199C48A238ACB6CB621`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-dossiers/create-instance/create-instance.md b/docs/common-workflows/analytics/manage-dossiers/create-instance/create-instance.md
index 7efb530c6..4d3a6dd46 100644
--- a/docs/common-workflows/analytics/manage-dossiers/create-instance/create-instance.md
+++ b/docs/common-workflows/analytics/manage-dossiers/create-instance/create-instance.md
@@ -11,7 +11,7 @@ This workflow sample demonstrates how to create an instance of a dashboard in me
 
 You can try this API with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/request/16131298-c530c47a-845f-4231-b071-2247bd846c66).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/manage-dossiers/manage-dossiers.md b/docs/common-workflows/analytics/manage-dossiers/manage-dossiers.md
index 42f045cdf..10b16cb0a 100644
--- a/docs/common-workflows/analytics/manage-dossiers/manage-dossiers.md
+++ b/docs/common-workflows/analytics/manage-dossiers/manage-dossiers.md
@@ -1,6 +1,6 @@
 ---
 title: Manage dashboards
-Description: Manage dashboards using the MicroStrategy REST API.
+Description: Manage dashboards using the Strategy REST API.
 ---
 
 <Available since="2021 Update 10" />
diff --git a/docs/common-workflows/analytics/manage-insights/get-kpi.md b/docs/common-workflows/analytics/manage-insights/get-kpi.md
index a3c1e0a8d..2e6848631 100644
--- a/docs/common-workflows/analytics/manage-insights/get-kpi.md
+++ b/docs/common-workflows/analytics/manage-insights/get-kpi.md
@@ -488,7 +488,7 @@ KPI in response:
 | content.id                        | The dashboard ID                                                                                                                                                                                                                                                              |
 | content.instanceId                | The instance ID of the dashboard, only required in [POST /api/insight/KPIs](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Insight%20Engine%20-%20KPIs/createKPI)                                                                                   |
 | schedule                          | Internal property, this field can be ignored                                                                                                                                                                                                                                  |
-| hashInfo                          | Used only by MicroStrategy App for cache purposes                                                                                                                                                                                                                             |
+| hashInfo                          | Used only by Strategy App for cache purposes                                                                                                                                                                                                                                  |
 | dataCompares                      | The comparison results according to `compareWith` parameter in URL. Comparisons are performed by the latest data point and the data point specified by indicator. e.g. "1d" compares the data point of the current time with the data point 24 hours before the current time. |
 | dataCompares[*].timestamp         | The timestamp of the data point used for comparison                                                                                                                                                                                                                           |
 | dataCompares[*].indicator         | The comparison indicator                                                                                                                                                                                                                                                      |
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/create-an-irr.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/create-an-irr.md
index 99eb1e229..45311c12d 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/create-an-irr.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/create-an-irr.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a new Incremental R
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-54f5b582-05ac-4f2d-88f9-98f36dd8373c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -598,7 +598,7 @@ The model for the definition of the Incremental Refresh Report can be represente
 
 :::info
 
-`objectID`, `dateCreated`, `dateModified`, and `versionId` are generated automatically. As of MicroStrategy 2021 Update 6, only `en-US` is available for `primaryLocale`.
+`objectID`, `dateCreated`, `dateModified`, and `versionId` are generated automatically. As of Strategy 2021 Update 6, only `en-US` is available for `primaryLocale`.
 
 :::
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/manage-incremental-refresh-report.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/manage-incremental-refresh-report.md
index b7d90693c..29c58b6e6 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/manage-incremental-refresh-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/manage-incremental-refresh-report.md
@@ -9,11 +9,11 @@ description: You can use REST API requests retrieve, create, and update the In
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-bc4cbadd-29e6-4426-85ff-30bcc0f20d60?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-Starting in MicroStrategy 2021 Update 6, you can use REST API requests retrieve, create, and update the Incremental Refresh Report (IRR) objects through the Modeling service.
+Starting in Strategy 2021 Update 6, you can use REST API requests retrieve, create, and update the Incremental Refresh Report (IRR) objects through the Modeling service.
 
 - [Retrieve an IRR definition](retrieve-an-irr-definition.md)
 - [Create an IRR](create-an-irr.md)
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition-with-advanced-properties.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition-with-advanced-properties.md
index 0d0b7bc03..6a1b63326 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition-with-advanced-properties.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition-with-advanced-properties.md
@@ -8,7 +8,7 @@ description: This topic covers several workflows to retrieve the definition for
 
 This topic covers several workflows to retrieve the definition for an Incremental Refresh Report with an advanced property value.
 
-The object ID of the Incremental Refresh Report is  `B17F066940FA684A00C1D9AC5FC95754` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+The object ID of the Incremental Refresh Report is  `B17F066940FA684A00C1D9AC5FC95754` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition.md
index eb4d47780..640f9bc7b 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition.md
@@ -8,7 +8,7 @@ description: This topic covers several workflows to retrieve an Incremental Refr
 
 This topic covers several workflows to retrieve an Incremental Refresh Report definition.
 
-You want to get the definition of the `YearInList_Insert` Incremental Refresh Report object as shown in the below screenshot. The object ID of the Incremental Refresh Report is  `B5905F5C4565159A5AEAF78E71DC8BF6` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `YearInList_Insert` Incremental Refresh Report object as shown in the below screenshot. The object ID of the Incremental Refresh Report is  `B5905F5C4565159A5AEAF78E71DC8BF6` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 ![IRR Report Editor](../../../../images/IRR_report_editor.png)
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-applicable-properties-of-an-incremental-refresh-report.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-applicable-properties-of-an-incremental-refresh-report.md
index b46a07573..30ab62f69 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-applicable-properties-of-an-incremental-refresh-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-applicable-properties-of-an-incremental-refresh-report.md
@@ -8,7 +8,7 @@ description: This workflow sample demonstrates how to retrieve applicable proper
 
 You can use REST APIs to retrieve all the applicable properties of an incremental refresh report through the Modeling service. The workflow includes the following REST APIs requests.
 
-The incremental refresh report object ID is 01234567890123456789012345678912. The incremental refresh report is in the project "MicroStrategy Tutorial", and the project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+The incremental refresh report object ID is 01234567890123456789012345678912. The incremental refresh report is in the project "Strategy Tutorial", and the project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
@@ -57,8 +57,8 @@ Sample Response Body:
       "showSqlPreview": true,
       "options": [
         {
-          "value": "Choosing this option keeps the backward compatibility with MicroStrategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
-          "sqlPreview": "OBSOLETE - Keep backward compatibility with MicroStrategy 2019."
+          "value": "Choosing this option keeps the backward compatibility with Strategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
+          "sqlPreview": "OBSOLETE - Keep backward compatibility with Strategy 2019."
         },
         {
           "value": "Cancel execution of cartesian join for SQL, MDX, In-Memory queries.",
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/update-an-irr-definition.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/update-an-irr-definition.md
index 910843be0..56db2e8d6 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/update-an-irr-definition.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/update-an-irr-definition.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to update an Incremental Refr
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-54f5b582-05ac-4f2d-88f9-98f36dd8373c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-page-by-information.md b/docs/common-workflows/analytics/manage-reports/manage-page-by-information.md
index 013a3df48..8530939ab 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-page-by-information.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-page-by-information.md
@@ -7,7 +7,7 @@ description: You can use REST API requests to manage page-by information for rep
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-244d4021-db1d-4e6d-9b3e-04dd192faa2f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -17,7 +17,7 @@ You can use REST API requests to manage page-by information for reports.
 - [Execute the report and fetch data to apply to the page-by information](#execute-the-report-and-fetch-data-to-apply-to-the-page-by-information)
 - [Update a report instance to modify the current page of page-by(s)](#update-a-report-instance-to-modify-the-current-page-of-page-bys)
 
-The workflows on this page use the Unit Sales Paged report located in the MicroStrategy Tutorial project at **Shared Reports** > **MicroStrategy Platform Capabilities** > **MicroStrategy Office** > **Excel - Self-Service Report Book** > **Paged Report**.
+The workflows on this page use the Unit Sales Paged report located in the Strategy Tutorial project at **Shared Reports** > **Strategy Platform Capabilities** > **Strategy Office** > **Excel - Self-Service Report Book** > **Paged Report**.
 
 ![page_by_report](../../../images/page_by_report.png)
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/create-a-new-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/create-a-new-report.md
index a385f6c8e..a1706ae6f 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/create-a-new-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/create-a-new-report.md
@@ -9,7 +9,7 @@ You can use REST APIs to create a new report through Modeling service. There are
 
 ## Create a new normal report within an instance
 
-In this sample workflow, we want to create a new normal report under the Public Objects/Report folder in the MicroStrategy Tutorial" project. The folder object ID is `D3C7D461F69C4610AA6BAA5EF51F4125`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this sample workflow, we want to create a new normal report under the Public Objects/Report folder in the Strategy Tutorial" project. The folder object ID is `D3C7D461F69C4610AA6BAA5EF51F4125`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/execute-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/execute-report.md
index ede964659..a465133ca 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/execute-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/execute-report.md
@@ -195,7 +195,7 @@ Sample Request Header:
 
 Sample Request Body: Empty
 
-Sample Response Body: See details in [MicroStrategy REST](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Reports/executeReport_1)
+Sample Response Body: See details in [Strategy REST](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Reports/executeReport_1)
 
 Sample Response Code: 200 (Report data has been returned.)
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/manage-report-objects.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/manage-report-objects.md
index 5acd2f0b6..58da41ab8 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/manage-report-objects.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/manage-report-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and update repor
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-37579918-50ac-4383-8187-52d886b82d4b?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-derived-elements-definition-in-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-derived-elements-definition-in-report.md
index c3cf02b44..d74eb0894 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-derived-elements-definition-in-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-derived-elements-definition-in-report.md
@@ -9,7 +9,7 @@ You can use REST APIs to retrieve a derived element’s definition in report thr
 
 ## Retrieve a derived element’s definition within a report instance
 
-In this sample workflow, we want to get the definition of a derived element in report. The report ID is `9B9ADA7F464E63CE0D0B709B03BD9370`. The derived element ID is `EA18C4C1484F06FF47B603A7A0DCA8D6`. The report is in the project "MicroStrategy Tutorial", and the project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this sample workflow, we want to get the definition of a derived element in report. The report ID is `9B9ADA7F464E63CE0D0B709B03BD9370`. The derived element ID is `EA18C4C1484F06FF47B603A7A0DCA8D6`. The report is in the project "Strategy Tutorial", and the project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-reports-definition.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-reports-definition.md
index 14efa606b..18b041ac5 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-reports-definition.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-reports-definition.md
@@ -13,7 +13,7 @@ You can use REST APIs to retrieve the definition of a report through Modeling se
   - [2. Get a report's definition within the instance](#2-get-a-reports-definition-within-the-instance)
   - [3. Delete report instance](#3-delete-report-instance)
 
-In both sample workflows, we want to retrieve a report’s definition from “MicroStrategy Tutorial“ project. The report ID is `FFDAB82F4CA397073ABD4196FCBCD918`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In both sample workflows, we want to retrieve a report’s definition from “Strategy Tutorial“ project. The report ID is `FFDAB82F4CA397073ABD4196FCBCD918`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-applicable-properties-of-a-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-applicable-properties-of-a-report.md
index 392fd2864..aea0d12e6 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-applicable-properties-of-a-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-applicable-properties-of-a-report.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to retrieve applicable proper
 
 You can use REST APIs to retrieve all the applicable properties of a report through the Modeling service. The workflow includes the following REST APIs requests.
 
-The report object ID is `E472644E4239AD7EFDBD869600C93E4D`. The report is in the project "MicroStrategy Tutorial", and the project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+The report object ID is `E472644E4239AD7EFDBD869600C93E4D`. The report is in the project "Strategy Tutorial", and the project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 ## Retrieve applicable properties of a report directly
 
@@ -45,8 +45,8 @@ Sample Response Body:
       "showSqlPreview": true,
       "options": [
         {
-          "value": "Choosing this option keeps the backward compatibility with MicroStrategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
-          "sqlPreview": "OBSOLETE - Keep backward compatibility with MicroStrategy 2019."
+          "value": "Choosing this option keeps the backward compatibility with Strategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
+          "sqlPreview": "OBSOLETE - Keep backward compatibility with Strategy 2019."
         },
         {
           "value": "Cancel execution of cartesian join for SQL, MDX, In-Memory queries.",
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/update-the-definition-of-an-existing-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/update-the-definition-of-an-existing-report.md
index f05613700..4b5c51a91 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/update-the-definition-of-an-existing-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/update-the-definition-of-an-existing-report.md
@@ -9,7 +9,7 @@ You can use REST APIs to update an existing report object through Modeling servi
 
 ## Update the definition of an existing report
 
-In this sample workflow, we want to update an existing report object "New Normal Report" (report ID: `FB7816D149C8AC0573CC55829E56F217`) in project "Microstrategy Tutorial" (project ID: `B19DEDCC11D4E0EFC000EB9495D0F44F`), we have just created it in Workflow Sample: Create a New Report.
+In this sample workflow, we want to update an existing report object "New Normal Report" (report ID: `FB7816D149C8AC0573CC55829E56F217`) in project "Strategy Tutorial" (project ID: `B19DEDCC11D4E0EFC000EB9495D0F44F`), we have just created it in Workflow Sample: Create a New Report.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/manage-transaction-report-objects.md b/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/manage-transaction-report-objects.md
index 52f00710d..892d4cedb 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/manage-transaction-report-objects.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/manage-transaction-report-objects.md
@@ -9,11 +9,11 @@ description: You can use REST API requests to retrieve, create, and update the
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-f0b4a18d-227b-4f84-b000-92d56e8fcf9b?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-Starting in MicroStrategy 2021 Update 8, you can use REST API requests to retrieve, create, and update the transaction reports.
+Starting in Strategy 2021 Update 8, you can use REST API requests to retrieve, create, and update the transaction reports.
 
 Transaction reports can be used to write-back data to the datasource. Similar to FFSQL reports, you can map an attribute form or a metric to a column of a table in the datasource. These columns will be updated once you start the transaction.
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/retrieve-transaction-report-definition.md b/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/retrieve-transaction-report-definition.md
index a357d6034..52d319668 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/retrieve-transaction-report-definition.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/retrieve-transaction-report-definition.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to retrieve a transaction rep
 
 This workflow sample demonstrates how to retrieve an existing transaction report's definition.
 
-You want to get the definition of the "Insert Sales Opportunity Action" transaction report. The object ID of the transaction report is `34D6AC79420AF8365B176480D411C3A9` in the "MicroStrategy Tutorial" project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You also need to fetch authorization token to send correct request.
+You want to get the definition of the "Insert Sales Opportunity Action" transaction report. The object ID of the transaction report is `34D6AC79420AF8365B176480D411C3A9` in the "Strategy Tutorial" project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You also need to fetch authorization token to send correct request.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-selectors/manage-selectors.md b/docs/common-workflows/analytics/manage-selectors/manage-selectors.md
index f3a10b55e..366474a01 100644
--- a/docs/common-workflows/analytics/manage-selectors/manage-selectors.md
+++ b/docs/common-workflows/analytics/manage-selectors/manage-selectors.md
@@ -1,9 +1,9 @@
 ---
 title: Manage selectors
-description: The MicroStrategy RESTful server supports different types of selectors, similar to the function in MicroStrategy Library Web.
+description: The Strategy RESTful server supports different types of selectors, similar to the function in Strategy Library Web.
 ---
 
-The MicroStrategy RESTful server supports different types of selectors, similar to the function in MicroStrategy Library Web.
+The Strategy RESTful server supports different types of selectors, similar to the function in Strategy Library Web.
 
 The following five selector types are supported:
 
@@ -34,9 +34,9 @@ The existing setting dashboard filter API is shown below. However, it is suggest
 
 The following section outlines a summary of the compatibility.
 
-### Compatibility prior to MicroStrategy 2021 Update 1
+### Compatibility prior to Strategy 2021 Update 1
 
-For library versions prior to MicroStrategy 2021 Update 1:
+For library versions prior to Strategy 2021 Update 1:
 
 - The behavior remains the same for all Intelligence Server versions.
 - The expected behavior for the GET Filter API is that the fetched filter definition json returns the chapter-level selector key, name, and summary.
@@ -44,11 +44,11 @@ For library versions prior to MicroStrategy 2021 Update 1:
   - Attribute element list filter
   - Metric qualification selector
 
-### Compatibility on and after MicroStrategy 2021 Update 1
+### Compatibility on and after Strategy 2021 Update 1
 
-For library versions on and after MicroStrategy 2021 Update 1, the behavior changes based on the Intelligence Server version.
+For library versions on and after Strategy 2021 Update 1, the behavior changes based on the Intelligence Server version.
 
-- For Intelligence Server versions prior to MicroStrategy 2021 Update 1
+- For Intelligence Server versions prior to Strategy 2021 Update 1
   - The expected behavior for the GET filter API is that the fetched filter definition json is missing information for visualization as filter and dataset name for dataset. Returns the definition of the following selector types:
     - Attribute element list selector
     - Attribute qualification selector
@@ -60,7 +60,7 @@ For library versions on and after MicroStrategy 2021 Update 1, the behavior chan
     - Metric qualification selector
     - Object replacement selector(Attribute/metric selector)
     - Visualization as filter
-- For Intelligence Server versions on and after MicroStrategy 2021 Update 1
+- For Intelligence Server versions on and after Strategy 2021 Update 1
   - The expected behavior for the GET filter API is that the fetched filter definition json is complete and returns the definition of the following selector types:
     - Attribute element list selector
     - Attribute qualification selector
diff --git a/docs/common-workflows/analytics/object-discovery/data-lineage-analysis-via-rest-apis.md b/docs/common-workflows/analytics/object-discovery/data-lineage-analysis-via-rest-apis.md
index 8a93d54dd..53d6337cf 100644
--- a/docs/common-workflows/analytics/object-discovery/data-lineage-analysis-via-rest-apis.md
+++ b/docs/common-workflows/analytics/object-discovery/data-lineage-analysis-via-rest-apis.md
@@ -9,13 +9,13 @@ description: The metadata is used in object management use cases, such as editin
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-e42edf07-9e68-4cc2-9eb9-a16ad920bb49?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 The metadata is used in object management use cases, such as editing a metric to use a different fact object. In such a use case, the user needs to understand how an object is used and where it comes from. To do so, the user can use a data lineage or data traceability function. Here, we can use search API to perform data lineage analysis on the metadata.
 
-There are two functions that MicroStrategy data lineage supports:
+There are two functions that Strategy data lineage supports:
 
 - Given an object, for example a report, attribute, dashboard, or database, list the direct and indirect components of that object
 - Given an object, list the objects which directly and indirectly depend on that object
diff --git a/docs/common-workflows/analytics/object-discovery/folder-browsing.md b/docs/common-workflows/analytics/object-discovery/folder-browsing.md
index b64689517..677558b8a 100644
--- a/docs/common-workflows/analytics/object-discovery/folder-browsing.md
+++ b/docs/common-workflows/analytics/object-discovery/folder-browsing.md
@@ -8,7 +8,7 @@ description: The workflow for browsing folders in the metadata includes the foll
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-01bcf62f-9d6f-4ddf-9f63-064d875ddae2?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -27,7 +27,7 @@ A detailed explanation of each step is provided below:
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
 
 ![swagger_POST_auth_login](../../../images/swagger_POST_auth_login.png)
 
@@ -86,7 +86,7 @@ Sample Response
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the MicroStrategy REST server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for the header parameter, `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for the header parameter, `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 ![swagger_GET_projects](../../../images/swagger_GET_projects.png)
 
@@ -117,9 +117,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "alias": "",
-      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -140,7 +140,7 @@ The response body contains information for each project that is returned, includ
 
 Endpoint: [GET /api/folders/preDefined/\{folderType}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Browsing/getPreDefinedFolder)
 
-This endpoint allows the caller to get the objects under a predefined folder with the MicroStrategy REST server. In this example, you get the objects under "Shared Reports" in the "MicroStrategy Tutorial" project. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for `folderType` from the [EnumDSSXMLFolderNames](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLFolderNames.html) enumeration. In this example, you use the value "7" , which specifies the predefined "Shared Reports" folder under the "Public Objects" folder. If the call is successful, the resulting HTTP response returns an HTTP status 200 and a list of metadata objects under the "Shared Reports" folder.
+This endpoint allows the caller to get the objects under a predefined folder with the Strategy REST server. In this example, you get the objects under "Shared Reports" in the "Strategy Tutorial" project. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for `folderType` from the [EnumDSSXMLFolderNames](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLFolderNames.html) enumeration. In this example, you use the value "7" , which specifies the predefined "Shared Reports" folder under the "Public Objects" folder. If the call is successful, the resulting HTTP response returns an HTTP status 200 and a list of metadata objects under the "Shared Reports" folder.
 
 ![swagger_GET_folders_preDefined](../../../images/swagger_GET_folders_preDefined.png)
 
@@ -170,7 +170,7 @@ Sample Response
 
 - Response Body
 
-  You can find detail definitions of each parameter in the Response body for this endpoint on the MicroStrategy REST API Explorer page, under Response Class -> Model.
+  You can find detail definitions of each parameter in the Response body for this endpoint on the Strategy REST API Explorer page, under Response Class -> Model.
 
   ```json
     {
@@ -219,10 +219,10 @@ Sample Response
       }
     },
     {
-      "name": "MicroStrategy Platform Capabilities",
+      "name": "Strategy Platform Capabilities",
       "id": "D64C532E4E7FBA74D29A7CA3576F39CF",
       "type": 8,
-      "description": "This folder contains examples of many of the sophisticated capabilities within the MicroStrategy platform.",
+      "description": "This folder contains examples of many of the sophisticated capabilities within the Strategy platform.",
       "subtype": 2048,
       "dateCreated": "2006-05-23T04:55:20.000-0400",
       "dateModified": "2012-05-17T05:00:38.000-0400",
@@ -273,7 +273,7 @@ Sample Response
 
 Endpoint: [GET /api/folders/preDefined?folderType=\{folderType}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Browsing/getPreDefinedFolders)
 
-This endpoint allows the caller to get the folder object of one or more predefined folders with the MicroStrategy REST server. In this example, you get the "Shared Reports" and "My Reports" folder objects in the "MicroStrategy Tutorial" project. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for `folderType` from the [EnumDSSXMLFolderNames](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLFolderNames.html) enumeration. You may specify multiple folder types as a comma separated list. In this example, you use the value "7,20", where "7" specifies the predefined "Shared Reports" folder under the "Public Objects" folder, and "20" specifies the "My Reports" folder under the profile folder of the active user. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the folder objects requested.
+This endpoint allows the caller to get the folder object of one or more predefined folders with the Strategy REST server. In this example, you get the "Shared Reports" and "My Reports" folder objects in the "Strategy Tutorial" project. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for `folderType` from the [EnumDSSXMLFolderNames](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLFolderNames.html) enumeration. You may specify multiple folder types as a comma separated list. In this example, you use the value "7,20", where "7" specifies the predefined "Shared Reports" folder under the "Public Objects" folder, and "20" specifies the "My Reports" folder under the profile folder of the active user. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the folder objects requested.
 
 Sample Request
 
@@ -354,7 +354,7 @@ Sample Response
 
 Endpoint: [GET /api/folders/\{id}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Browsing/getFolder)
 
-This endpoint allows the caller to get the objects under a folder with the MicroStrategy REST server using the folder ID. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for the `id` path parameter with the ID of the folder you want to browse to. In this example, the value "032A5E114A59D28267BDD8B6D9E58B22" is used, which is the ID of the "Business Roles" folder under "Shared Reports" that was returned by [GET /api/folders/preDefined/7](#browse-to-the-shared-reports-folder). If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of metadata objects under the folder.
+This endpoint allows the caller to get the objects under a folder with the Strategy REST server using the folder ID. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for the `id` path parameter with the ID of the folder you want to browse to. In this example, the value "032A5E114A59D28267BDD8B6D9E58B22" is used, which is the ID of the "Business Roles" folder under "Shared Reports" that was returned by [GET /api/folders/preDefined/7](#browse-to-the-shared-reports-folder). If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of metadata objects under the folder.
 
 Sample Request
 
@@ -538,7 +538,7 @@ When calling `GET /api/folders/{id}`, you can use the optional query parameters
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST server. In this example, you close the active user session by providing the `X-MSTR-AuthToken` authorization token generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST server. In this example, you close the active user session by providing the `X-MSTR-AuthToken` authorization token generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ![swagger_POST_auth_logout](../../../images/swagger_POST_auth_logout.png)
 
diff --git a/docs/common-workflows/analytics/object-discovery/search-for-objects.md b/docs/common-workflows/analytics/object-discovery/search-for-objects.md
index cea0a6a56..0d6c3b01c 100644
--- a/docs/common-workflows/analytics/object-discovery/search-for-objects.md
+++ b/docs/common-workflows/analytics/object-discovery/search-for-objects.md
@@ -8,7 +8,7 @@ description: The workflow for performing a quick search for specific objects inc
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-52d5eba3-f23a-4853-aa5b-6cc0c38f698d?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -27,7 +27,7 @@ A detailed explanation of each step is provided below:
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing `X-MSTR-AuthToken`, the authorization token that will be used in subsequent requests.
 
 ![swagger_POST_auth_login](../../../images/swagger_POST_auth_login.png)
 
@@ -87,7 +87,7 @@ The authorization token "`x-mstr-authtoken`" is returned in the response header.
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the MicroStrategy REST Server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 ![swagger_GET_projects](../../../images/swagger_GET_projects.png)
 
@@ -118,9 +118,9 @@ Sample Response
        [
          {
            "id": "nllmm5lpmkjdsj4d4etgdikc6c",
-           "name": "MicroStrategy Tutorial",
+           "name": "Strategy Tutorial",
            "alias": "",
-           "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+           "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
            "status": 0
          },
          {
@@ -141,7 +141,7 @@ The response body contains information for each project that is returned, includ
 
 Endpoint: [GET /api/searches/results](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Browsing/doQuickSearch)
 
-This endpoint allows the caller to perform a quick search for specific objects. In this example, you search in the "MicroStrategy Tutorial" project for reports that include "Customer" in the title and then return all results without pagination. You use two different types of parameters—header and query.
+This endpoint allows the caller to perform a quick search for specific objects. In this example, you search in the "Strategy Tutorial" project for reports that include "Customer" in the title and then return all results without pagination. You use two different types of parameters—header and query.
 
 - You identify the project by passing the project ID in the request header.
 - You set the following values using query parameters in the request:
@@ -258,7 +258,7 @@ Sample Response
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST server. In this example, you close the active user session by providing the authorization token, X-MSTR-AuthToken, generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST server. In this example, you close the active user session by providing the authorization token, X-MSTR-AuthToken, generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ![swagger_POST_auth_logout](../../../images/swagger_POST_auth_logout.png)
 
diff --git a/docs/common-workflows/analytics/project-management/manage-project-load-settings-on-server-startup.md b/docs/common-workflows/analytics/project-management/manage-project-load-settings-on-server-startup.md
index 4bf6bb337..1c4771830 100644
--- a/docs/common-workflows/analytics/project-management/manage-project-load-settings-on-server-startup.md
+++ b/docs/common-workflows/analytics/project-management/manage-project-load-settings-on-server-startup.md
@@ -9,7 +9,7 @@ description: A high-level workflow sample for loading project settings at the st
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-a5485e49-f3a6-4f14-bc79-b5c0d716f6db?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -40,7 +40,7 @@ A detailed explanation of each step is provided below.
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the user to authenticate with the MicroStrategy REST Server. You can provide the information used to create the session in the body of the request. In this example, you can use standard authentication, so you need to provide the username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code of 204 and a response header containing X-MSTR-AuthToken. This authorization token is used by all subsequent requests.
+This endpoint allows the user to authenticate with the Strategy REST Server. You can provide the information used to create the session in the body of the request. In this example, you can use standard authentication, so you need to provide the username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code of 204 and a response header containing X-MSTR-AuthToken. This authorization token is used by all subsequent requests.
 
 ### Sample request
 
@@ -76,7 +76,7 @@ pragma: no-cache
 x-mstr-authtoken: 6ksnde5dr2mij718ibouu8fgjj
 cache-control: no-cache, no-store, max-age=0, must-revalidate
 date: Tue22 Sept 2020 17:58:29 GMT
-server: MicroStrategy
+server: Strategy
 expires: 0
 content-type: null
 ```
@@ -114,7 +114,7 @@ This is the response of a clustered Intelligence Server, and thus, contains many
 {
   "projects": {
     "B7CA92F04B9FAE8D941C3E9B7E0CD754": {
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
       "nodes": ["env-220285laio2use1"]
     },
@@ -207,7 +207,7 @@ Response Body:
 {
   "projects": {
     "B7CA92F04B9FAE8D941C3E9B7E0CD754": {
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
       "nodes": ["env-220285laio2use1", "env-220285laio1use1"]
     },
@@ -246,7 +246,7 @@ Response Code: 200 (OK)
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out the authenticated user from the MicroStrategy REST server. In this example, you close the active user session by providing the X-MSTR-AuthToken authorization token, which is generated by `POST /api/auth/login` during [login](#log-in). If the call is successful, the resulting HTTP response returns a HTTP status code of 204.
+This endpoint allows the caller to log out the authenticated user from the Strategy REST server. In this example, you close the active user session by providing the X-MSTR-AuthToken authorization token, which is generated by `POST /api/auth/login` during [login](#log-in). If the call is successful, the resulting HTTP response returns a HTTP status code of 204.
 
 ### Sample request
 
@@ -273,7 +273,7 @@ must-revalidate
 date: Tue22 Sep 2020 04:51:11 GMT
 expires: 0
 pragma: no-cache
-server: MicroStrategy
+server: Strategy
 status: 204
 ```
 
diff --git a/docs/common-workflows/analytics/project-management/manage-project-settings.md b/docs/common-workflows/analytics/project-management/manage-project-settings.md
index 8fec46c09..e71a0f254 100644
--- a/docs/common-workflows/analytics/project-management/manage-project-settings.md
+++ b/docs/common-workflows/analytics/project-management/manage-project-settings.md
@@ -9,7 +9,7 @@ description: A high-level workflow sample for managing project settings is shown
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d30bab86-7c75-4b05-88d2-35ca2091e983?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -19,7 +19,7 @@ A high-level workflow sample for managing project settings is shown below. The s
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the user to authenticate with the MicroStrategy REST Server. You can provide the information used to create the session in the body of the request. In this example, you can use standard authentication, so you need to provide the username and password. If the call is successful, the resulting response returns a status code of 204 and a response header containing X-MSTR-AuthToken. This authorization token is used by all subsequent requests.
+This endpoint allows the user to authenticate with the Strategy REST Server. You can provide the information used to create the session in the body of the request. In this example, you can use standard authentication, so you need to provide the username and password. If the call is successful, the resulting response returns a status code of 204 and a response header containing X-MSTR-AuthToken. This authorization token is used by all subsequent requests.
 
 In the following example, standard authentication uses a username of administrator and a blank password.
 
@@ -58,7 +58,7 @@ Response Code: 204 (Success: No Content)
 
 Endpoint: [GET /api/v2/projects/\{projectId}/settings/config](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getServerSettingProperties)
 
-This endpoint allows the user to retrieve information on all project settings that are available in MicroStrategy REST API. The information includes the setting description, type, options, unit, minimum value, maximum value, and reboot rule. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
+This endpoint allows the user to retrieve information on all project settings that are available in Strategy REST API. The information includes the setting description, type, options, unit, minimum value, maximum value, and reboot rule. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
 
 :::tip
 
@@ -133,7 +133,7 @@ Response Code: 200 (Success: OK)
 
 Endpoint: [GET /api/v2/projects/\{projectId}/settings](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getServerSettings_3)
 
-This endpoint allows you to retrieve all project setting values that are available in MicroStrategy REST API. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
+This endpoint allows you to retrieve all project setting values that are available in Strategy REST API. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
 
 :::tip
 
@@ -285,7 +285,7 @@ Response Code: 200 (Success: OK)
 
 Endpoint: [PUT /api/v2/projects/\{projectId}/settings](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/setAllServerSettings)
 
-This endpoint allows you to access all of the setting values that are available in MicroStrategy REST API. In this endpoint, you must provide a complete list of project settings, which is the different from the `PATCH /api/v2/projects/{projectId}/settings` endpoint. You can find a list of project settings exposed in REST API via `GET /api/v2/projects/{projectId}/settings/config`. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
+This endpoint allows you to access all of the setting values that are available in Strategy REST API. In this endpoint, you must provide a complete list of project settings, which is the different from the `PATCH /api/v2/projects/{projectId}/settings` endpoint. You can find a list of project settings exposed in REST API via `GET /api/v2/projects/{projectId}/settings/config`. You must specify an authorization token in the request header, which can be obtained from `POST /api/auth/login` during [login](#log-in).
 
 :::tip
 
@@ -396,7 +396,7 @@ Response Code: 200 (Success: OK)
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out the authenticated user from the MicroStrategy REST server. In this example, you close the active user session by providing the `X-MSTR-AuthToken` authorization token, which is generated by `POST /api/auth/login`. If the call is successful, the resulting response returns a status code of 204.
+This endpoint allows the caller to log out the authenticated user from the Strategy REST server. In this example, you close the active user session by providing the `X-MSTR-AuthToken` authorization token, which is generated by `POST /api/auth/login`. If the call is successful, the resulting response returns a status code of 204.
 
 ### Sample request
 
diff --git a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-applicable-advanced-properties.md b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-applicable-advanced-properties.md
index f9ec6ebe4..eabb2c40f 100644
--- a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-applicable-advanced-properties.md
+++ b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-applicable-advanced-properties.md
@@ -10,13 +10,13 @@ description: Get applicable properties for a project.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-585d42d1-fbdc-4d1d-afbb-c4e872753709?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to retrieve the applicable properties of a project through Modeling Service.
 
-You want to get the applicable properties of the `MicroStrategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
+You want to get the applicable properties of the `Strategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
 
 :::info
 
@@ -65,8 +65,8 @@ You can view the applicable properties of a project in the body of the response.
       "showSqlPreview": true,
       "options": [
         {
-          "value": "Choosing this option keeps the backward compatibility with MicroStrategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
-          "sqlPreview": "OBSOLETE - Keep backward compatibility with MicroStrategy 2019."
+          "value": "Choosing this option keeps the backward compatibility with Strategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
+          "sqlPreview": "OBSOLETE - Keep backward compatibility with Strategy 2019."
         },
         {
           "value": "Cancel execution of cartesian join for SQL, MDX, In-Memory queries.",
diff --git a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-with-advanced-properties.md b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-with-advanced-properties.md
index 5cd605d24..d8e1b8b02 100644
--- a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-with-advanced-properties.md
+++ b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-with-advanced-properties.md
@@ -9,13 +9,13 @@ description: The workflow involves getting project definition along with its adv
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c3c3e563-696d-45b8-8f65-b02cb1cb394e?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to retrieve project's definition and its advanced properties.
 
-You want to get the advanced properties of the `MicroStrategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
+You want to get the advanced properties of the `Strategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
 
 :::info
 
@@ -60,8 +60,8 @@ You can view project's definition and its advanced properties in the response.
     "primaryLocale": "en-US",
     "objectId": "6851110C470AF40EB46B559D5098F309",
     "subType": "project",
-    "name": "MicroStrategy Tutorial",
-    "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
+    "name": "Strategy Tutorial",
+    "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
   },
   "advancedProperties": {
     "vldbProperties": {
diff --git a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/project-advanced-properties-management.md b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/project-advanced-properties-management.md
index c722ad592..9fa2899b9 100644
--- a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/project-advanced-properties-management.md
+++ b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/project-advanced-properties-management.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to manage project.
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d30bab86-7c75-4b05-88d2-35ca2091e983?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/update-project-advanced-property.md b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/update-project-advanced-property.md
index 7607805a2..a02ced495 100644
--- a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/update-project-advanced-property.md
+++ b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/update-project-advanced-property.md
@@ -9,7 +9,7 @@ description: The workflow involves modifying project's advanced properties value
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-804b24e1-dccb-48c1-bfde-0a132163e409?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -17,7 +17,7 @@ Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/
 
 This workflow sample demonstrates how to update project's advanced property value
 
-You want to get update an advanced property of the `MicroStrategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
+You want to get update an advanced property of the `Strategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
 
 :::info
 
@@ -74,8 +74,8 @@ You can view list of advanced properties including updated property in the respo
     "primaryLocale": "en-US",
     "objectId": "6851110C470AF40EB46B559D5098F309",
     "subType": "project",
-    "name": "MicroStrategy Tutorial",
-    "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
+    "name": "Strategy Tutorial",
+    "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
   },
   "advancedProperties": {
     "vldbProperties": {
@@ -155,8 +155,8 @@ You can view list of advanced properties including updated property in the respo
     "primaryLocale": "en-US",
     "objectId": "6851110C470AF40EB46B559D5098F309",
     "subType": "project",
-    "name": "MicroStrategy Tutorial",
-    "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
+    "name": "Strategy Tutorial",
+    "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
   },
   "advancedProperties": {
     "vldbProperties": {
diff --git a/docs/common-workflows/analytics/question-with-bot-routing-api/ask-question-to-bots-in-the-application.md b/docs/common-workflows/analytics/question-with-bot-routing-api/ask-question-to-bots-in-the-application.md
index c38da92d0..2c3be7ffa 100644
--- a/docs/common-workflows/analytics/question-with-bot-routing-api/ask-question-to-bots-in-the-application.md
+++ b/docs/common-workflows/analytics/question-with-bot-routing-api/ask-question-to-bots-in-the-application.md
@@ -4,7 +4,7 @@ title: Ask a question with bot routing
 description: This workflow sample demonstrates how to ask a question with bot routing.
 ---
 
-<Available since="MicroStrategy ONE (June 2024)" />
+<Available since="Strategy ONE (June 2024)" />
 
 Use this API to identify the most suitable bot to answer your question based on the application, content group, and specific bots.
 
diff --git a/docs/common-workflows/analytics/question-with-bot-routing-api/ask-suggested-question-to-bots-in-the-application.md b/docs/common-workflows/analytics/question-with-bot-routing-api/ask-suggested-question-to-bots-in-the-application.md
index 7100eda6f..c9eb76599 100644
--- a/docs/common-workflows/analytics/question-with-bot-routing-api/ask-suggested-question-to-bots-in-the-application.md
+++ b/docs/common-workflows/analytics/question-with-bot-routing-api/ask-suggested-question-to-bots-in-the-application.md
@@ -4,7 +4,7 @@ title: Ask suggested questions with bot routing
 description: This workflow sample demonstrates how to ask suggested questions with bot routing.
 ---
 
-<Available since="MicroStrategy ONE (June 2024)" />
+<Available since="Strategy ONE (June 2024)" />
 
 This workflow sample demonstrates how to ask suggested questions with bot routing.
 
diff --git a/docs/common-workflows/analytics/question-with-bot-routing-api/get-image-of-answer.md b/docs/common-workflows/analytics/question-with-bot-routing-api/get-image-of-answer.md
index 4f2611c4a..4eef3efd0 100644
--- a/docs/common-workflows/analytics/question-with-bot-routing-api/get-image-of-answer.md
+++ b/docs/common-workflows/analytics/question-with-bot-routing-api/get-image-of-answer.md
@@ -4,7 +4,7 @@ title: Get an image of an answer related to a question with bot routing
 description: This workflow sample demonstrates how to get an image of an answer related to a question with bot routing.
 ---
 
-<Available since="MicroStrategy ONE (June 2024)" />
+<Available since="Strategy ONE (June 2024)" />
 
 This workflow sample demonstrates how to get an image of an answer related to a question with bot routing.
 
diff --git a/docs/common-workflows/analytics/question-with-bot-routing-api/get-question-from-bots-in-the-application.md b/docs/common-workflows/analytics/question-with-bot-routing-api/get-question-from-bots-in-the-application.md
index 8e5418c6b..fd7a25d92 100644
--- a/docs/common-workflows/analytics/question-with-bot-routing-api/get-question-from-bots-in-the-application.md
+++ b/docs/common-workflows/analytics/question-with-bot-routing-api/get-question-from-bots-in-the-application.md
@@ -4,7 +4,7 @@ title: Get a question with bot routing
 description: This workflow sample demonstrates how to get a question with bot routing.
 ---
 
-<Available since="MicroStrategy ONE (June 2024)" />
+<Available since="Strategy ONE (June 2024)" />
 
 This workflow sample demonstrates how to get a question with bot routing.
 
diff --git a/docs/common-workflows/analytics/question-with-bot-routing-api/question-api.md b/docs/common-workflows/analytics/question-with-bot-routing-api/question-api.md
index f82316690..1508c030c 100644
--- a/docs/common-workflows/analytics/question-with-bot-routing-api/question-api.md
+++ b/docs/common-workflows/analytics/question-with-bot-routing-api/question-api.md
@@ -3,7 +3,7 @@ title: Question with Bot Routing APIs
 description: This page contains a summary of REST APIs for the "questions" endpoint. You can use REST API requests to ask question with bot routing.
 ---
 
-<Available since="MicroStrategy ONE (June 2024)" />
+<Available since="Strategy ONE (June 2024)" />
 
 With our newly added question with bot routing APIs, you can inquire all bots within the entire application without the need to manually identify the appropriate bot. The API automatically determines the most suitable bot to address your questions. Additionally, you have the option to specify the search scope using content groups and bot IDs for more accurate responses.
 
diff --git a/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md b/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md
index c0d873fe9..e080e6dc0 100644
--- a/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md
+++ b/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md
@@ -1,20 +1,20 @@
 ---
 title: Retrieve data from the Intelligence Server using the JSON Data API
-description: You can use the Reports API, the Cubes API and the Dashboards API to retrieve definitions and data from the Intelligence Server. Together, they are often referred to as the JSON Data API. They are part of the MicroStrategy REST Server, which is shipped inside the "MicroStrategyLibrary.war" web application.
+description: You can use the Reports API, the Cubes API and the Dashboards API to retrieve definitions and data from the Intelligence Server. Together, they are often referred to as the JSON Data API. They are part of the Strategy REST Server, which is shipped inside the "StrategyLibrary.war" web application.
 ---
 
 :::tip
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-7b08f07c-89d2-4c61-8bc1-83cee2eb2eaf?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-You can use the Reports API, the Cubes API and the Dashboards API to retrieve definitions and data from the Intelligence Server. Together, they are often referred to as the JSON Data API. They are part of the MicroStrategy REST Server, which is shipped inside the `MicroStrategyLibrary.war` web application.
+You can use the Reports API, the Cubes API and the Dashboards API to retrieve definitions and data from the Intelligence Server. Together, they are often referred to as the JSON Data API. They are part of the Strategy REST Server, which is shipped inside the `StrategyLibrary.war` web application.
 
 :::tip
 
-Prior to MicroStrategy 10.10, there was a standalone server called the JSON Data API Server, which was deployed as an executable jar file. This standalone server has been deprecated.
+Prior to Strategy 10.10, there was a standalone server called the JSON Data API Server, which was deployed as an executable jar file. This standalone server has been deprecated.
 
 :::
diff --git a/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/workflow-retrieve-data-from-the-intelligence-server.md b/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/workflow-retrieve-data-from-the-intelligence-server.md
index d2986df7e..90f4aa0b6 100644
--- a/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/workflow-retrieve-data-from-the-intelligence-server.md
+++ b/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/workflow-retrieve-data-from-the-intelligence-server.md
@@ -8,7 +8,7 @@ description: You can use REST APIs to retrieve both the definition and data for
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-84db2127-16e8-4fd2-909f-b5990516f889?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -36,7 +36,7 @@ To make it easy for you to try out this workflow in your environment, we have pr
 
 Endpoint: [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin)
 
-This endpoint allows the caller to authenticate with the MicroStrategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing X-MSTR-AuthToken, the authorization token that will be used in subsequent requests.
+This endpoint allows the caller to authenticate with the Strategy REST Server. You provide the information used to create the session in the body of the request. In this example, you use standard authentication so you need to provide username, password, and loginMode (which specifies the authentication mode to use). If you omit an optional field, the REST Server uses the default value. If the call is successful, the resulting HTTP response returns an HTTP status code 204 and a response header containing X-MSTR-AuthToken, the authorization token that will be used in subsequent requests.
 
 ![swagger_POST_auth_login](../../../images/swagger_POST_auth_login.png)
 
@@ -106,12 +106,12 @@ A detailed explanation of how to retrieve the definition of a report, cube, or d
 
 Endpoint: [GET /api/reports/\{reportId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Reports/getDefinition_1)
 
-This endpoint returns the definition for a specific report in a specific project from the MicroStrategy Intelligence Server. The body of the response contains the name and ID for the report and all the attributes and metrics included in the report.
+This endpoint returns the definition for a specific report in a specific project from the Strategy Intelligence Server. The body of the response contains the name and ID for the report and all the attributes and metrics included in the report.
 
 - Identify the project by passing the project ID in the request header.
 - Identify the report by passing the report ID in the path of the request.
 
-In the sample provided, you get the definition for the report “01 Basic Report” in the “MicroStrategy Tutorial” project. This report has two attributes and three metrics.
+In the sample provided, you get the definition for the report “01 Basic Report” in the “Strategy Tutorial” project. This report has two attributes and three metrics.
 
 ![GET_report_definition](../../../images/GET_report_definition.png)
 
@@ -217,12 +217,12 @@ Response Code: 204 (Success: No Content)
 
 Endpoint: [GET /api/cubes/\{cubeId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Cubes/getDefinition)
 
-This endpoint returns the definition for a specific cube in a specific project from the MicroStrategy Intelligence Server. The body of the response contains the name and ID for the cube and all the attributes and metrics included in the cube definition.
+This endpoint returns the definition for a specific cube in a specific project from the Strategy Intelligence Server. The body of the response contains the name and ID for the cube and all the attributes and metrics included in the cube definition.
 
 - Identify the project by passing the project ID in the request header.
 - Identify the cube by passing the cube ID in the path of the request.
 
-In the sample provided, you get the definition for the cube “Advanced sort" in the “MicroStrategy Tutorial” project. This cube has two attributes and two metrics.
+In the sample provided, you get the definition for the cube “Advanced sort" in the “Strategy Tutorial” project. This cube has two attributes and two metrics.
 
 ![GET_cube_definition](../../../images/GET_cube_definition.png)
 
@@ -311,12 +311,12 @@ Response Code: 204 (Success: No Content)
 
 Endpoint: [GET /api/dossiers/\{dossierId}/definition](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Dossiers%20and%20Documents/getVisualizationList)
 
-This endpoint returns the hierarchy for a specific dashboard in a specific project from the MicroStrategy Intelligence Server. The body of the response contains the chapters, pages, and visualizations in the dashboard.
+This endpoint returns the hierarchy for a specific dashboard in a specific project from the Strategy Intelligence Server. The body of the response contains the chapters, pages, and visualizations in the dashboard.
 
 - Identify the project by passing the project ID in the request header.
 - Identify the dashboard by passing the dashboard ID in the path of the request.
 
-In the sample provided, you get the hierarchy for the dashboard “Dossier of Advanced sort" in the “MicroStrategy Tutorial” project. This dashboard has one chapter, one page, and one visualization.
+In the sample provided, you get the hierarchy for the dashboard “Dossier of Advanced sort" in the “Strategy Tutorial” project. This dashboard has one chapter, one page, and one visualization.
 
 ![GET_dossier_hierarchy](../../../images/GET_dossier_hierarchy.png)
 
@@ -394,14 +394,14 @@ When you create a report or cube instance using a POST request, the instance ID
 
 Endpoint: [POST /api/reports/\{reportId}/instances](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Reports/createReportInstance)
 
-This endpoint creates a new instance of a specific report in a specific project on the MicroStrategy Intelligence Server and returns the results if processing has finished. You can refine the amount of data that is returned using offset and limit parameters in the request and specifying filtering parameters in the body of the request. You can check whether processing has finished by checking the value of status in the body of the request.
+This endpoint creates a new instance of a specific report in a specific project on the Strategy Intelligence Server and returns the results if processing has finished. You can refine the amount of data that is returned using offset and limit parameters in the request and specifying filtering parameters in the body of the request. You can check whether processing has finished by checking the value of status in the body of the request.
 
 - Identify the project by passing the project ID in the request header.
 - Identify the report by passing the report ID in the path of the request.
 
 :::tip
 
-In the sample that was provided, you create an instance of the report “01 Basic Report” in the “MicroStrategy Tutorial” project. This report has two attributes and three metrics.
+In the sample that was provided, you create an instance of the report “01 Basic Report” in the “Strategy Tutorial” project. This report has two attributes and three metrics.
 
 :::
 
@@ -661,12 +661,12 @@ Response Code: 204 (Success: OK)
 
 Endpoint: [POST /api/cubes/\{cubeId}/instances](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Cubes/createCubeInstance)
 
-This endpoint creates a new instance of a specific cube in a specific project on the MicroStrategy Intelligence Server and returns the results if processing has finished. You can refine the amount of data that is returned using offset and limit parameters in the request and specifying filtering parameters in the body of the request. You can check whether processing has finished by checking the value of status in the body of the request.
+This endpoint creates a new instance of a specific cube in a specific project on the Strategy Intelligence Server and returns the results if processing has finished. You can refine the amount of data that is returned using offset and limit parameters in the request and specifying filtering parameters in the body of the request. You can check whether processing has finished by checking the value of status in the body of the request.
 
 - Identify the project by passing the project ID in the request header.
 - Identify the cube by passing the cube ID in the path of the request.
 
-  In sample that was provided, you create an instance of the cube “Advanced Sort” in the “MicroStrategy Tutorial” project. This cube has two attributes and two metrics.
+  In sample that was provided, you create an instance of the cube “Advanced Sort” in the “Strategy Tutorial” project. This cube has two attributes and two metrics.
 
 - Identity the start and end position as offset and limit request parameters
 
@@ -859,9 +859,9 @@ Response Code: 204 (Success: OK)
 
 Endpoint: [POST /api/dossiers/\{dossierId}/instances](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Dossiers%20and%20Documents/createDossierInstance_2)
 
-This endpoint allows the caller to create a new instance of a specific dashboard in a specific project from the MicroStrategy Intelligence Server. The request body contains linking and bookmark information for the dashboard. The body of the response contains the instance ID for the dashboard and the status.
+This endpoint allows the caller to create a new instance of a specific dashboard in a specific project from the Strategy Intelligence Server. The request body contains linking and bookmark information for the dashboard. The body of the response contains the instance ID for the dashboard and the status.
 
-In the sample that was provided, you create an instance of the dashboard “Dossier for Advanced sort” in the “MicroStrategy Tutorial” project. This dashboard has two attributes and two metrics.
+In the sample that was provided, you create an instance of the dashboard “Dossier for Advanced sort” in the “Strategy Tutorial” project. This dashboard has two attributes and two metrics.
 
 ![POST_dossier_instance](../../../images/POST_dossier_instance.png)
 
@@ -906,12 +906,12 @@ For dashboards, you can retrieve only data for a specific visualization in the d
 
 Endpoint: [GET /api/reports/\{reportId}/instances/\{instanceId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Reports/executeReport)
 
-This endpoint gets the data for a specific report instance in a specific project from the MicroStrategy Intelligence Server. The results are determined by the conditions you applied when you created the instance. You can refine the amount of data that is returned using offset and limit parameters in the request.
+This endpoint gets the data for a specific report instance in a specific project from the Strategy Intelligence Server. The results are determined by the conditions you applied when you created the instance. You can refine the amount of data that is returned using offset and limit parameters in the request.
 
 - Identify the project by passing the project ID in the request header.
 - Identify the report instance by passing the report ID and the report instance ID in the path of the request.
 
-  In the downloadable sample that was provided, you get the data for an instance of the report “01 Basic Report” in the “MicroStrategy Tutorial” project. This report has two attributes and three metrics.
+  In the downloadable sample that was provided, you get the data for an instance of the report “01 Basic Report” in the “Strategy Tutorial” project. This report has two attributes and three metrics.
 
 - Identity the start and end position as offset and limit request parameters
   - offset is the start point of your response. For example, if offset=2, it will return the report data beginning with the second record. The default value is 0.
@@ -1045,10 +1045,10 @@ Response Code: 204 (Success: OK)
 
 Endpoint: [GET /api/cubes/\{cubeId}/instances/\{instanceId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Cubes/getReport)
 
-This endpoint gets the data for a specific cube instance in a specific project from the MicroStrategy Intelligence Server. The response body contains the cube data; the results are determined by the conditions you applied when you created the instance. You can refine the amount of data that is returned using offset and limit parameters in the request.
+This endpoint gets the data for a specific cube instance in a specific project from the Strategy Intelligence Server. The response body contains the cube data; the results are determined by the conditions you applied when you created the instance. You can refine the amount of data that is returned using offset and limit parameters in the request.
 
 - Identify the project by passing the project ID in the request header.
-- Identify the cube instance by passing the cube ID and the cube instance ID in the path of the request. In the sample that was provided, you get the data for an instance of the cube “Advanced sort” in the “MicroStrategy Tutorial” project. This cube has two attributes and two metrics.
+- Identify the cube instance by passing the cube ID and the cube instance ID in the path of the request. In the sample that was provided, you get the data for an instance of the cube “Advanced sort” in the “Strategy Tutorial” project. This cube has two attributes and two metrics.
 
 - Identity the start and end position as offset and limit request parameters
   - offset is the start point of your response. For example, if offset=2, it will return the cube data beginning with the second record. The default value is 0.
@@ -1233,13 +1233,13 @@ Response Code: 204 (Success: OK)
 
 ### Get dashboard data (specific visualization)
 
-This endpoint gets dashboard data by visualization for a specific dashboard instance in a specific project from the MicroStrategy Intelligence Server. The response body contains the cube data; the results are determined by the conditions you applied when you created the instance. You can refine the amount of data that is returned using offset and limit parameters in the request.
+This endpoint gets dashboard data by visualization for a specific dashboard instance in a specific project from the Strategy Intelligence Server. The response body contains the cube data; the results are determined by the conditions you applied when you created the instance. You can refine the amount of data that is returned using offset and limit parameters in the request.
 
 - Identify the project by passing the project ID in the request header.
 - Identify the dashboard instance by passing the dashboard ID and the dashboard instance ID in the path of the request.
 - Identify the chapter and visualization by passing the chapter key and visualization key in the path of the request.
 
-  In the sample that was provided, you get the data for a visualization in an instance of the dashboard “Year Cost” in the “MicroStrategy Tutorial” project.
+  In the sample that was provided, you get the data for a visualization in an instance of the dashboard “Year Cost” in the “Strategy Tutorial” project.
 
 - Identity the start and end position as offset and limit request parameters
   - offset is the start point of your response. For example, if offset=2, it will return the report data beginning with the second record. The default value is 0.
@@ -1390,7 +1390,7 @@ Response Code: 204 (Success: OK)
 
 Endpoint: [POST /api/auth/logout](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogout)
 
-This endpoint allows the caller to log out for the authenticated user with the MicroStrategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
+This endpoint allows the caller to log out for the authenticated user with the Strategy REST Server. In this example, you close the active user session by providing the authorization token, `X-MSTR-AuthToken`, generated during login. If the call is successful, the resulting HTTP response returns an HTTP status code 204.
 
 ![swagger_POST_auth_logout](../../../images/swagger_POST_auth_logout.png)
 
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-dataset-sql.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-dataset-sql.md
index 0c4b2bf1e..3ba3645e6 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-dataset-sql.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-dataset-sql.md
@@ -10,13 +10,13 @@ description: You can retrieve the SQL statements of all datasets in a document o
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-5d5e523d-6a02-45a1-9537-bc0d37f9c10c).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 You can retrieve the SQL statements of all datasets in a document or dashboard instance. In this workflow sample, a dashboard instance is used. However, the same workflow applies to a document instance.
 
-You want to view the SQL statement of every dataset in the Cost Analysis Dashboard in the MicroStrategy Tutorial project. The object ID of the dashboard is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to view the SQL statement of every dataset in the Cost Analysis Dashboard in the Strategy Tutorial project. The object ID of the dashboard is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-grid-or-graph-query-details.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-grid-or-graph-query-details.md
index b4e092bfd..450a45eed 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-grid-or-graph-query-details.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-grid-or-graph-query-details.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to retrieve the query details
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-b0ee6146-bd68-4aae-adfb-ef186d9e26ee?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to retrieve the query details of grids and graphs in a document instance.
 
-You want to view query details of grids and graphs in the Cost Analysis Document in the MicroStrategy Tutorial project. The object ID of the document is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to view query details of grids and graphs in the Cost Analysis Document in the Strategy Tutorial project. The object ID of the document is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-report-or-card-sql.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-report-or-card-sql.md
index 0ecbc76b3..2288ba81d 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-report-or-card-sql.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-report-or-card-sql.md
@@ -10,13 +10,13 @@ description: You can retrieve a report or card instance’s SQL statement. In th
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c962ed90-f4e6-4934-8b65-4480bf45746e?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 You can retrieve a report or card instance’s SQL statement. In this workflow sample, a document with a report object is used. However, the same workflow applies to card objects.
 
-You want to get the definition of the SQL statement from the Cost Analysis Report in the MicroStrategy Tutorial project. The object ID of the report is `CA8E4E2C6F4AC30B0DDE2195998B82DC`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the SQL statement from the Cost Analysis Report in the Strategy Tutorial project. The object ID of the report is `CA8E4E2C6F4AC30B0DDE2195998B82DC`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-sql-statements-and-query-details.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-sql-statements-and-query-details.md
index f63272e49..79b39f938 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-sql-statements-and-query-details.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-sql-statements-and-query-details.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve SQL statements and query
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-fae624de-293e-4c55-9a26-a9ff10d17b3f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-visualization-query-details.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-visualization-query-details.md
index cfc52ef70..0b1d70854 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-visualization-query-details.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-visualization-query-details.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to retrieve the query details
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-5d5e523d-6a02-45a1-9537-bc0d37f9c10c).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to retrieve the query details of visualizations in a dashboard instance.
 
-You want to view the query details of visualizations in the Cost Analysis Dashboard in the MicroStrategy Tutorial project. The object ID of the dashboard is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to view the query details of visualizations in the Cost Analysis Dashboard in the Strategy Tutorial project. The object ID of the dashboard is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/analytics/sort-data.md b/docs/common-workflows/analytics/sort-data.md
index fd1061cf5..47ab8e975 100644
--- a/docs/common-workflows/analytics/sort-data.md
+++ b/docs/common-workflows/analytics/sort-data.md
@@ -7,7 +7,7 @@ description: When you use a REST API request to create a cube or report, you can
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-f01c3304-fd56-48bf-a13a-cae926afb2a5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -63,13 +63,13 @@ You specify a metric whose value is used to sort the report contents. You also p
 
 - Sorting using the default attribute sort
 
-In MicroStrategy Developer, you can set a default attribute sort property, which is saved in the metadata. To set this property, you specify an attribute form whose value will be used to sort the contents of any report that includes the attribute; you also specify whether the sort order will be ascending or descending. This default attribute sort property is automatically applied whenever the attribute is used in a report.
+In Strategy Developer, you can set a default attribute sort property, which is saved in the metadata. To set this property, you specify an attribute form whose value will be used to sort the contents of any report that includes the attribute; you also specify whether the sort order will be ascending or descending. This default attribute sort property is automatically applied whenever the attribute is used in a report.
 
 - If you are creating a report instance that includes an attribute whose form has the default attribute sort property set and it is the only sorting criteria that will be used in the report, you do not have to specify the sort. This is because the default attribute sort is automatically applied whenever the attribute is used in a report.
 
 - If you are creating a report instance that includes an attribute whose form has the default attribute sort property set and it is one of the multiple sorting criteria that is used in the report, you must specify the sort in the hierarchical order where it should be applied. You provide the ID of the attribute. You do not have to specify the attribute form to use or the sort order because they are part of the default attribute sort property.
 
-You cannot set the default attribute sort property in MicroStrategy Web. It can only be set in MicroStrategy Developer.
+You cannot set the default attribute sort property in Strategy Web. It can only be set in Strategy Developer.
 
 ### Sample body parameter
 
diff --git a/docs/common-workflows/analytics/use-bot-api/ask-bot-instance-question.md b/docs/common-workflows/analytics/use-bot-api/ask-bot-instance-question.md
index 3954c4616..66fe137c1 100644
--- a/docs/common-workflows/analytics/use-bot-api/ask-bot-instance-question.md
+++ b/docs/common-workflows/analytics/use-bot-api/ask-bot-instance-question.md
@@ -4,11 +4,11 @@ title: Ask the bot instance a question
 description: This workflow sample demonstrates how to ask the bot instance a question.
 ---
 
-<Available since="MicroStrategy ONE (March 2024)" />
+<Available since="Strategy ONE (March 2024)" />
 
 :::caution
 
-This API is planned for future retirement. Therefore, MicroStrategy recommends that you transition to the [Ask Question to Bots in the Application API](../question-with-bot-routing-api/ask-question-to-bots-in-the-application) for bot-related workflows.
+This API is planned for future retirement. Therefore, Strategy recommends that you transition to the [Ask Question to Bots in the Application API](../question-with-bot-routing-api/ask-question-to-bots-in-the-application) for bot-related workflows.
 
 Using Ask Question to Bots in the Application API:
 
diff --git a/docs/common-workflows/analytics/use-bot-api/ask-bot-instance-suggested-question.md b/docs/common-workflows/analytics/use-bot-api/ask-bot-instance-suggested-question.md
index 5fbf2d433..904cf5553 100644
--- a/docs/common-workflows/analytics/use-bot-api/ask-bot-instance-suggested-question.md
+++ b/docs/common-workflows/analytics/use-bot-api/ask-bot-instance-suggested-question.md
@@ -4,11 +4,11 @@ title: Ask a bot instance for suggested questions
 description: This workflow sample demonstrates how to ask a bot instance for suggested questions
 ---
 
-<Available since="MicroStrategy ONE (March 2024)" />
+<Available since="Strategy ONE (March 2024)" />
 
 :::caution
 
-This API is planned for future retirement. Therefore, MicroStrategy recommends that you transition to the [Ask Suggested Question to Bots in the Application API](../question-with-bot-routing-api/ask-suggested-question-to-bots-in-the-application.md) for retrieving suggested questions from bots.
+This API is planned for future retirement. Therefore, Strategy recommends that you transition to the [Ask Suggested Question to Bots in the Application API](../question-with-bot-routing-api/ask-suggested-question-to-bots-in-the-application.md) for retrieving suggested questions from bots.
 
 Using Ask Suggested Question to Bots in the Application API:
 
diff --git a/docs/common-workflows/analytics/use-bot-api/create-a-bot-instance.md b/docs/common-workflows/analytics/use-bot-api/create-a-bot-instance.md
index d3d26426e..aa69f6fb6 100644
--- a/docs/common-workflows/analytics/use-bot-api/create-a-bot-instance.md
+++ b/docs/common-workflows/analytics/use-bot-api/create-a-bot-instance.md
@@ -4,11 +4,11 @@ title: Create a bot instance
 description: This workflow sample demonstrates how to create a bot instance
 ---
 
-<Available since="MicroStrategy ONE (March 2024)" />
+<Available since="Strategy ONE (March 2024)" />
 
 :::caution
 
-This API is planned for future retirement. Therefore, MicroStrategy recommends that you transition to the [Question with Bot Routing API](../question-with-bot-routing-api/question-api.md) for bot-related workflows.
+This API is planned for future retirement. Therefore, Strategy recommends that you transition to the [Question with Bot Routing API](../question-with-bot-routing-api/question-api.md) for bot-related workflows.
 
 Using the Question with Bot Routing API:
 
diff --git a/docs/common-workflows/analytics/use-bot-api/delete-a-bot-instance.md b/docs/common-workflows/analytics/use-bot-api/delete-a-bot-instance.md
index 18cc6dc95..fc771a596 100644
--- a/docs/common-workflows/analytics/use-bot-api/delete-a-bot-instance.md
+++ b/docs/common-workflows/analytics/use-bot-api/delete-a-bot-instance.md
@@ -4,11 +4,11 @@ title: Delete a bot instance
 description: This workflow sample demonstrates how to delete a bot instance
 ---
 
-<Available since="MicroStrategy ONE (March 2024)" />
+<Available since="Strategy ONE (March 2024)" />
 
 :::caution
 
-This API is planned for future retirement. Therefore, MicroStrategy recommends that you transition to the [Question with Bot Routing API](../question-with-bot-routing-api/question-api.md) for bot-related workflows.
+This API is planned for future retirement. Therefore, Strategy recommends that you transition to the [Question with Bot Routing API](../question-with-bot-routing-api/question-api.md) for bot-related workflows.
 
 Using the Question with Bot Routing API:
 
diff --git a/docs/common-workflows/analytics/use-bot-api/get-a-bot-question.md b/docs/common-workflows/analytics/use-bot-api/get-a-bot-question.md
index af4d3487b..e9e45a7a2 100644
--- a/docs/common-workflows/analytics/use-bot-api/get-a-bot-question.md
+++ b/docs/common-workflows/analytics/use-bot-api/get-a-bot-question.md
@@ -4,11 +4,11 @@ title: Get a bot's question
 description: This workflow sample demonstrates how to get a chat bot's question.
 ---
 
-<Available since="MicroStrategy ONE (March 2024)" />
+<Available since="Strategy ONE (March 2024)" />
 
 :::caution
 
-This API is planned for future retirement. Therefore, MicroStrategy recommends that you transition to the [Get Question from Bots in the Application API](../question-with-bot-routing-api/get-question-from-bots-in-the-application.md) for retrieving bot responses.
+This API is planned for future retirement. Therefore, Strategy recommends that you transition to the [Get Question from Bots in the Application API](../question-with-bot-routing-api/get-question-from-bots-in-the-application.md) for retrieving bot responses.
 
 The Get Question from Bots in the Application API can be used in combination with the [Ask Question to Bots in the Application API](../question-with-bot-routing-api/ask-question-to-bots-in-the-application.md) to ask questions and retrieve answers from bots. This streamlined workflow removes manual bot instance management and provides flexible bot routing.
 
diff --git a/docs/common-workflows/analytics/use-bot-api/get-bot-configuration.md b/docs/common-workflows/analytics/use-bot-api/get-bot-configuration.md
index 72baa0aa9..fd33b9845 100644
--- a/docs/common-workflows/analytics/use-bot-api/get-bot-configuration.md
+++ b/docs/common-workflows/analytics/use-bot-api/get-bot-configuration.md
@@ -4,7 +4,7 @@ title: Get a chat bot's configuration
 description: This workflow sample demonstrates how to get a chat bot's configuration.
 ---
 
-<Available since="MicroStrategy ONE (March 2024)" />
+<Available since="Strategy ONE (March 2024)" />
 
 This workflow sample demonstrates how to get a chat bot's configuration.
 
diff --git a/docs/common-workflows/analytics/use-bot-api/get-bot-question-list.md b/docs/common-workflows/analytics/use-bot-api/get-bot-question-list.md
index 121f8839b..1582e043b 100644
--- a/docs/common-workflows/analytics/use-bot-api/get-bot-question-list.md
+++ b/docs/common-workflows/analytics/use-bot-api/get-bot-question-list.md
@@ -4,7 +4,7 @@ title: Get a bot's question list
 description: This workflow sample demonstrates how to get a chat bot's question list.
 ---
 
-<Available since="MicroStrategy ONE (March 2024)" />
+<Available since="Strategy ONE (March 2024)" />
 
 This workflow sample demonstrates how to get a chat bot's question list.
 
diff --git a/docs/common-workflows/analytics/use-bot-api/use-bot-api.md b/docs/common-workflows/analytics/use-bot-api/use-bot-api.md
index a210f2b3f..37929e1cf 100644
--- a/docs/common-workflows/analytics/use-bot-api/use-bot-api.md
+++ b/docs/common-workflows/analytics/use-bot-api/use-bot-api.md
@@ -3,11 +3,11 @@ title: Bot APIs
 description: This page contains a summary of REST APIs for the "bots" endpoint. You can use REST API requests to consume the chat bots.
 ---
 
-<Available since="MicroStrategy ONE (March 2024)" />
+<Available since="Strategy ONE (March 2024)" />
 
 :::caution
 
-The following Bot APIs are planned for future retirement. Therefore, MicroStrategy recommends that you use the [Question with Bot Routing APIs](../question-with-bot-routing-api/question-api.md) instead:
+The following Bot APIs are planned for future retirement. Therefore, Strategy recommends that you use the [Question with Bot Routing APIs](../question-with-bot-routing-api/question-api.md) instead:
 
 - [Create a bot instance.](./create-a-bot-instance.md)
 - [Ask for suggested questions](./ask-bot-instance-suggested-question.md)
@@ -23,7 +23,7 @@ Reason:
 
 :::
 
-For users interested in creating a custom chatbot experience utilizing the capabilities of MicroStrategy AI, a suite of bot-related APIs is available. These APIs are designed to facilitate seamless integration of MicroStrategy AI into nearly any application. By leveraging these tools, users can enhance their applications with advanced AI features quickly and efficiently. For further details on how to use these APIs, please refer to the following sections of this manual.
+For users interested in creating a custom chatbot experience utilizing the capabilities of Strategy AI, a suite of bot-related APIs is available. These APIs are designed to facilitate seamless integration of Strategy AI into nearly any application. By leveraging these tools, users can enhance their applications with advanced AI features quickly and efficiently. For further details on how to use these APIs, please refer to the following sections of this manual.
 
 - [Get a bot's configuration](./get-bot-configuration.md)
 - [Get a bot question list.](./get-bot-question-list.md)
diff --git a/docs/common-workflows/analytics/use-prompts-objects/answer-prompts.md b/docs/common-workflows/analytics/use-prompts-objects/answer-prompts.md
index 7f206327b..a510e08d5 100644
--- a/docs/common-workflows/analytics/use-prompts-objects/answer-prompts.md
+++ b/docs/common-workflows/analytics/use-prompts-objects/answer-prompts.md
@@ -122,7 +122,7 @@ This endpoint allows the caller to export the document to a PDF file (in the for
 
 You can use REST APIs to provide prompt answers for three types of prompts applied to dashboards, documents, and reports. For these three prompt types, you can provide specific answers to prompts, choose to [use default prompt answers](#use-default-prompt-answers), or [close optional prompts without providing answers](#close-prompts-without-answers). You can also reset the status so that the dashboard, document, or report will be re-prompted the next time it is run.
 
-The prompts supported in the MicroStrategy platform are defined in [EnumDSSXMLPromptType.](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPromptType.html)
+The prompts supported in the Strategy platform are defined in [EnumDSSXMLPromptType.](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPromptType.html)
 
 You use the following REST API endpoints to answer a prompt applied to a dashboard, document, or report:
 
diff --git a/docs/common-workflows/analytics/use-prompts-objects/get-prompt-information/get-prompt-information.md b/docs/common-workflows/analytics/use-prompts-objects/get-prompt-information/get-prompt-information.md
index 205f9f0cd..743cab8e6 100644
--- a/docs/common-workflows/analytics/use-prompts-objects/get-prompt-information/get-prompt-information.md
+++ b/docs/common-workflows/analytics/use-prompts-objects/get-prompt-information/get-prompt-information.md
@@ -6,7 +6,7 @@ title: Get prompt information
 
 You can use REST APIs to get information about five supported types of prompts applied to dashboards, documents, and reports. You can get a list of the prompts that have been applied to a dashboard, document or report, together with the definition of each prompt.
 
-The prompts supported in the MicroStrategy platform are defined in EnumDSSXMLPromptType.
+The prompts supported in the Strategy platform are defined in EnumDSSXMLPromptType.
 
 You can use REST APIs to return information about the following prompts:
 
@@ -20,4 +20,4 @@ You can use REST APIs to return information about the following prompts:
 
 You can identify prompts with the prompt key, prompt ID, or prompt name. If more than one identifier is provided, the logic for identifying the prompt will follow this order: key, ID, name. The prompt key is used first if is available because the key is the only unique value. Since the same prompt can be applied more than once to a dataset, the ID and the name might not be unique. Despite this possibility, the name is often the most convenient way to identify a prompt because of its descriptive nature.
 
-To help you get started using REST APIs to build feature-rich applications that leverage MicroStrategy's prompt capabilities, we have provided a [workflow sample for getting a prompt definition](workflow-get-prompt-information.md).
+To help you get started using REST APIs to build feature-rich applications that leverage Strategy's prompt capabilities, we have provided a [workflow sample for getting a prompt definition](workflow-get-prompt-information.md).
diff --git a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/attribute-element-prompts.md b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/attribute-element-prompts.md
index 4ba83696c..7bb0089b8 100644
--- a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/attribute-element-prompts.md
+++ b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/attribute-element-prompts.md
@@ -9,7 +9,7 @@ description: The attribute element prompt is one of the most commonly used promp
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-5eeb2bce-6951-41c6-aba0-97565505eaa5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/attribute-qualification-prompts.md b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/attribute-qualification-prompts.md
index 0974acd69..ac87a4424 100644
--- a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/attribute-qualification-prompts.md
+++ b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/attribute-qualification-prompts.md
@@ -9,7 +9,7 @@ description: The attribute qualification prompt is a restrictive type prompt tha
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-6fe150ae-169d-441e-8d1d-311c78db3663?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/object-prompts.md b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/object-prompts.md
index dd997d8b7..0262a7350 100644
--- a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/object-prompts.md
+++ b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/object-prompts.md
@@ -9,7 +9,7 @@ description: An object prompt allows the caller to supply a list of objects, suc
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-763d27e2-3d03-47ab-9e7b-6b3b4db736b4?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/prompt-types.md b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/prompt-types.md
index c8245da27..c4774c232 100644
--- a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/prompt-types.md
+++ b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/prompt-types.md
@@ -1,11 +1,11 @@
 ---
 title: Prompt types
-description: There are several different prompt types in the MicroStrategy platform. Each prompt type is defined by a specific set of parameters and corresponds to a value in EnumDSSXMLPromptType.
+description: There are several different prompt types in the Strategy platform. Each prompt type is defined by a specific set of parameters and corresponds to a value in EnumDSSXMLPromptType.
 ---
 
 <Available since="2021 Update 1" />
 
-There are several different prompt types in the MicroStrategy platform. Each prompt type is defined by a specific set of parameters and corresponds to a value in [EnumDSSXMLPromptType](https://www2.microstrategy.com/producthelp/Current/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPromptType.html).
+There are several different prompt types in the Strategy platform. Each prompt type is defined by a specific set of parameters and corresponds to a value in [EnumDSSXMLPromptType](https://www2.microstrategy.com/producthelp/Current/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPromptType.html).
 
 For the following prompt types, you can perform prompt actions supported by REST APIs. This includes getting prompt definitions, providing specific prompt answers, specifying that default prompt answers should be used, closing prompts without supplying answers for optional prompts, or resetting prompts.
 
diff --git a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/value-prompts.md b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/value-prompts.md
index ca90d1e1a..6ab7ef5af 100644
--- a/docs/common-workflows/analytics/use-prompts-objects/prompt-types/value-prompts.md
+++ b/docs/common-workflows/analytics/use-prompts-objects/prompt-types/value-prompts.md
@@ -9,7 +9,7 @@ description: A value prompt allows the results to be filtered based on a specifi
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-30ed13b7-880a-4b38-bdf7-363d868bf70c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/analytics/use-prompts-objects/use-prompts-objects.md b/docs/common-workflows/analytics/use-prompts-objects/use-prompts-objects.md
index 8a99caf9e..8642fe4c2 100644
--- a/docs/common-workflows/analytics/use-prompts-objects/use-prompts-objects.md
+++ b/docs/common-workflows/analytics/use-prompts-objects/use-prompts-objects.md
@@ -1,6 +1,6 @@
 ---
 title: Use prompts objects
-description: Prompts are a platform capability of MicroStrategy that refine the data displayed in reports, documents, and dashboards. The system poses the prompt as a question during execution of a dashboard, document, or report, and the answer determines the data that is returned. A prompt is similar to a filter; both are applied at runtime and customize the results of data that is returned from a data source. The actual prompt definition cannot be changed at runtime, but the answers to the prompt can be changed dynamically. Together with filtering, prompts allow you to build feature-rich applications by leveraging core MicroStrategy platform capabilities.
+description: Prompts are a platform capability of Strategy that refine the data displayed in reports, documents, and dashboards. The system poses the prompt as a question during execution of a dashboard, document, or report, and the answer determines the data that is returned. A prompt is similar to a filter; both are applied at runtime and customize the results of data that is returned from a data source. The actual prompt definition cannot be changed at runtime, but the answers to the prompt can be changed dynamically. Together with filtering, prompts allow you to build feature-rich applications by leveraging core Strategy platform capabilities.
 ---
 
 <Available since="2021 Update 1" />
@@ -9,11 +9,11 @@ description: Prompts are a platform capability of MicroStrategy that refine the
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c22a4c1c-85a3-4f3b-8b34-ffeebd05e795?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-Prompts are a platform capability of MicroStrategy that refine the data displayed in reports, documents, and dashboards. The system poses the prompt as a question during execution of a dashboard, document, or report, and the answer determines the data that is returned. A prompt is similar to a [filter](../filter-data/filter-data.md); both are applied at runtime and customize the results of data that is returned from a data source. The actual prompt definition cannot be changed at runtime, but the answers to the prompt can be changed dynamically. Together with filtering, prompts allow you to build feature-rich applications by leveraging core MicroStrategy platform capabilities.
+Prompts are a platform capability of Strategy that refine the data displayed in reports, documents, and dashboards. The system poses the prompt as a question during execution of a dashboard, document, or report, and the answer determines the data that is returned. A prompt is similar to a [filter](../filter-data/filter-data.md); both are applied at runtime and customize the results of data that is returned from a data source. The actual prompt definition cannot be changed at runtime, but the answers to the prompt can be changed dynamically. Together with filtering, prompts allow you to build feature-rich applications by leveraging core Strategy platform capabilities.
 
 Prompts are applied directly to reports and stored with the dataset for the report. Prompts are applied to dashboards and documents more indirectly. When you use a prompted report as a dataset for a dashboard or document, the prompts stored with the dataset are automatically applied to the document or dashboard.
 
@@ -26,6 +26,6 @@ You can use REST APIs to integrate prompts into your application workflow. You c
 
 :::tip
 
-For general information about prompts, see the [MicroStrategy product help](https://doc-archives.microstrategy.com/producthelp/10.5/basicreporting/webhelp/lang_1033/content/basicreporting/Asking_for_user_input__Prompts.htm#brcreatingquery_2014045409_1076748). For information on using prompts in data displayed on a mobile device, see the MicroStrategy Mobile Design and Administration Guide.
+For general information about prompts, see the [Strategy product help](https://doc-archives.microstrategy.com/producthelp/10.5/basicreporting/webhelp/lang_1033/content/basicreporting/Asking_for_user_input__Prompts.htm#brcreatingquery_2014045409_1076748). For information on using prompts in data displayed on a mobile device, see the Strategy Mobile Design and Administration Guide.
 
 :::
diff --git a/docs/common-workflows/common-workflows.md b/docs/common-workflows/common-workflows.md
index 1a0be6544..aafa45479 100644
--- a/docs/common-workflows/common-workflows.md
+++ b/docs/common-workflows/common-workflows.md
@@ -1,19 +1,19 @@
 ---
 title: Common workflows
-description: The first step in a typical MicroStrategy REST API workflow is authenticating the user and creating a session on the Intelligence Server. When authentication is successful, an authorization token and a session cookie are returned in the response header. The authorization token and the cookie must be provided in every subsequent request. If a browser is handling requests, it will also handle the cookies. However, if you are using your own client, you need to maintain the cookie and include it in further requests, together with the authorization token.
+description: The first step in a typical Strategy REST API workflow is authenticating the user and creating a session on the Intelligence Server. When authentication is successful, an authorization token and a session cookie are returned in the response header. The authorization token and the cookie must be provided in every subsequent request. If a browser is handling requests, it will also handle the cookies. However, if you are using your own client, you need to maintain the cookie and include it in further requests, together with the authorization token.
 ---
 
 :::tip
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/collection/16131298-9ba9a108-18ee-438e-8f4f-df058f265f1b?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-The first step in a typical MicroStrategy REST API workflow is authenticating the user and creating a session on the Intelligence Server. When authentication is successful, an authorization token and a session cookie are returned in the response header. The authorization token and the cookie must be provided in every subsequent request. If a browser is handling requests, it will also handle the cookies. However, if you are using your own client, you need to maintain the cookie and include it in further requests, together with the authorization token.
+The first step in a typical Strategy REST API workflow is authenticating the user and creating a session on the Intelligence Server. When authentication is successful, an authorization token and a session cookie are returned in the response header. The authorization token and the cookie must be provided in every subsequent request. If a browser is handling requests, it will also handle the cookies. However, if you are using your own client, you need to maintain the cookie and include it in further requests, together with the authorization token.
 
-REST API request sequences with descriptions and code samples have been provided for the following common MicroStrategy REST API workflows.
+REST API request sequences with descriptions and code samples have been provided for the following common Strategy REST API workflows.
 
 Our workflows are arranged in 3 sections:
 
diff --git a/docs/common-workflows/modeling/common-object-management/change-ownership.md b/docs/common-workflows/modeling/common-object-management/change-ownership.md
index 652abbc57..c3d61b6d4 100644
--- a/docs/common-workflows/modeling/common-object-management/change-ownership.md
+++ b/docs/common-workflows/modeling/common-object-management/change-ownership.md
@@ -10,7 +10,7 @@ description: Change the owner of an object.
 
 You can try this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-dc9e5266-db8c-4842-9c44-16b5dd614f47).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -233,7 +233,7 @@ You can view the updated owner and access rights information in the body of the
   "viewMedia": 1879072805,
   "ancestors": [
     {
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 3
     },
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-acl.md b/docs/common-workflows/modeling/common-object-management/manage-object-acl.md
index 8a81ff7e2..5a7a97d7a 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-acl.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-acl.md
@@ -7,7 +7,7 @@ description: An Access Control List (ACL) is a set of permissions on objects so
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-638a5542-2f37-4df9-be9a-972a11055db5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -166,7 +166,7 @@ Response Body:
   "extType": 0,
   "ancestors": [
     {
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 2
     },
@@ -266,7 +266,7 @@ Response Body:
   "extType": 0,
   "ancestors": [
     {
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 3
     },
@@ -465,7 +465,7 @@ Response Body:
   "extType": 0,
   "ancestors": [
     {
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 2
     },
@@ -564,7 +564,7 @@ Response Body:
   "extType": 0,
   "ancestors": [
     {
-      "name": "MicroStrategy Tutorial",
+      "name": "Strategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 3
     },
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-translations/manage-object-translations.md b/docs/common-workflows/modeling/common-object-management/manage-object-translations/manage-object-translations.md
index 14c366b87..e54aeae98 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-translations/manage-object-translations.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-translations/manage-object-translations.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, remove, add and update
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d83e2ec3-5b5b-4fb3-8c30-4338db4c0f51?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-translations/remove-add-object-translations.md b/docs/common-workflows/modeling/common-object-management/manage-object-translations/remove-add-object-translations.md
index 82435061d..a887954c0 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-translations/remove-add-object-translations.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-translations/remove-add-object-translations.md
@@ -42,7 +42,7 @@ All params, but the request body are common for both 'add' and 'replace' operati
 
 In this demo following parameter values will be used:
 
-- Project: MicroStrategy Tutorial
+- Project: Strategy Tutorial
 - Project ID: `B7CA92F04B9FAE8D941C3E9B7E0CD754`
 - Object ID: `BEC722A6406320A3E67DBFBAB2F033CB`
 - Object type: `report_definition`
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-translations/retrieve-object-translations.md b/docs/common-workflows/modeling/common-object-management/manage-object-translations/retrieve-object-translations.md
index b1c41afaa..b35389236 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-translations/retrieve-object-translations.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-translations/retrieve-object-translations.md
@@ -25,7 +25,7 @@ Prepare necessary info in order to perform GET operation
 
 In this demo following parameter values will be used:
 
-- Project: MicroStrategy Tutorial
+- Project: Strategy Tutorial
 - Project ID: `B7CA92F04B9FAE8D941C3E9B7E0CD754`
 - Object ID: `BEC722A6406320A3E67DBFBAB2F033CB`
 - Object type: `report_definition`
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-translations/update-object-translations.md b/docs/common-workflows/modeling/common-object-management/manage-object-translations/update-object-translations.md
index 65ce6618d..6e98418b1 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-translations/update-object-translations.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-translations/update-object-translations.md
@@ -36,7 +36,7 @@ Prepare necessary info in order to perform PATCH operation
 
 In this demo, the following parameter values will be used:
 
-- Project: MicroStrategy Tutorial
+- Project: Strategy Tutorial
 - Project ID: `B7CA92F04B9FAE8D941C3E9B7E0CD754`
 - Object ID: `BEC722A6406320A3E67DBFBAB2F033CB`
 - Object type: `report_definition`
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/lock-the-schema.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/lock-the-schema.md
index 1b2c579bf..40af2ad53 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/lock-the-schema.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/lock-the-schema.md
@@ -9,13 +9,13 @@ description: This workflow sample demonstrates how to lock the schema.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c3ac84b3-bce5-495d-94d5-941305fc1def?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to lock the schema.
 
-You want to lock the schema in the MicroStrategy Tutorial project with an `“absolute_individual“` lock. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to lock the schema in the Strategy Tutorial project with an `“absolute_individual“` lock. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/manage-the-schema.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/manage-the-schema.md
index 34dec39e7..723056287 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/manage-the-schema.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/manage-the-schema.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve the schema lock, lock and
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-8f48dce2-e826-4f45-98fb-c3ceed64b670?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-asynchronously.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-asynchronously.md
index 15bd0cf7b..7cb7e733d 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-asynchronously.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-asynchronously.md
@@ -9,7 +9,7 @@ description: This workflow sample demonstrates how to reload (update) the schema
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-edc29ca6-4db8-4a8b-988e-11d9583ed993?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ This workflow sample demonstrates how to reload (update) the schema asynchronous
 1. [Reload (update) the schema asynchronously.](#reload-update-the-schema-asynchronously)
 1. [Check the status of the schema reload (update).](#check-the-status-of-the-schema-reload-update)
 
-You want to reload (update) the schema asynchronously in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to reload (update) the schema asynchronously in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 Get the authorization token needed to execute the request with [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin).
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-synchronously.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-synchronously.md
index eb320d5cd..5d571226c 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-synchronously.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-synchronously.md
@@ -9,13 +9,13 @@ description: This workflow sample demonstrates how to reload (update) the schema
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-b58bf430-4495-4904-8a1c-929a126be1f0?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to reload (update) the schema synchronously.
 
-You want to reload (update) the schema synchronously in the MicroStrategy Tutorial project . The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to reload (update) the schema synchronously in the Strategy Tutorial project . The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/retrieve-the-schema-lock.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/retrieve-the-schema-lock.md
index 884e7d5a1..2f7e32712 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/retrieve-the-schema-lock.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/retrieve-the-schema-lock.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to retrieve the schema lock.
 
 This workflow sample demonstrates how to retrieve the schema lock.
 
-You want to get the schema lock status of the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the schema lock status of the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -51,7 +51,7 @@ Sample Response Body:
 {
   "lockType": "exclusive_constituent",
   "dateCreated": "2021-03-24T01:39:04",
-  "comment": "<COMMENTS><PRODUCT>MicroStrategy Modeling Service</PRODUCT><COMPONENT>MicroStrategy Modeling Service</COMPONENT><LOCKID>E723124CEE0E481FBC8AC539D89C6A67</LOCKID></COMMENTS>",
+  "comment": "<COMMENTS><PRODUCT>Strategy Modeling Service</PRODUCT><COMPONENT>Strategy Modeling Service</COMPONENT><LOCKID>E723124CEE0E481FBC8AC539D89C6A67</LOCKID></COMMENTS>",
   "machineName": "env-247993laiouse1",
   "ownerName": "MSTR User",
   "ownerId": "7FC05A65473CE2FD845CE6A1D3F13233"
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/unlock-the-schema.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/unlock-the-schema.md
index c85ec43b3..bfd8d13ea 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/unlock-the-schema.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/unlock-the-schema.md
@@ -9,13 +9,13 @@ description: This workflow sample demonstrates how to unlock the schema.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c3ac84b3-bce5-495d-94d5-941305fc1def?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to unlock the schema.
 
-You want to unlock the schema in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to unlock the schema in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/create-an-attribute-object.md b/docs/common-workflows/modeling/manage-attribute-objects/create-an-attribute-object.md
index 273303bb4..eb859af4e 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/create-an-attribute-object.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/create-an-attribute-object.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to create an attribute object
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-fc30f1d1-7f8e-4bbb-8f27-7b66c67e6db6?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to create an attribute object through the Modeling service.
 
-You want to create a "Subcategory" attribute object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID of the attribute is `98FE182C2A10427EACE0CD30B6768258` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a "Subcategory" attribute object under the Public Objects folder in the Strategy Tutorial project. The folder object ID of the attribute is `98FE182C2A10427EACE0CD30B6768258` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -44,7 +44,7 @@ To create an attribute, in the request body, "forms" contains the detailed defin
 
 - "expression": Must be in either "tree" or "tokens" format.
 
-  Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
+  Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
 
 - "tables": A list of tables that the "expression" applies to. Warehouse partition base tables and metadata partition mapping tables are not allowed here.
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/get-attribute-applicable-advanced-properties.md b/docs/common-workflows/modeling/manage-attribute-objects/get-attribute-applicable-advanced-properties.md
index 5ab75ac8d..b8340104c 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/get-attribute-applicable-advanced-properties.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/get-attribute-applicable-advanced-properties.md
@@ -10,7 +10,7 @@ description: Get applicable properties for an attribute.
 
 You can try this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-df3dd3da-b225-4637-93dd-c41579ce1074?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/get-attribute-with-advanced-properties.md b/docs/common-workflows/modeling/manage-attribute-objects/get-attribute-with-advanced-properties.md
index a165ba4a4..2c6b60d93 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/get-attribute-with-advanced-properties.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/get-attribute-with-advanced-properties.md
@@ -10,7 +10,7 @@ description: Get attribute definition and advanced properties.
 
 You can try this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-df3dd3da-b225-4637-93dd-c41579ce1074?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/manage-attribute-objects.md b/docs/common-workflows/modeling/manage-attribute-objects/manage-attribute-objects.md
index f0bfe53c0..0dd040494 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/manage-attribute-objects.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/manage-attribute-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create and update attrib
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-df3dd3da-b225-4637-93dd-c41579ce1074?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition-within-a-changeset.md
index 33aaad76d..0a1a7cb82 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve an attribute's de
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-5038d0d2-f112-47fc-b602-e01c58fd8aec?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -22,7 +22,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 :::
 
-You want to get the definition of the "Subcategory" attribute object. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Subcategory" attribute object. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition.md b/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition.md
index b9e58541a..46eb26d31 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve the definition of
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-9a89680f-6695-47d0-b939-4cb8dee003dd?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/
 
 This workflow sample demonstrates how to retrieve the definition of an attribute through the Modeling service.
 
-You want to get the definition of the `"Subcategory"` attribute object. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Subcategory"` attribute object. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -211,7 +211,7 @@ Response Code: 200 (The attribute's definition was returned successfully.)
 
 ## Retrieve an attribute's definition with expressions in tree and tokens formats
 
-In this workflow sample, you want to get the definition of the "`Subcategory`“ attribute object, with the expression returned in tree and tokens formats. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to get the definition of the "`Subcategory`“ attribute object, with the expression returned in tree and tokens formats. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
@@ -221,7 +221,7 @@ Expressions are presented in the following formats:
 - "tree": A tree data structure fully defining the expression. This format can be used if you want to examine and modify the expression programmatically.
 - "tokens": A list of parsed tokens. This format can be used if you want to examine and modify the expression using the parser component. Be aware that generating tokens requires additional time.
 
-  Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
+  Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
 
 If `showExpressionAs` is omitted, the expression is returned in "text" format.
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/update-an-attributes-definition.md b/docs/common-workflows/modeling/manage-attribute-objects/update-an-attributes-definition.md
index 9a05fd55b..ce66dd71e 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/update-an-attributes-definition.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/update-an-attributes-definition.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to update an attribute's defi
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-0c9c449c-883d-4112-af6d-f14656ed5d30?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to update an attribute's definition through the Modeling service.
 
-You want to update the definition of the "Customer" attribute object under the Public Objects folder in the MicroStrategy Tutorial project. The attribute object ID is `5D6C76C3A3F548A0B9ADE5F9D2AA65C6` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the definition of the "Customer" attribute object under the Public Objects folder in the Strategy Tutorial project. The attribute object ID is `5D6C76C3A3F548A0B9ADE5F9D2AA65C6` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -36,7 +36,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 Use [PATCH /api/model/attributes/\{attributeId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Attributes/ms-updateAttribute).
 
-You want to update the definition of the "Customer" attribute object under the Public Objects folder in the MicroStrategy Tutorial project by ungrouping the "Name" form group and adding a new form group "Email". The attribute object ID is `5D6C76C3A3F548A0B9ADE5F9D2AA65C6` in the MicroStrategy Tutorial project.
+You want to update the definition of the "Customer" attribute object under the Public Objects folder in the Strategy Tutorial project by ungrouping the "Name" form group and adding a new form group "Email". The attribute object ID is `5D6C76C3A3F548A0B9ADE5F9D2AA65C6` in the Strategy Tutorial project.
 
 :::tip
 
@@ -46,7 +46,7 @@ To update an attribute, in the request body, "forms" contains the detailed defin
 
   - "expression": Must be in either "tree" or "tokens" format.
 
-    Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say an attribute form expression is "Year - 10". When the attribute form expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Year_ID", Year_column_ID), ("-", Minus_ID), ("10", Constant).
+    Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say an attribute form expression is "Year - 10". When the attribute form expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Year_ID", Year_column_ID), ("-", Minus_ID), ("10", Constant).
 
   - "tables": A list of tables that the "expression" applies to. Warehouse partition base tables and metadata partition mapping tables are not allowed here.
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/update-attribute-advanced-property.md b/docs/common-workflows/modeling/manage-attribute-objects/update-attribute-advanced-property.md
index a994cf817..8dcd01313 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/update-attribute-advanced-property.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/update-attribute-advanced-property.md
@@ -9,7 +9,7 @@ description: The workflow involves modifying attribute's advanced properties val
 
 You can try these workflows at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-df3dd3da-b225-4637-93dd-c41579ce1074?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-attribute-relationships/manage-attribute-relationships.md b/docs/common-workflows/modeling/manage-attribute-relationships/manage-attribute-relationships.md
index 2cfba8a0a..59c4c5952 100644
--- a/docs/common-workflows/modeling/manage-attribute-relationships/manage-attribute-relationships.md
+++ b/docs/common-workflows/modeling/manage-attribute-relationships/manage-attribute-relationships.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create and update an att
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-697327d8-4eaa-48ef-9e75-3daa23d4860f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships-within-a-changeset.md b/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships-within-a-changeset.md
index 00ee2611f..36c3d0905 100644
--- a/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve an attribute's re
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-8b42c446-de96-4899-b3c1-005f25702596?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -26,7 +26,7 @@ Changesets are used in this workflow. For information on how to create and use c
 1. [Get an attribute's relationships within a changeset.](#get-an-attributes-relationships-within-a-changeset)
 1. Delete the changeset.
 
-You want to get the relationships of the `"Month"` attribute object. The object ID of the attribute is `8D679D4411D3E4981000E787EC6DE8A4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the relationships of the `"Month"` attribute object. The object ID of the attribute is `8D679D4411D3E4981000E787EC6DE8A4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -40,7 +40,7 @@ Get the project ID from [GET /api/projects](https://demo.microstrategy.com/Micro
 
 Use [GET /api/model/systemHierarchy/attributes/\{attributeId}/relationships]([https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System) Hierarchy/ms-getAttributeRelationships).
 
-You want to get the relationship of the `"Month"` attribute object. The object ID of the attribute is `8D679D4411D3E4981000E787EC6DE8A4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the relationship of the `"Month"` attribute object. The object ID of the attribute is `8D679D4411D3E4981000E787EC6DE8A4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 Sample Request Header:
 
diff --git a/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships.md b/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships.md
index 7a8599396..bc061526b 100644
--- a/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships.md
+++ b/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to retrieve the relationships
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-063edda6-63ad-4938-ab4c-a4eb8f13d65e?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to retrieve the relationships related to an attribute through the Modeling service.
 
-You want to get the relationships of the "Month" attribute object. The object ID of the attribute is 8D679D4411D3E4981000E787EC6DE8A4 in the MicroStrategy Tutorial project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+You want to get the relationships of the "Month" attribute object. The object ID of the attribute is 8D679D4411D3E4981000E787EC6DE8A4 in the Strategy Tutorial project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-attribute-relationships/update-an-attributes-relationships.md b/docs/common-workflows/modeling/manage-attribute-relationships/update-an-attributes-relationships.md
index 61c7477af..c471a3b95 100644
--- a/docs/common-workflows/modeling/manage-attribute-relationships/update-an-attributes-relationships.md
+++ b/docs/common-workflows/modeling/manage-attribute-relationships/update-an-attributes-relationships.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to update an attribute's rela
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-a1ebd204-40ea-42e0-9ccc-21f391c797fb?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to update an attribute's relationship thro
 1. Commit the changeset.
 1. Delete the changeset.
 
-You want to update the relationship for the `“Subcategory“` attribute object with ID `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the relationship for the `“Subcategory“` attribute object with ID `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -41,7 +41,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 Use [PUT /api/model/systemHierarchy/attributes/\{attributeId}/relationships](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System%20Hierarchy/ms-putAttributeRelationships).
 
-You want to update the relationship of the "Subcategory" attribute object by adding relationships between "Category" and "Subcategory", and "Subcategory" and "Item". The object ID of the "Subcategory" attribute is `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the relationship of the "Subcategory" attribute object by adding relationships between "Category" and "Subcategory", and "Subcategory" and "Item". The object ID of the "Subcategory" attribute is `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 The following screenshot shows how these relationships are shown in the editor.
 
diff --git a/docs/common-workflows/modeling/manage-base-formula-objects/create-a-base-formulas-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-base-formula-objects/create-a-base-formulas-definition-within-a-changeset.md
index 3e2ef0b23..c4c2c847f 100644
--- a/docs/common-workflows/modeling/manage-base-formula-objects/create-a-base-formulas-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-base-formula-objects/create-a-base-formulas-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create an attribute object
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-bfe3c7f0-372a-44ef-a687-0f694deda59b?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 :::
 
-You want to create a new base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The destination folder ID is `31727EF14E35DAA437B716BA56466585`  in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The destination folder ID is `31727EF14E35DAA437B716BA56466585`  in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-base-formula-objects/manage-base-formula-objects.md b/docs/common-workflows/modeling/manage-base-formula-objects/manage-base-formula-objects.md
index 182858604..e78a2f9f5 100644
--- a/docs/common-workflows/modeling/manage-base-formula-objects/manage-base-formula-objects.md
+++ b/docs/common-workflows/modeling/manage-base-formula-objects/manage-base-formula-objects.md
@@ -9,7 +9,7 @@ description: Base formulas are mathematical expressions created using existing f
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-cf953972-3d9d-4347-b253-5d89e40c088c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -34,7 +34,7 @@ There are two important fields in the API response body defined for a base formu
 
   :information_source: **Info**
 
-  Tokens are a semi-structured representation of a MicroStrategy expression text that includes object references. When the base formula’s expression is represented as tokens, the text is broken down into pieces, or tokens, with information about what these pieces represent in the metadata.
+  Tokens are a semi-structured representation of a Strategy expression text that includes object references. When the base formula’s expression is represented as tokens, the text is broken down into pieces, or tokens, with information about what these pieces represent in the metadata.
 
   :::
 
diff --git a/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition-within-a-changeset.md
index c55130583..276c1beaf 100644
--- a/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve a base formula's
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-7bcc16b2-2864-4980-b2b1-77681174827a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 ::::
 
-You want to get the definition of the `"Cost"` related base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The object ID of the base formula is `594A680CB5894B25BD3AE8BB47AAF424`  in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Cost"` related base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The object ID of the base formula is `594A680CB5894B25BD3AE8BB47AAF424`  in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 For different formats of base formula expressions, please refer to [Retrieve a base formula's definition](retrieve-a-base-formulas-definition.md).
 
diff --git a/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition.md b/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition.md
index 31f37bf0e..bd480d314 100644
--- a/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition.md
+++ b/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition.md
@@ -10,7 +10,7 @@ description: This topic covers several workflows for retrieving a filter's defin
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-7bcc16b2-2864-4980-b2b1-77681174827a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 :::
 
-You want to get the definition of the `"Cost"` related base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The object ID of the base formula is `594A680CB5894B25BD3AE8BB47AAF424`  in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Cost"` related base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The object ID of the base formula is `594A680CB5894B25BD3AE8BB47AAF424`  in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-base-formula-objects/update-a-base-formulas-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-base-formula-objects/update-a-base-formulas-definition-within-a-changeset.md
index aa3124a61..a3d6d72cf 100644
--- a/docs/common-workflows/modeling/manage-base-formula-objects/update-a-base-formulas-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-base-formula-objects/update-a-base-formulas-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to update a base formula's de
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-bfe3c7f0-372a-44ef-a687-0f694deda59b?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-calendar-objects/manage-calendar-objects.md b/docs/common-workflows/modeling/manage-calendar-objects/manage-calendar-objects.md
index dded6db6a..6fbb81721 100644
--- a/docs/common-workflows/modeling/manage-calendar-objects/manage-calendar-objects.md
+++ b/docs/common-workflows/modeling/manage-calendar-objects/manage-calendar-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and replace cale
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-b40233c5-3269-43b2-bc9e-e44f6ad8d432?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-consolidation-objects/create-a-consolidation-object.md b/docs/common-workflows/modeling/manage-consolidation-objects/create-a-consolidation-object.md
index bf09fdfda..967e5a981 100644
--- a/docs/common-workflows/modeling/manage-consolidation-objects/create-a-consolidation-object.md
+++ b/docs/common-workflows/modeling/manage-consolidation-objects/create-a-consolidation-object.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a new consolidation
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-cd93cd32-2391-4f2f-9308-9f47783540bf?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -23,7 +23,7 @@ This workflow sample demonstrates how to create a new consolidation object throu
 
 [More Example: Create a consolidation with two elements.](#example-create-a-consolidation-with-two-elements)
 
-You want to create a new consolidation with the expression "(\{Customer Age=20 AND Customer=Aaby:Alen} + \{Customer City=Addison})" under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is 98FE182C2A10427EACE0CD30B6768258. The project ID is 091B51154B22036C53CFBB9958B2E8FC.
+You want to create a new consolidation with the expression "(\{Customer Age=20 AND Customer=Aaby:Alen} + \{Customer City=Addison})" under the Public Objects folder in the Strategy Tutorial project. The folder object ID is 98FE182C2A10427EACE0CD30B6768258. The project ID is 091B51154B22036C53CFBB9958B2E8FC.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-consolidation-objects/manage-consolidation-objects.md b/docs/common-workflows/modeling/manage-consolidation-objects/manage-consolidation-objects.md
index 554cd73a3..345f96fd3 100644
--- a/docs/common-workflows/modeling/manage-consolidation-objects/manage-consolidation-objects.md
+++ b/docs/common-workflows/modeling/manage-consolidation-objects/manage-consolidation-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and replace cons
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-7cc97135-4b16-4910-a32f-5463f39519cf?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-consolidation-objects/retrieve-a-consolidations-definition.md b/docs/common-workflows/modeling/manage-consolidation-objects/retrieve-a-consolidations-definition.md
index 03cc66401..48627a95d 100644
--- a/docs/common-workflows/modeling/manage-consolidation-objects/retrieve-a-consolidations-definition.md
+++ b/docs/common-workflows/modeling/manage-consolidation-objects/retrieve-a-consolidations-definition.md
@@ -10,7 +10,7 @@ description: You can use REST APIs to retrieve the definition for a consolidatio
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d0ad5e63-76a5-47c8-b185-1f5781a443f6?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ You can use REST APIs to retrieve the definition for a consolidation through the
 
 ## Retrieve a consolidation's definition
 
-You want to get the definition of a consolidation object. The object ID of the consolidation is B9E7FD5911D3E936C000B3B2D86C964F in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of a consolidation object. The object ID of the consolidation is B9E7FD5911D3E936C000B3B2D86C964F in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -461,7 +461,7 @@ Response Code: 200 (The consolidation's definition is returned successfully.)
 
 ## Retrieve a consolidation's definition within a changeset
 
-You want the definition of the consolidation object "Customer Geography". The object ID of the consolidation is B9E7FD5911D3E936C000B3B2D86C964F in the MicroStrategy Tutorial project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+You want the definition of the consolidation object "Customer Geography". The object ID of the consolidation is B9E7FD5911D3E936C000B3B2D86C964F in the Strategy Tutorial project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-consolidation-objects/update-a-consolidation-object.md b/docs/common-workflows/modeling/manage-consolidation-objects/update-a-consolidation-object.md
index 4c153a2f1..bc5143295 100644
--- a/docs/common-workflows/modeling/manage-consolidation-objects/update-a-consolidation-object.md
+++ b/docs/common-workflows/modeling/manage-consolidation-objects/update-a-consolidation-object.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to replace an existing consol
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-cd93cd32-2391-4f2f-9308-9f47783540bf?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to replace an existing consolidation objec
 1. Commit the changeset.
 1. Delete the changeset.
 
-You want to replace the existing consolidation object Customer Geography in the MicroStrategy Tutorial project. The consolidation object ID is `B9E7FD5911D3E936C000B3B2D86C964F`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to replace the existing consolidation object Customer Geography in the Strategy Tutorial project. The consolidation object ID is `B9E7FD5911D3E936C000B3B2D86C964F`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object-with-filter-elements-using-custom-expressions.md b/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object-with-filter-elements-using-custom-expressions.md
index fbf266f30..3958d587a 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object-with-filter-elements-using-custom-expressions.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object-with-filter-elements-using-custom-expressions.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a new custom group
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-595a6492-e685-41a9-bdc2-5c0b9c571315?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ You want to create a new `"Last 10 year"` custom group object with 2 filter elem
 - last 5 year: "(Year(CurrentDate()) - 5)\<= Year@ID"
 - last 10-5 years: "((Year(CurrentDate()) - 10)\<= Year@ID)AND((Year(CurrentDate()) - 5)>Year@ID)"
 
-You want to save the object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to save the object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object.md b/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object.md
index 40c83f311..5db443c11 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to create a new custom group
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-3c57732e-0689-406a-a6ad-c73ece5960c2?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to create a new custom group object through the Modeling service.
 
-You want to create a new `“Age Group“` custom group object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new `“Age Group“` custom group object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/manage-custom-group-objects.md b/docs/common-workflows/modeling/manage-custom-group-objects/manage-custom-group-objects.md
index 24a1dff67..76e6ffee3 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/manage-custom-group-objects.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/manage-custom-group-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and update custo
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-897727c2-1954-4b12-8d51-ddf79968e22c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition-within-a-changeset.md
index 926824779..df3da9d0a 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve a custom group’
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-1cd8c3f9-4d8f-496f-b183-3f615c8812e2?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ This workflow sample demonstrates how to retrieve a custom group’s definition
 
 Changesets are used in this workflow. For information on how to create and use changesets, see [Changesets](/docs/common-workflows/modeling/changesets.md). If you plan to use the response of `GET /api/model/customGroups/{customGroupsId}` to create a new custom group or update the custom group's definition, it is recommended to associate all requests to one changeset.
 
-You want to get the definition of the `"Age Group"` custom group object. The object ID of the custom group is `085CBF314703A71E926EA187C2002969` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Age Group"` custom group object. The object ID of the custom group is `085CBF314703A71E926EA187C2002969` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition.md b/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition.md
index b086d799e..baa2dbab3 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition.md
@@ -10,7 +10,7 @@ description: This topic covers three workflows for retrieving a custom group’s
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-1cd8c3f9-4d8f-496f-b183-3f615c8812e2?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -20,7 +20,7 @@ This topic covers three workflows for retrieving a custom group’s definition.
 
 This workflow sample demonstrates how to retrieve the definition of a custom group with filter elements through the Modeling service.
 
-You want to get the definition of the `"Age Group"` custom group object. The object ID of the custom group is `085CBF314703A71E926EA187C2002969` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Age Group"` custom group object. The object ID of the custom group is `085CBF314703A71E926EA187C2002969` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -276,7 +276,7 @@ Response Code: 200 (The custom group's definition was returned successfully.)
 
 This workflow sample demonstrates how to retrieve the definition of a custom group with a banding element through the Modeling service.
 
-You want to get the definition of the `"Customers Value Banding"` custom group object. The object ID of the custom group is `F519146F4B0A6EC81ED3CFA30F1C90B4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Customers Value Banding"` custom group object. The object ID of the custom group is `F519146F4B0A6EC81ED3CFA30F1C90B4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -393,7 +393,7 @@ Expressions are presented in the following formats:
 - `"tree"`: A tree data structure fully defining the expression. This format can be used if you want to examine and modify the expression programmatically.
 - `"tokens"`: A list of parsed tokens. This format can be used if you want to examine and modify the expression using the parser component. Be aware that generating tokens requires additional time.
 
-  Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a custom group filter element's expression is "Revenue > Cost". When the custom group filter element's expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).
+  Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a custom group filter element's expression is "Revenue > Cost". When the custom group filter element's expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).
 
 If omitted, the expression is returned in `"text"` format.
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/update-a-custom-groups-definition.md b/docs/common-workflows/modeling/manage-custom-group-objects/update-a-custom-groups-definition.md
index 352b1ecf1..3a33f7560 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/update-a-custom-groups-definition.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/update-a-custom-groups-definition.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to update a custom group’s
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-3c57732e-0689-406a-a6ad-c73ece5960c2?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to update a custom group’s definition through the Modeling service.
 
-You want to update the definition of the "Customers Value Metric Value Banding" custom group and rename it to "Customers Value Points Banding". The custom group is in the MicroStrategy Tutorial project. The object ID of the custom group is C4E98C9B4BACB6D57CCF58BD95672BF4. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+You want to update the definition of the "Customers Value Metric Value Banding" custom group and rename it to "Customers Value Points Banding". The custom group is in the Strategy Tutorial project. The object ID of the custom group is C4E98C9B4BACB6D57CCF58BD95672BF4. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-datamart-objects/execute-a-datamart.md b/docs/common-workflows/modeling/manage-datamart-objects/execute-a-datamart.md
index 8fbc66bca..2ea488c5d 100644
--- a/docs/common-workflows/modeling/manage-datamart-objects/execute-a-datamart.md
+++ b/docs/common-workflows/modeling/manage-datamart-objects/execute-a-datamart.md
@@ -48,7 +48,7 @@ content-type: application/json
 date: Thu,09 Feb 2023 06:16:42 GMT
 expires: 0
 pragma: no-cache
-server: MicroStrategy
+server: Strategy
 strict-transport-security: max-age=31536000;includeSubDomains
 x-content-type-options: nosniff
 x-mstr-ms-instance: 35DCAB983549ECD49FC20F9AB0CC4C28
diff --git a/docs/common-workflows/modeling/manage-datamart-objects/manage-datamart-objects.md b/docs/common-workflows/modeling/manage-datamart-objects/manage-datamart-objects.md
index 7e953cd71..9b9f9de9f 100644
--- a/docs/common-workflows/modeling/manage-datamart-objects/manage-datamart-objects.md
+++ b/docs/common-workflows/modeling/manage-datamart-objects/manage-datamart-objects.md
@@ -9,11 +9,11 @@ description: You can use REST API requests to retrieve, create, and update dat
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-1f302e4e-e863-4247-a360-802794a8d8a5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-Starting in MicroStrategy 2021 Update 7, you can use REST API requests retrieve, create, and update datamart objects through the Modeling service.
+Starting in Strategy 2021 Update 7, you can use REST API requests retrieve, create, and update datamart objects through the Modeling service.
 
 - [Retrieve a datamart definition](retrieve-a-datamart-definition.md)
 - [Create a datamart from a source report](create-a-datamart-from-a-source-report.md)
diff --git a/docs/common-workflows/modeling/manage-datamart-objects/retrieve-a-datamart-definition.md b/docs/common-workflows/modeling/manage-datamart-objects/retrieve-a-datamart-definition.md
index f77f0d698..6adba4dc1 100644
--- a/docs/common-workflows/modeling/manage-datamart-objects/retrieve-a-datamart-definition.md
+++ b/docs/common-workflows/modeling/manage-datamart-objects/retrieve-a-datamart-definition.md
@@ -12,7 +12,7 @@ This topic covers several workflows to retrieve a datamart definition:
 - [Retrieve a datamart definition with a filter custom expression in tree and tokens formats](#retrieve-a-datamart-definition-with-a-filter-custom-expression-in-tree-and-tokens-formats)
 - [Retrieve a datamart definition with advanced properties](#retrieve-a-datamart-definition-with-advanced-properties)
 
-You want to get the definition of the “Customer" datamart object as below screenshot with datamart options. The object ID of the datamart is  CEA3C6FC4E6749C8F8B19580D16D2443 in the "MicroStrategy Tutorial" project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+You want to get the definition of the “Customer" datamart object as below screenshot with datamart options. The object ID of the datamart is  CEA3C6FC4E6749C8F8B19580D16D2443 in the "Strategy Tutorial" project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-datamart-objects/retrieve-applicable-properties-of-a-datamart.md b/docs/common-workflows/modeling/manage-datamart-objects/retrieve-applicable-properties-of-a-datamart.md
index db7f7bd5e..203430c45 100644
--- a/docs/common-workflows/modeling/manage-datamart-objects/retrieve-applicable-properties-of-a-datamart.md
+++ b/docs/common-workflows/modeling/manage-datamart-objects/retrieve-applicable-properties-of-a-datamart.md
@@ -5,7 +5,7 @@ description: This workflow sample demonstrates how to retrieve applicable proper
 
 You can use REST APIs to retrieve all the applicable properties of a datamart through the Modeling service. The workflow includes the following REST APIs requests.
 
-The datamart object ID is 0DC7208C43B65E0DA10B26A6273F5067. The datamart is in the project "MicroStrategy Tutorial", and the project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+The datamart object ID is 0DC7208C43B65E0DA10B26A6273F5067. The datamart is in the project "Strategy Tutorial", and the project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
@@ -54,8 +54,8 @@ Sample Response Body:
       "showSqlPreview": true,
       "options": [
         {
-          "value": "Choosing this option keeps the backward compatibility with MicroStrategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
-          "sqlPreview": "OBSOLETE - Keep backward compatibility with MicroStrategy 2019."
+          "value": "Choosing this option keeps the backward compatibility with Strategy 2019 where SQL queries are governed by \"Cartesian Join Warning\" VLDB setting.",
+          "sqlPreview": "OBSOLETE - Keep backward compatibility with Strategy 2019."
         },
         {
           "value": "Cancel execution of cartesian join for SQL, MDX, In-Memory queries.",
diff --git a/docs/common-workflows/modeling/manage-derived-element-objects/create-a-derived-element.md b/docs/common-workflows/modeling/manage-derived-element-objects/create-a-derived-element.md
index a53996644..2232aa0df 100644
--- a/docs/common-workflows/modeling/manage-derived-element-objects/create-a-derived-element.md
+++ b/docs/common-workflows/modeling/manage-derived-element-objects/create-a-derived-element.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a new derived eleme
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d4a5b7c7-3dba-46fc-acce-0683a23bb1fe?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -27,7 +27,7 @@ This workflow sample demonstrates how to create a new derived element object thr
 
 ## Create a derived element using a list element
 
-You want to create a new `"{Age Range} = 25 to 34, Under 24"` derived element object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `091B51154B22036C53CFBB9958B2E8FC`.
+You want to create a new `"{Age Range} = 25 to 34, Under 24"` derived element object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `091B51154B22036C53CFBB9958B2E8FC`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-derived-element-objects/manage-derived-element-objects.md b/docs/common-workflows/modeling/manage-derived-element-objects/manage-derived-element-objects.md
index 5ea9aa5ee..40f9c5f12 100644
--- a/docs/common-workflows/modeling/manage-derived-element-objects/manage-derived-element-objects.md
+++ b/docs/common-workflows/modeling/manage-derived-element-objects/manage-derived-element-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and replace deri
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-45044f1d-938d-4f1a-872d-6b3577c73416?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-derived-element-objects/replace-an-existing-element.md b/docs/common-workflows/modeling/manage-derived-element-objects/replace-an-existing-element.md
index ca13fd5d6..debe3b0b4 100644
--- a/docs/common-workflows/modeling/manage-derived-element-objects/replace-an-existing-element.md
+++ b/docs/common-workflows/modeling/manage-derived-element-objects/replace-an-existing-element.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to replace an existing derive
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d4a5b7c7-3dba-46fc-acce-0683a23bb1fe?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to replace an existing derived element obj
 1. Commit the changeset.
 1. Delete the changeset.
 
-You want to replace the existing `"Region DE"` derived element object in the MicroStrategy Tutorial project. The derived element object ID is `610B9CC14AD9DCB69F094C89D3B5480B`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to replace the existing `"Region DE"` derived element object in the Strategy Tutorial project. The derived element object ID is `610B9CC14AD9DCB69F094C89D3B5480B`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-derived-element-objects/retrieve-a-derived-elements-definition.md b/docs/common-workflows/modeling/manage-derived-element-objects/retrieve-a-derived-elements-definition.md
index 6eb35f1ff..d4bc13b90 100644
--- a/docs/common-workflows/modeling/manage-derived-element-objects/retrieve-a-derived-elements-definition.md
+++ b/docs/common-workflows/modeling/manage-derived-element-objects/retrieve-a-derived-elements-definition.md
@@ -10,7 +10,7 @@ description: You can use REST APIs to retrieve the definition for a derived elem
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d4a5b7c7-3dba-46fc-acce-0683a23bb1fe?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ You can use REST APIs to retrieve the definition for a derived element through t
 
 ## Retrieve a derived element's definition
 
-You want to get the definition of a derived element that is defined by a list. The object ID of the derived element is `610B9CC14AD9DCB69F094C89D3B5480B` in the MicroStrategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to get the definition of a derived element that is defined by a list. The object ID of the derived element is `610B9CC14AD9DCB69F094C89D3B5480B` in the Strategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -170,7 +170,7 @@ Response Code: 200 (The derived element's definition is returned successfully.)
 
 ## Retrieve the definition of a derived element within a changeset
 
-You want to get the definition of the derived element object, `"groupDerivedElement"`. The object ID of the derived element is `610B9CC14AD9DCB69F094C89D3B5480B` in the MicroStrategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to get the definition of the derived element object, `"groupDerivedElement"`. The object ID of the derived element is `610B9CC14AD9DCB69F094C89D3B5480B` in the Strategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-dossier-themes/manage-dossier-themes.md b/docs/common-workflows/modeling/manage-dossier-themes/manage-dossier-themes.md
index d9154b5b1..6b4e6f8f9 100644
--- a/docs/common-workflows/modeling/manage-dossier-themes/manage-dossier-themes.md
+++ b/docs/common-workflows/modeling/manage-dossier-themes/manage-dossier-themes.md
@@ -7,7 +7,7 @@ description: A dashboard theme is used to define dashboard presentation styles.
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-dossier-themes/save-dossier-themes.md b/docs/common-workflows/modeling/manage-dossier-themes/save-dossier-themes.md
index f915e4151..2d40373d1 100644
--- a/docs/common-workflows/modeling/manage-dossier-themes/save-dossier-themes.md
+++ b/docs/common-workflows/modeling/manage-dossier-themes/save-dossier-themes.md
@@ -10,7 +10,7 @@ description: A workflow sample for saving a dashboard theme instance to metadata
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-drill-maps/create-a-drill-map.md b/docs/common-workflows/modeling/manage-drill-maps/create-a-drill-map.md
index cd6ee1df6..de7ac518a 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/create-a-drill-map.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/create-a-drill-map.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to create a new drill map obj
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2b7a0f0c-2172-418a-93ec-e0f0a13fa741?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to create a new drill map object through the Modeling service.
 
-The drill map is under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `091B51154B22036C53CFBB9958B2E8FC`.
+The drill map is under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `091B51154B22036C53CFBB9958B2E8FC`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-drill-maps/manage-drill-maps.md b/docs/common-workflows/modeling/manage-drill-maps/manage-drill-maps.md
index 85a8508a6..e4440650e 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/manage-drill-maps.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/manage-drill-maps.md
@@ -9,11 +9,11 @@ description: You can use REST API requests to retrieve, create, and update drill
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-675653f8-369b-425d-b730-a43e11b584bb?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-Starting in MicroStrategy 2021 Update 6, you can use REST API requests to retrieve, create, and update drill map objects through the Modeling service.
+Starting in Strategy 2021 Update 6, you can use REST API requests to retrieve, create, and update drill map objects through the Modeling service.
 
 - [Retrieve a drill map definition](retrieve-a-drill-map-definition.md)
 - [Create a drill map](create-a-drill-map.md)
diff --git a/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-drill-map-definition.md b/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-drill-map-definition.md
index 21ca660c6..0c093aa7f 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-drill-map-definition.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-drill-map-definition.md
@@ -10,7 +10,7 @@ description: You can use REST API requests to retrieve, create, and update drill
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2b7a0f0c-2172-418a-93ec-e0f0a13fa741?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ You can use REST APIs to retrieve the definition of a drill map through the Mode
 
 ## Retrieve a drill map definition
 
-You want to get the definition of a drill map object. The object ID of the drill map is `CC2E6AA3421EFF5C41C2D0939750BB24` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of a drill map object. The object ID of the drill map is `CC2E6AA3421EFF5C41C2D0939750BB24` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
@@ -187,7 +187,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 :::
 
-You want to get the definition of the Sample Drill Map drill map object. The object ID of this drill map is `CC2E6AA3421EFF5C41C2D0939750BB24` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the Sample Drill Map drill map object. The object ID of this drill map is `CC2E6AA3421EFF5C41C2D0939750BB24` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-list-of-objects.md b/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-list-of-objects.md
index 390de5c42..50d634cc1 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-list-of-objects.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-list-of-objects.md
@@ -8,7 +8,7 @@ description: This workflow sample demonstrates how to get the list of objects as
 
 This workflow sample demonstrates how to get the list of objects associated with a specific drill map.
 
-You want to get the list of objects associated with the `Drill Map for Demo` drill map object in the MicroStrategy Tutorial project. The project ID is `091B51154B22036C53CFBB9958B2E8FC`. The drill map ID is `CC2E6AA3421EFF5C41C2D0939750BB24`.
+You want to get the list of objects associated with the `Drill Map for Demo` drill map object in the Strategy Tutorial project. The project ID is `091B51154B22036C53CFBB9958B2E8FC`. The drill map ID is `CC2E6AA3421EFF5C41C2D0939750BB24`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-drill-maps/update-a-drill-map.md b/docs/common-workflows/modeling/manage-drill-maps/update-a-drill-map.md
index 1d9950ea3..2d194a0b3 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/update-a-drill-map.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/update-a-drill-map.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to update an existing drill m
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2b7a0f0c-2172-418a-93ec-e0f0a13fa741?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to update an existing drill map object through the Modeling service.
 
-You want to update the existing `Drill Map for Demo` drill map object in the MicroStrategy Tutorial project. The project ID is `091B51154B22036C53CFBB9958B2E8FC`). The drill map ID is `CC2E6AA3421EFF5C41C2D0939750BB24`.
+You want to update the existing `Drill Map for Demo` drill map object in the Strategy Tutorial project. The project ID is `091B51154B22036C53CFBB9958B2E8FC`). The drill map ID is `CC2E6AA3421EFF5C41C2D0939750BB24`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/create-a-fact-object.md b/docs/common-workflows/modeling/manage-fact-objects/create-a-fact-object.md
index d4baf9838..738452262 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/create-a-fact-object.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/create-a-fact-object.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a fact object throu
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-11d116e7-cf31-451a-848e-0d2be6fa3041?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to create a fact object through the Modeli
 1. Commit the changeset
 1. Delete the changeset
 
-You want to create a "Profit" fact object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a "Profit" fact object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -47,7 +47,7 @@ To create a fact, in the request body, "expressions" contains a list of fact exp
 
 - "expression": Must be in either "tree" or "tokens" format.
 
-  Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
+  Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
 
 - "tables": A list of tables that the "expression" applies to. Warehouse partition base tables and metadata partition mapping tables are not allowed here.
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/manage-fact-objects.md b/docs/common-workflows/modeling/manage-fact-objects/manage-fact-objects.md
index d3f875a59..a19560cee 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/manage-fact-objects.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/manage-fact-objects.md
@@ -10,7 +10,7 @@ description: You can use REST API requests to retrieve, create and update fact o
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d9b59a86-7b75-4cea-be1c-941dae6f4b08?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition-within-a-changeset.md
index 788f05e22..5aa99d824 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve a fact's definiti
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-440d539e-15d7-4709-94a5-9c74eecc03db?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -26,7 +26,7 @@ Changesets are used in this workflow. For information on how to create and use c
 1. [Get a fact's definition within a changeset.](#get-a-facts-definition-within-a-changeset)
 1. Delete the changeset.
 
-You want to get the definition of the "Profit" fact object. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the "MicroStrategy Tutorial" project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Profit" fact object. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the "Strategy Tutorial" project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition.md b/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition.md
index b819b0db6..75703c0e9 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition.md
@@ -10,7 +10,7 @@ description: This topic covers two workflows for retrieving a fact’s definitio
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-3b137a26-4cf4-4902-8f11-9d7a7cffc5f0?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -23,7 +23,7 @@ This topic covers two workflows for retrieving a fact’s definition:
 
 This workflow sample demonstrates how to retrieve the definition of a fact through the Modeling service.
 
-You want to get the definition of the "Profit" fact object. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Profit" fact object. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -99,7 +99,7 @@ Response Code: 200 (The fact's definition was returned successfully.)
 
 ## Retrieve a fact's definition with expressions in tree and tokens formats
 
-In this sample workflow, you want to get the definition of the "Profit" fact object, with its expressions returned in tree and tokens formats. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this sample workflow, you want to get the definition of the "Profit" fact object, with its expressions returned in tree and tokens formats. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
@@ -109,7 +109,7 @@ Expressions are presented in the following formats:
 - "tree": A tree data structure fully defining the expression. This format can be used if you want to examine and modify the expression programmatically.
 - "tokens": A list of parsed tokens. This format can be used if you want to examine and modify the expression using the parser component. Be aware that generating tokens requires additional time.
 
-Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
+Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
 
 If `showExpressionAs` is omitted, the expression is returned in "text" format.
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/update-a-fact-object.md b/docs/common-workflows/modeling/manage-fact-objects/update-a-fact-object.md
index 1383a764d..774f4e6c4 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/update-a-fact-object.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/update-a-fact-object.md
@@ -10,7 +10,7 @@ description: The workflow to update a fact object.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-11d116e7-cf31-451a-848e-0d2be6fa3041?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -19,7 +19,7 @@ Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/
 1. Commit the changeset.
 1. Delete the changeset.
 
-You want to update the "Profit" fact object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the "Profit" fact object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -45,7 +45,7 @@ To update a fact, in the request body, "expressions" contains a list of fact exp
 
 - "expression": Must be in either "tree" or "tokens" format.
 
-  Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
+  Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a fact expression is "Revenue - Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", Minus_ID), ("Cost", Cost_ID).
 
 - "tables": A list of tables that the "expression" applies to. Warehouse partition base tables and metadata partition mapping tables are not allowed here.
 - "dataType" is optional. If omitted, it calculates based on the first fact expression.
diff --git a/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object-with-a-custom-expression.md b/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object-with-a-custom-expression.md
index b4253cddb..ffb950ab4 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object-with-a-custom-expression.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object-with-a-custom-expression.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a new filter object
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-b6421792-16ec-4d68-9af9-8fc38eb35b7e?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -29,7 +29,7 @@ This workflow sample demonstrates how to create a new filter object using a cust
 
 Additional samples are provided in [More samples](#more-samples).
 
-You want to create a new "(Year(CurrentDate()) - 5)< Year@ID" filter object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new "(Year(CurrentDate()) - 5)< Year@ID" filter object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object.md b/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object.md
index 4d58d2da6..a300b1001 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a new filter object
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-5bb60de6-52e2-43c4-87bc-b404125f96ad?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to create a new filter object through the
 1. Commit the changeset
 1. Delete the changeset
 
-You want to create a new “Year>2015“ filter object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new “Year>2015“ filter object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/manage-filter-objects.md b/docs/common-workflows/modeling/manage-filter-objects/manage-filter-objects.md
index d24ff6c4a..1c59513fa 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/manage-filter-objects.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/manage-filter-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create and update filter
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c51122ec-725f-4841-aa4f-1ba8f88249ff?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition-within-a-changeset.md
index e7bb179e0..25ab934c5 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve a filter's defini
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-67e58dfc-a902-47a6-9166-a26e308ef644?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -22,7 +22,7 @@ Changesets are used in this workflow. For information on how to create and use c
 1. [Get the filter's definition within a changeset.](#get-a-filter-definition-within-a-changeset)
 1. Delete the changeset.
 
-You want to get the definition of the "Year > 2015" filter object. The object ID of the filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Year > 2015" filter object. The object ID of the filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition.md b/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition.md
index 96a2a4bb6..54595dc05 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition.md
@@ -10,7 +10,7 @@ description: This topic covers several workflows for retrieving a filter's defin
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c532ccd7-317b-4f18-9a37-1388740cbab5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -25,7 +25,7 @@ This topic covers several workflows for retrieving a filter's definition:
 
 This workflow sample demonstrates how to retrieve the definition of a filter through the Modeling service.
 
-You want to get the definition of the "Year > 2015" filter object. The object ID of the filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Year > 2015" filter object. The object ID of the filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -109,7 +109,7 @@ In this workflow sample, you want to get the definition of the "Year < 2015" fil
 
 :::tip
 
-Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a filter expression is "Revenue > Cost". When the filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).
+Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a filter expression is "Revenue > Cost". When the filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).
 
 A filter's "qualification" is presented in the following formats:
 
@@ -245,7 +245,7 @@ Custom expressions are presented in the following formats:
 - "tree": A tree data structure fully defining the expression. This format can be used if you want to examine and modify the expression programmatically.
 - "tokens": A list of parsed tokens. This format can be used if you want to examine and modify the expression using the parser component. Be aware that generating tokens requires additional time.
 
-Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a filter expression is "Revenue > Cost". When the filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).
+Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a filter expression is "Revenue > Cost". When the filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).
 
 If omitted, the custom expression is returned in "text" format.
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/update-a-filters-definition.md b/docs/common-workflows/modeling/manage-filter-objects/update-a-filters-definition.md
index 5a0f082fc..651663f9e 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/update-a-filters-definition.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/update-a-filters-definition.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to update a filter's definiti
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-5bb60de6-52e2-43c4-87bc-b404125f96ad?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to update a filter's definition through th
 1. Commit the changeset using `POST /api/model/changesets/{changesetId}/commit`
 1. Delete the changeset using `DELETE /api/model/changesets/{changesetId}`
 
-You want to update the definition of the "Year > 2015" filter and rename it to "Year > 2020". The filter is in the MicroStrategy Tutorial project. The object ID of the filter is 8018C24FEBC4406CB9E36838C01C82D1. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754
+You want to update the definition of the "Year > 2015" filter and rename it to "Year > 2020". The filter is in the Strategy Tutorial project. The object ID of the filter is 8018C24FEBC4406CB9E36838C01C82D1. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-metric-objects/create-a-metric-within-a-changeset.md b/docs/common-workflows/modeling/manage-metric-objects/create-a-metric-within-a-changeset.md
index 1715fbc0e..cc0f121d0 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/create-a-metric-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/create-a-metric-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a metric object thr
 
 You can try this workflow with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-cd346c9a-019b-401a-9470-6097a5d9b24a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-metric-objects/manage-metric-objects.md b/docs/common-workflows/modeling/manage-metric-objects/manage-metric-objects.md
index 5c279eb2c..1c051b14e 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/manage-metric-objects.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/manage-metric-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and update met
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-e7563dc0-b691-44bd-bba9-a7ff60faeb19?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -29,21 +29,21 @@ Training metrics, extreme metric, reference line metrics, and relationship metri
 
 The following table lists important fields in the API response body defined for a metric:
 
-| Field             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| information       | Stores the basic subtotal information including `dateCreated`, `dateModified`, `versionId`, `primaryLocale`, `objectId`, `subType`, and `name`. For a metric, `subType` is `metric`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| expression        | Stores the aggregation types and targets defined in the metric either using single-value functions or group-value functions.<br/><br/>Tokens are a semi-structured representation of a MicroStrategy expression text that includes object references. When the metric’s expression is represented as tokens, the text is broken down into pieces, or tokens, with information about what these pieces represent in the metadata.<br/><br/>A metric's “expression" is presented in the following formats:<br/><br/>_"text": A human-readable, but non-parsable text, that describes a metric's expression.<br/> <br/>_ "tree": A tree data structure that fully defines the metric's expression.<br/> <br/> "tokens": A list of parsed tokens that define a metric's expression. Generating tokens requires additional time.<br/> <br/><br/>If `showExpressionAs` is omitted, only "text" formats are returned.<br/><br/>If `showExpressionAs` is `tree`, "text" and "tree" formats are returned.<br/><br/>If `showExpressionAs` is `tokens`, "text" and "tokens" formats are returned. |
-| dimty             | Contains a list of `DimtyUnit`, which describes the level metrics can be calculated.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| conditionality    | Contains a filter that needs to apply to the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| metricSubtotals   | Contains a vector that needs to apply to the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| aggregateFromBase | Contains a vector of subtotals to apply to the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| formulaJoinType   | Indicates the formula join type for the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| dataType          | Indicates the data type for the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| smartTotal        | Indicates the total calculation type.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| format            | Contains the header format and value format.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| subtotalFromBase  | Indicates the subtotal type for the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| columnNameAlias   | Contains the name used in SQL generation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| metricFormatType  | Indicates the format type for the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| thresholds        | Contains a list of thresholds applied to the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Field             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| information       | Stores the basic subtotal information including `dateCreated`, `dateModified`, `versionId`, `primaryLocale`, `objectId`, `subType`, and `name`. For a metric, `subType` is `metric`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| expression        | Stores the aggregation types and targets defined in the metric either using single-value functions or group-value functions.<br/><br/>Tokens are a semi-structured representation of a Strategy expression text that includes object references. When the metric’s expression is represented as tokens, the text is broken down into pieces, or tokens, with information about what these pieces represent in the metadata.<br/><br/>A metric's “expression" is presented in the following formats:<br/><br/>_"text": A human-readable, but non-parsable text, that describes a metric's expression.<br/> <br/>_ "tree": A tree data structure that fully defines the metric's expression.<br/> <br/> "tokens": A list of parsed tokens that define a metric's expression. Generating tokens requires additional time.<br/> <br/><br/>If `showExpressionAs` is omitted, only "text" formats are returned.<br/><br/>If `showExpressionAs` is `tree`, "text" and "tree" formats are returned.<br/><br/>If `showExpressionAs` is `tokens`, "text" and "tokens" formats are returned. |
+| dimty             | Contains a list of `DimtyUnit`, which describes the level metrics can be calculated.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| conditionality    | Contains a filter that needs to apply to the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| metricSubtotals   | Contains a vector that needs to apply to the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| aggregateFromBase | Contains a vector of subtotals to apply to the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| formulaJoinType   | Indicates the formula join type for the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| dataType          | Indicates the data type for the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| smartTotal        | Indicates the total calculation type.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| format            | Contains the header format and value format.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| subtotalFromBase  | Indicates the subtotal type for the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| columnNameAlias   | Contains the name used in SQL generation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| metricFormatType  | Indicates the format type for the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| thresholds        | Contains a list of thresholds applied to the metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 
 For more information about the Modeling service, see [Configuring the Modeling Service](https://www2.microstrategy.com/producthelp/2021/InstallConfig/en-us/Content/modeling_service.htm).
diff --git a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-applicable-properties.md b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-applicable-properties.md
index f72a81064..7dfde705f 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-applicable-properties.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-applicable-properties.md
@@ -10,13 +10,13 @@ description: This topic covers the workflow for retrieving a metric's applicable
 
 You can try this workflow with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c9639bc3-853f-4746-94b6-528b5aed21a5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This topic covers the workflow to retrieve a metric's applicable properties.
 
-Get the applicable properties of the `“Cost Comparison"` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+Get the applicable properties of the `“Cost Comparison"` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition-within-a-changeset.md
index 21595b54b..f7e0d4517 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve a metric's defini
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c9639bc3-853f-4746-94b6-528b5aed21a5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 :::
 
-Get the definition of the `“Cost Comparison”` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+Get the definition of the `“Cost Comparison”` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 For different formats of metric expressions, see [Retrieve a metric's definition](../manage-metric-objects/retrieve-a-metrics-definition.md).
 
diff --git a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition.md b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition.md
index 2925a6fe7..9fce2e3ef 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition.md
@@ -10,13 +10,13 @@ description: This topic covers several workflows for retrieving a metric's defin
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c9639bc3-853f-4746-94b6-528b5aed21a5?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This topic covers several workflows for retrieving a metric's definition.
 
-You want to get the definition of the `“Cost Comparison"` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `“Cost Comparison"` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-metric-objects/update-a-metrics-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-metric-objects/update-a-metrics-definition-within-a-changeset.md
index 92bd57ee5..18077a2d1 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/update-a-metrics-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/update-a-metrics-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to update a metric's definiti
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-cd346c9a-019b-401a-9470-6097a5d9b24a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/create-a-prompt-within-a-changeset.md b/docs/common-workflows/modeling/manage-prompt-objects/create-a-prompt-within-a-changeset.md
index f824bdcd9..ba7ba6ce7 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/create-a-prompt-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/create-a-prompt-within-a-changeset.md
@@ -8,7 +8,7 @@ description: This workflow sample demonstrates how to create a new prompt object
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-bfdf91c2-f8d8-495a-b4ca-cf1daeb7c6db?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -19,7 +19,7 @@ This workflow sample demonstrates how to create a new prompt object through the
 1. Commit a changeset using `POST /api/model/changesets/{changesetId}/commit`
 1. Delete a changeset using `DELETE /api/model/changesets/{changesetId}`
 
-You want to create a new prompt object for the `"Call Center in USA"` prompt under a specific folder in the MicroStrategy Tutorial project. The folder object ID is `8A1831FF494F528D02A4A8BF5FB73459`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new prompt object for the `"Call Center in USA"` prompt under a specific folder in the Strategy Tutorial project. The folder object ID is `8A1831FF494F528D02A4A8BF5FB73459`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -39,7 +39,7 @@ Get the project ID from [GET /api/projects](https://demo.microstrategy.com/Micro
 
 ## Create a prompt using [POST /api/model/prompts](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Prompts/ms-postPrompt)
 
-You want to create a `"Call Center in USA"` prompt of an attribute element prompt under a specific folder in the MicroStrategy Tutorial project. To create the prompt, you must submit the request body with the correct information. In `"information"`, provide the `"subType"`, `"name"`, and `"destinationFolderId"` for the prompt you want to create.
+You want to create a `"Call Center in USA"` prompt of an attribute element prompt under a specific folder in the Strategy Tutorial project. To create the prompt, you must submit the request body with the correct information. In `"information"`, provide the `"subType"`, `"name"`, and `"destinationFolderId"` for the prompt you want to create.
 
 If you are constructing the POST prompt request body based on the response of the GET prompt call of an existing prompt, be aware that any embedded objects (`"isEmbedded":true`) cannot be used to create a new prompt, as the embedded objects are only "local" to their owner.
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/manage-prompt-objects.md b/docs/common-workflows/modeling/manage-prompt-objects/manage-prompt-objects.md
index 1f7d41e66..a97943a66 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/manage-prompt-objects.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/manage-prompt-objects.md
@@ -7,7 +7,7 @@ description: You can use REST API requests to retrieve, create, update, and dele
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-02d537e0-b0b3-4e13-b613-1cd863b7db88?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/attribute-element-prompts.md b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/attribute-element-prompts.md
index b13c1d90d..95c6e2740 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/attribute-element-prompts.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/attribute-element-prompts.md
@@ -7,7 +7,7 @@ description: An attribute element prompt is one of the most commonly used prompt
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-fc989893-c6cd-42eb-915f-955f12a7fc05?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/attribute-qualification-prompts.md b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/attribute-qualification-prompts.md
index d5baa4ae2..6683000b8 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/attribute-qualification-prompts.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/attribute-qualification-prompts.md
@@ -7,7 +7,7 @@ description: An attribute qualification prompt is a restrictive type prompt that
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-ac7cde77-bb20-4c51-86e3-a457f5b8f43f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/hierarchy-qualification-prompts.md b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/hierarchy-qualification-prompts.md
index 41848977a..41eb9177a 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/hierarchy-qualification-prompts.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/hierarchy-qualification-prompts.md
@@ -7,7 +7,7 @@ description: A hierarchy qualification prompt allows users to filter data in a r
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c7bb0522-b646-4b0a-93a1-159c55b3af82?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/metric-expression-prompts.md b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/metric-expression-prompts.md
index fb7aa4716..8524b75a4 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/metric-expression-prompts.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/metric-expression-prompts.md
@@ -7,7 +7,7 @@ description: A metric expression element prompt is one of the most commonly used
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-bca657c1-687a-4ba4-9050-3b45b4a5ce39?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/object-prompts.md b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/object-prompts.md
index 7c57c1aae..c9e6f054a 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/object-prompts.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/object-prompts.md
@@ -7,7 +7,7 @@ description: An object prompt allows the caller to supply a list of objects, suc
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-10f21f1c-3d27-4459-80ba-729a44b945a7?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/prompt-types.md b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/prompt-types.md
index 477e658f4..08a865e88 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/prompt-types.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/prompt-types.md
@@ -1,9 +1,9 @@
 ---
 title: Prompt types for managing prompt objects
-description: There are several different prompt types in the MicroStrategy platform. Each prompt type is defined by a specific set of parameters and corresponds to a value in EnumDSSXMLPromptType.
+description: There are several different prompt types in the Strategy platform. Each prompt type is defined by a specific set of parameters and corresponds to a value in EnumDSSXMLPromptType.
 ---
 
-There are several different prompt types in the MicroStrategy platform. Each prompt type is defined by a specific set of parameters and corresponds to a value in [EnumDSSXMLPromptType](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPromptType.html).
+There are several different prompt types in the Strategy platform. Each prompt type is defined by a specific set of parameters and corresponds to a value in [EnumDSSXMLPromptType](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLPromptType.html).
 
 For the following prompt types, you can perform prompt actions supported by REST APIs for managing prompt objects. This includes retrieving prompt definitions, creating new prompts, modifying prompt definitions, and deleting existing prompts.
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/value-prompts.md b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/value-prompts.md
index f96cb7fff..635f2e232 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/value-prompts.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/prompt-types/value-prompts.md
@@ -7,7 +7,7 @@ description: A value prompt allows the results to be filtered based on a specifi
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2541f642-4418-4621-980d-40fa31236eb8?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/retrieve-a-prompts-definition.md b/docs/common-workflows/modeling/manage-prompt-objects/retrieve-a-prompts-definition.md
index a994f94c2..3ea02465a 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/retrieve-a-prompts-definition.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/retrieve-a-prompts-definition.md
@@ -8,13 +8,13 @@ description: This workflow sample demonstrates how to retrieve a prompt's defini
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-3952eb54-479d-4930-aac5-64cf1c1dfdaf?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to retrieve a prompt's definition.
 
-You want to get the definition of the `"Call Center in USA"` prompt object. The object ID of the prompt is `2804B5284AFF95E8E0EEB4AC09B5B972` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Call Center in USA"` prompt object. The object ID of the prompt is `2804B5284AFF95E8E0EEB4AC09B5B972` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/update-a-prompts-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-prompt-objects/update-a-prompts-definition-within-a-changeset.md
index 5727148fb..2a258dcb9 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/update-a-prompts-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/update-a-prompts-definition-within-a-changeset.md
@@ -8,7 +8,7 @@ description: This workflow demonstrates how to update a prompt's definition thro
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-3952eb54-479d-4930-aac5-64cf1c1dfdaf?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object-using-a-custom-expression.md b/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object-using-a-custom-expression.md
index 9f69b0d7e..0aefa9bbd 100644
--- a/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object-using-a-custom-expression.md
+++ b/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object-using-a-custom-expression.md
@@ -20,7 +20,7 @@ This workflow sample demonstrates how to create a security filter definition thr
 
 Additional examples are provided in [More samples](#more-samples).
 
-In this workflow sample, you want to create a new security filter object to qualification for the last five years. The custom expression is `“(Year(CurrentDate()) - 5)< Year@ID”`. Save the security filter under the Public Objects folder in the MicroStrategy Tutorial project. The folder ID is `98FE182C2A10427EACE0CD30B6768258`. The MicroStrategy Tutorial project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to create a new security filter object to qualification for the last five years. The custom expression is `“(Year(CurrentDate()) - 5)< Year@ID”`. Save the security filter under the Public Objects folder in the Strategy Tutorial project. The folder ID is `98FE182C2A10427EACE0CD30B6768258`. The Strategy Tutorial project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object.md b/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object.md
index 849e21001..6c278e39e 100644
--- a/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object.md
+++ b/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object.md
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to create a new security filter object thr
 
 Additional samples are provided in [More samples](#more-samples).
 
-In this workflow sample, you want to create a "Year > 2015" security filter object under the Public Objects folder in the MicroStrategy Tutorial project. The folder ID is `98FE182C2A10427EACE0CD30B6768258`. The MicroStrategy Tutorial project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to create a "Year > 2015" security filter object under the Public Objects folder in the Strategy Tutorial project. The folder ID is `98FE182C2A10427EACE0CD30B6768258`. The Strategy Tutorial project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-security-filter-objects/manage-security-filter-objects.md b/docs/common-workflows/modeling/manage-security-filter-objects/manage-security-filter-objects.md
index 17c596c5e..fb00b98a0 100644
--- a/docs/common-workflows/modeling/manage-security-filter-objects/manage-security-filter-objects.md
+++ b/docs/common-workflows/modeling/manage-security-filter-objects/manage-security-filter-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create and update securi
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-add85127-d706-4f6d-b202-16368325e40e?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-security-filter-objects/modify-a-security-filters-member.md b/docs/common-workflows/modeling/manage-security-filter-objects/modify-a-security-filters-member.md
index 49439ffef..c9c238645 100644
--- a/docs/common-workflows/modeling/manage-security-filter-objects/modify-a-security-filters-member.md
+++ b/docs/common-workflows/modeling/manage-security-filter-objects/modify-a-security-filters-member.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to modify the users and user
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-b39c86ac-1a16-4100-a96d-b1a6d2f74b9c?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-security-filter-objects/retrieve-a-security-filter-definition.md b/docs/common-workflows/modeling/manage-security-filter-objects/retrieve-a-security-filter-definition.md
index a6f17f497..5e6a87db0 100644
--- a/docs/common-workflows/modeling/manage-security-filter-objects/retrieve-a-security-filter-definition.md
+++ b/docs/common-workflows/modeling/manage-security-filter-objects/retrieve-a-security-filter-definition.md
@@ -16,7 +16,7 @@ This topic covers several workflows for retrieving a security filter's definitio
 
 ## Retrieve a security filter's definition
 
-In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -104,7 +104,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 :::
 
-In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -252,11 +252,11 @@ Sample Response Code: 204 (The changeset has been deleted successfully)
 
 ## Retrieve a security filter's definition in tokens format
 
-In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. This procedure is similar to [Retrieve a security filter's definition](#retrieve-a-security-filters-definition), except you want to enable the `showFilterTokens` parameter to retrieve the security filter's definition in tokens format.
+In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. This procedure is similar to [Retrieve a security filter's definition](#retrieve-a-security-filters-definition), except you want to enable the `showFilterTokens` parameter to retrieve the security filter's definition in tokens format.
 
 :::tip
 
-Security filter tokens are used the same manner as filter tokens. Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let's say a security filter expression is "Revenue > Cost". When the security filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).<br/><br/>A security filter's "qualification" is presented in the following formats:
+Security filter tokens are used the same manner as filter tokens. Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let's say a security filter expression is "Revenue > Cost". When the security filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).<br/><br/>A security filter's "qualification" is presented in the following formats:
 
 - "text": A human-readable, but non-parsable text, describing a filter's qualification.
 - "tree": A tree data structure fully defining the filter's qualification.
@@ -392,7 +392,7 @@ Custom expressions are presented in the following formats:
 - "tree": A tree data structure fully defining the expression. This format can be used if you want to examine and modify the expression programmatically.
 - "tokens": A list of parsed tokens. This format can be used if you want to examine and modify the expression using the parser component. Be aware that generating tokens requires additional time.
 
-  Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let's say a security filter expression is "Revenue > Cost". When the security filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).
+  Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let's say a security filter expression is "Revenue > Cost". When the security filter expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), (">", GreaterThan_ID), ("Cost", Cost_ID).
 
 If omitted, the custom expression is returned in "text" format.
 
diff --git a/docs/common-workflows/modeling/manage-subtotal-objects/create-a-subtotal-within-a-changeset.md b/docs/common-workflows/modeling/manage-subtotal-objects/create-a-subtotal-within-a-changeset.md
index e1a871582..2cdcad097 100644
--- a/docs/common-workflows/modeling/manage-subtotal-objects/create-a-subtotal-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-subtotal-objects/create-a-subtotal-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a subtotal object t
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-0054ca44-40a6-4387-b766-35fc5f00e428?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-subtotal-objects/manage-subtotal-objects.md b/docs/common-workflows/modeling/manage-subtotal-objects/manage-subtotal-objects.md
index d5711dffe..f037deef6 100644
--- a/docs/common-workflows/modeling/manage-subtotal-objects/manage-subtotal-objects.md
+++ b/docs/common-workflows/modeling/manage-subtotal-objects/manage-subtotal-objects.md
@@ -9,7 +9,7 @@ description: Subtotals allow you to dynamically control the computation and disp
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-0e8e2533-03d6-4235-8aa0-6aef1cc2e723?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -34,7 +34,7 @@ There are three important fields in the API response body defined for a subtotal
 
   :information_source: **Info**
 
-  Tokens are a semi-structured representation of a MicroStrategy expression text that includes object references. When the subtotal’s expression is represented as tokens, the text is broken down into pieces, or tokens, with information about what these pieces represent in the metadata.
+  Tokens are a semi-structured representation of a Strategy expression text that includes object references. When the subtotal’s expression is represented as tokens, the text is broken down into pieces, or tokens, with information about what these pieces represent in the metadata.
 
   :::
 
diff --git a/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition-within-a-changeset.md
index 43d14a516..9982cd73e 100644
--- a/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to retrieve a subtotal's defi
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d1504a52-db9a-4d71-99d2-0ffbd82ee91a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 :::
 
-You want to get the definition of an object with the ID of `514C2064DF754990AF60432A1C1E4A77` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of an object with the ID of `514C2064DF754990AF60432A1C1E4A77` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 For different formats of subtotal expressions, see [Retrieve a subtotal's definition](retrieve-a-subtotals-definition.md).
 
diff --git a/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition.md b/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition.md
index 5945742b0..349905d76 100644
--- a/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition.md
+++ b/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition.md
@@ -10,13 +10,13 @@ description: This topic covers several workflows for retrieving a metric's defin
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-d1504a52-db9a-4d71-99d2-0ffbd82ee91a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This topic covers several workflows for retrieving a metric's definition:
 
-You want to get the definition of an object with the ID of `514C2064DF754990AF60432A1C1E4A77` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of an object with the ID of `514C2064DF754990AF60432A1C1E4A77` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-subtotal-objects/update-a-subtotal-within-a-changeset.md b/docs/common-workflows/modeling/manage-subtotal-objects/update-a-subtotal-within-a-changeset.md
index 3375f2ca6..b0c84ea49 100644
--- a/docs/common-workflows/modeling/manage-subtotal-objects/update-a-subtotal-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-subtotal-objects/update-a-subtotal-within-a-changeset.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to update a subtotal's defini
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-0054ca44-40a6-4387-b766-35fc5f00e428?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/create-a-new-partition-mapping-table-object.md b/docs/common-workflows/modeling/manage-table-objects/create-a-new-partition-mapping-table-object.md
index fea09e621..7fd4202ad 100644
--- a/docs/common-workflows/modeling/manage-table-objects/create-a-new-partition-mapping-table-object.md
+++ b/docs/common-workflows/modeling/manage-table-objects/create-a-new-partition-mapping-table-object.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a new partition map
 
 You can try this workflow with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-43769ee1-7480-4413-990a-13b50119b384).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/create-a-new-table-object.md b/docs/common-workflows/modeling/manage-table-objects/create-a-new-table-object.md
index 28e9aca35..ea418e3ac 100644
--- a/docs/common-workflows/modeling/manage-table-objects/create-a-new-table-object.md
+++ b/docs/common-workflows/modeling/manage-table-objects/create-a-new-table-object.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to create a new table object
 
 You can try this workflow with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-69df2b48-9b7c-4f35-9b80-15c9066d48b0?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ This workflow sample demonstrates how to create a new table object through the M
 
 ## Create a new table object
 
-In this workflow sample, you create a new `"CITY_CTR_SLS"` table object in the MicroStrategy Tutorial project. Table name should be unique within the project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`. All schema tables are created under the objects/tables folder schema.
+In this workflow sample, you create a new `"CITY_CTR_SLS"` table object in the Strategy Tutorial project. Table name should be unique within the project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`. All schema tables are created under the objects/tables folder schema.
 
 Get the authorization token needed to execute the request with [POST /api/auth/login]([https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin).
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/manage-table-objects.md b/docs/common-workflows/modeling/manage-table-objects/manage-table-objects.md
index b077a5e78..c5fbb05ab 100644
--- a/docs/common-workflows/modeling/manage-table-objects/manage-table-objects.md
+++ b/docs/common-workflows/modeling/manage-table-objects/manage-table-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and update table
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-43769ee1-7480-4413-990a-13b50119b384?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-list-of-all-available-table-definitions.md b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-list-of-all-available-table-definitions.md
index af90ce317..d5f181205 100644
--- a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-list-of-all-available-table-definitions.md
+++ b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-list-of-all-available-table-definitions.md
@@ -10,7 +10,7 @@ You can use REST APIs to retrieve the definitions for a list of all available ta
 
 ## Retrieve a list of all available tables' definitions
 
-In this workflow sample, you want to get the definitions of all available tables in the project schema. Use the MicroStrategy Tutorial project. Its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definitions of all available tables in the project schema. Use the Strategy Tutorial project. Its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -89,7 +89,7 @@ Response Code: 200 (The tables' definitions are returned successfully.)
 
 ### Retrieve a list of available tables' definitions within a changeset
 
-In this workflow sample, you want to get the definitions of all available tables in the project schema. Use the MicroStrategy Tutorial project. Its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definitions of all available tables in the project schema. Use the Strategy Tutorial project. Its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-partition-mapping-tables-definition.md b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-partition-mapping-tables-definition.md
index 3e1222790..524c2df8d 100644
--- a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-partition-mapping-tables-definition.md
+++ b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-partition-mapping-tables-definition.md
@@ -10,13 +10,13 @@ description: You can use REST APIs to retrieve the definition for a partition ma
 
 You can try this workflow with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-43769ee1-7480-4413-990a-13b50119b384).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-You can use REST APIs to retrieve the definition for a partition mapping table through the Modeling service. A brief introduction of partition mapping is provided in this documentation. To learn more about partition mapping, refer to [Microstrategy Community](https://www2.microstrategy.com/producthelp/Current/ProjectDesignGuide/WebHelp/Lang_1033/Content/Dividing_tables_to_increase_performance__Partition.htm).
+You can use REST APIs to retrieve the definition for a partition mapping table through the Modeling service. A brief introduction of partition mapping is provided in this documentation. To learn more about partition mapping, refer to [Strategy Community](https://www2.microstrategy.com/producthelp/Current/ProjectDesignGuide/WebHelp/Lang_1033/Content/Dividing_tables_to_increase_performance__Partition.htm).
 
-The partitioning feature improves query performance when working with large data volumes. Partitioning "breaks" the data into different (ideally balanced) portions, and each portion is called a partition base table (PBT), or a partition table. In other words, a partition table is a warehouse table that contains one part of a larger set of data. To manage which partition table to use for a given query, partition mapping is introduced by MicroStrategy to identify and keep track of the partitioned base tables as part of a logical whole. MicroStrategy supports two types of partition mapping:
+The partitioning feature improves query performance when working with large data volumes. Partitioning "breaks" the data into different (ideally balanced) portions, and each portion is called a partition base table (PBT), or a partition table. In other words, a partition table is a warehouse table that contains one part of a larger set of data. To manage which partition table to use for a given query, partition mapping is introduced by Strategy to identify and keep track of the partitioned base tables as part of a logical whole. Strategy supports two types of partition mapping:
 
 **Warehouse partition mapping (WHPM)**: uses a specialized warehouse table (WHPM table) to determine which table to access
 
@@ -34,7 +34,7 @@ Get the project ID from [GET /api/projects](https://demo.microstrategy.com/Micro
 
 ## Retrieve a WHPM table's definition
 
-Use this workflow sample to get the definition of a WHPM table. The object ID of the table is `569A89E78FA1455687F4E327B259B3FB`. The table is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+Use this workflow sample to get the definition of a WHPM table. The object ID of the table is `569A89E78FA1455687F4E327B259B3FB`. The table is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 Get the table's definition with [GET /api/model/tables/\{TableId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Tables/ms-getTableDetails).
 
@@ -245,7 +245,7 @@ Response Code: 200 (The WHPM table's definition is returned successfully.)
 
 ## Retrieve a MDPM table's definition
 
-Use this workflow sample to get the definition of an MDPM table. The object ID of the table is `473718A30DA84A9A814424537879778F`. The table is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`. The API usage is the same as retrieving a WHPM table. Unlike all other tables, you can use "showExpressionAs" and "showFilterTokens" to customize partition filter representation.
+Use this workflow sample to get the definition of an MDPM table. The object ID of the table is `473718A30DA84A9A814424537879778F`. The table is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`. The API usage is the same as retrieving a WHPM table. Unlike all other tables, you can use "showExpressionAs" and "showFilterTokens" to customize partition filter representation.
 
 Get the table's definition with [GET /api/model/tables/\{TableId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Tables/ms-getTableDetails).
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-prompt-of-an-sap-hana-table.md b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-prompt-of-an-sap-hana-table.md
index 1e1642cd3..915c9844b 100644
--- a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-prompt-of-an-sap-hana-table.md
+++ b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-prompt-of-an-sap-hana-table.md
@@ -10,11 +10,11 @@ description: You can use REST APIs to retrieve a prompt of a table through the M
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-6ddc138b-b2ab-4c53-8172-b2af26f4586d?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-Starting in MicroStrategy 2021 Update 6, you can use REST APIs to retrieve a prompt of a table through the Modeling service, if you have read access to the table.
+Starting in Strategy 2021 Update 6, you can use REST APIs to retrieve a prompt of a table through the Modeling service, if you have read access to the table.
 
 This workflow applies only to SAP HANA tables with input parameters because only these tables have prompts, and one input parameters corresponds to one prompt. For more information, see [KB48437: Support for SAP HANA calculation views with input parameters](https://community.microstrategy.com/s/article/Support-for-SAP-HANA-calculation-views-with-input-parameters?language=en_US).
 
@@ -22,7 +22,7 @@ This workflow applies only to SAP HANA tables with input parameters because only
 
 This workflow sample demonstrates how to retrieve an existing prompt of an SAP HANA table.
 
-The object ID of the table is `84AF2517E662417D9924FD678B44591A` and the object ID of the prompt is `339585B03F354D11AE8760C4489160F1`. The table is in the MicroStrategy Tutorial Advanced project and its project ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`.
+The object ID of the table is `84AF2517E662417D9924FD678B44591A` and the object ID of the prompt is `339585B03F354D11AE8760C4489160F1`. The table is in the Strategy Tutorial Advanced project and its project ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`.
 
 :::tip
 
@@ -93,7 +93,7 @@ Response Code: 200 (Table's prompt is returned successfully.)
 
 ## Retrieve a table prompt within a changeset
 
-You want to get the prompt of the same table object mentioned in [Retrieve a prompt of a table](#retrieve-a-prompt-of-a-table), while within a changeset. The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the MicroStrategy Tutorial Advanced project and its project ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`.
+You want to get the prompt of the same table object mentioned in [Retrieve a prompt of a table](#retrieve-a-prompt-of-a-table), while within a changeset. The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the Strategy Tutorial Advanced project and its project ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-tables-definition.md b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-tables-definition.md
index 6b0496500..3ad7ea3bc 100644
--- a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-tables-definition.md
+++ b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-tables-definition.md
@@ -10,7 +10,7 @@ description: You can use REST APIs to retrieve the definition for a table throug
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-95d4124f-c4e5-48ce-986e-a05c6d47069f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ You can use REST APIs to retrieve the definition for a table through the Modelin
 
 ## Retrieve a table's definition
 
-In this workflow sample, you want to get the definition of a table that is defined by a normal warehouse table. The object ID of the table is `862780DC499A14D74FEC7EB2EF317DA2`. The table is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definition of a table that is defined by a normal warehouse table. The object ID of the table is `862780DC499A14D74FEC7EB2EF317DA2`. The table is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -323,7 +323,7 @@ Response Code: 200 (The table's definition is returned successfully.)
 
 ## Retrieve a table's definition within a changeset
 
-In this workflow sample, you want to get the definition of the same table object mentioned in [Retrieve a table's definition](#retrieve-a-tables-definition), while within a changeset. The object ID of the table is `862780DC499A14D74FEC7EB2EF317DA2`. The table is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definition of the same table object mentioned in [Retrieve a table's definition](#retrieve-a-tables-definition), while within a changeset. The object ID of the table is `862780DC499A14D74FEC7EB2EF317DA2`. The table is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-a-partition-mapping-tables-definition.md b/docs/common-workflows/modeling/manage-table-objects/update-a-partition-mapping-tables-definition.md
index 83ff5c5ee..f634d01ce 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-a-partition-mapping-tables-definition.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-a-partition-mapping-tables-definition.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to update an existing partiti
 
 You can try this workflow with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-43769ee1-7480-4413-990a-13b50119b384).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-a-prompt-of-an-sap-hana-table.md b/docs/common-workflows/modeling/manage-table-objects/update-a-prompt-of-an-sap-hana-table.md
index 80a768341..09b50d0d3 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-a-prompt-of-an-sap-hana-table.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-a-prompt-of-an-sap-hana-table.md
@@ -10,11 +10,11 @@ description: You can use REST APIs to update a prompt of a table through the Mod
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-e3e4974a-dc93-4f79-9ea6-259a1693dc0d?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-Starting in MicroStrategy 2021 Update 6, you can use REST APIs to update a prompt of a table through the Modeling service.
+Starting in Strategy 2021 Update 6, you can use REST APIs to update a prompt of a table through the Modeling service.
 
 :::info
 
@@ -24,11 +24,11 @@ This workflow applies only to SAP HANA tables with input parameters because only
 
 :::tip
 
-You should at least have **read access** to the table to successfully complete this workflow. If the prompt you want to update is a managed object, **write access** to the table is also required. The managed prompts of an SAP HANA table with input parameters are automatically created by MicroStrategy by default. However, you can choose to replace these managed prompts with standalone ones by following the steps in [Update SAP HANA parameters for an SAP HANA table with input parameters](update-sap-hana-parameters.md). For more information on managed objects, see [About Managed Objects](https://www2.microstrategy.com/producthelp/2021/MDXCubeReporting/WebHelp/Lang_1033/Content/About_managed_objects.htm).
+You should at least have **read access** to the table to successfully complete this workflow. If the prompt you want to update is a managed object, **write access** to the table is also required. The managed prompts of an SAP HANA table with input parameters are automatically created by Strategy by default. However, you can choose to replace these managed prompts with standalone ones by following the steps in [Update SAP HANA parameters for an SAP HANA table with input parameters](update-sap-hana-parameters.md). For more information on managed objects, see [About Managed Objects](https://www2.microstrategy.com/producthelp/2021/MDXCubeReporting/WebHelp/Lang_1033/Content/About_managed_objects.htm).
 
 :::
 
-You want to update the prompt of a table. The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the MicroStrategy Tutorial Advanced project and its ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`. The object ID of the current prompt is `339585B03F354D11AE8760C4489160F1` and you want to update fields of the prompt, for example, the name and default answers.
+You want to update the prompt of a table. The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the Strategy Tutorial Advanced project and its ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`. The object ID of the current prompt is `339585B03F354D11AE8760C4489160F1` and you want to update fields of the prompt, for example, the name and default answers.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-a-tables-definition.md b/docs/common-workflows/modeling/manage-table-objects/update-a-tables-definition.md
index b215946ed..1e2d04997 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-a-tables-definition.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-a-tables-definition.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to update an existing table t
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-95d4124f-c4e5-48ce-986e-a05c6d47069f?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to update an existing table through the Modeling service.
 
-In this workflow sample, you update an existing `"CITY_CTR_SLS"` table object in the MicroStrategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you update an existing `"CITY_CTR_SLS"` table object in the Strategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-a-tables-physical-table-structure.md b/docs/common-workflows/modeling/manage-table-objects/update-a-tables-physical-table-structure.md
index 5cddabbe0..5daf43329 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-a-tables-physical-table-structure.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-a-tables-physical-table-structure.md
@@ -8,13 +8,13 @@ description: This workflow sample demonstrates how to update a table's physical
 
 You can try out this workflow at [REST API Playground].
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to update an existing table's physical table structure through the Modeling service.
 
-In this workflow sample, you update an existing `"CITY_CTR_SLS"` table's physical table structure in the MicroStrategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you update an existing `"CITY_CTR_SLS"` table's physical table structure in the Strategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-sap-hana-parameters.md b/docs/common-workflows/modeling/manage-table-objects/update-sap-hana-parameters.md
index 4146ceca3..e62bd9821 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-sap-hana-parameters.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-sap-hana-parameters.md
@@ -6,7 +6,7 @@ description: You can use REST APIs to update a prompt of a table through the Mod
 
 <Available since="2021 Update 6" />
 
-Similar to [Update a prompt of an SAP HANA table with input parameters](update-a-prompt-of-an-sap-hana-table.md), you can use REST APIs to update the table definition through the Modeling service starting in MicroStrategy 2021 Update 6.
+Similar to [Update a prompt of an SAP HANA table with input parameters](update-a-prompt-of-an-sap-hana-table.md), you can use REST APIs to update the table definition through the Modeling service starting in Strategy 2021 Update 6.
 
 :::info
 
@@ -32,7 +32,7 @@ To replace the current prompt with a standalone prompt, the prompt must either b
 
 :::
 
-The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the MicroStrategy Tutorial Advanced project and its ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`. Different operations on different SAP HANA parameters are done:
+The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the Strategy Tutorial Advanced project and its ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`. Different operations on different SAP HANA parameters are done:
 
 - Keep `IP_Column_Hier_Value_Help` the same
 - Reset `IP_Static_List`
diff --git a/docs/common-workflows/modeling/manage-time-zone-objects/create-a-time-zone-object.md b/docs/common-workflows/modeling/manage-time-zone-objects/create-a-time-zone-object.md
index 8d8dbead9..6c8995994 100644
--- a/docs/common-workflows/modeling/manage-time-zone-objects/create-a-time-zone-object.md
+++ b/docs/common-workflows/modeling/manage-time-zone-objects/create-a-time-zone-object.md
@@ -8,7 +8,7 @@ description: This workflow demonstrates how to create a new custom object throug
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-0bea31ca-d010-4214-8ad6-19c1906fbd5a?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-time-zone-objects/manage-time-zone-objects.md b/docs/common-workflows/modeling/manage-time-zone-objects/manage-time-zone-objects.md
index 76597184d..dacdfed74 100644
--- a/docs/common-workflows/modeling/manage-time-zone-objects/manage-time-zone-objects.md
+++ b/docs/common-workflows/modeling/manage-time-zone-objects/manage-time-zone-objects.md
@@ -7,7 +7,7 @@ description: You can use REST API requests to retrieve, create, and replace time
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-dcd45e43-c8f8-4198-9fa6-c0e3a22c0aaf?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-time-zone-objects/retrieve-a-list-of-time-zones-definitions.md b/docs/common-workflows/modeling/manage-time-zone-objects/retrieve-a-list-of-time-zones-definitions.md
index d3afd116f..df1ca6472 100644
--- a/docs/common-workflows/modeling/manage-time-zone-objects/retrieve-a-list-of-time-zones-definitions.md
+++ b/docs/common-workflows/modeling/manage-time-zone-objects/retrieve-a-list-of-time-zones-definitions.md
@@ -7,7 +7,7 @@ description: You can use REST APIs to retrieve definitions for a list of availab
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-8f48dce2-e826-4f45-98fb-c3ceed64b670?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-time-zone-objects/retrieve-a-time-zones-definition.md b/docs/common-workflows/modeling/manage-time-zone-objects/retrieve-a-time-zones-definition.md
index 924ff36ae..e5a019753 100644
--- a/docs/common-workflows/modeling/manage-time-zone-objects/retrieve-a-time-zones-definition.md
+++ b/docs/common-workflows/modeling/manage-time-zone-objects/retrieve-a-time-zones-definition.md
@@ -7,7 +7,7 @@ description: You can use REST APIs to retrieve the definition for a timezone thr
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-4845cf11-1e66-4530-b33f-730143143498?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-time-zone-objects/update-a-time-zone-object.md b/docs/common-workflows/modeling/manage-time-zone-objects/update-a-time-zone-object.md
index 7c1f44767..36c17fe9c 100644
--- a/docs/common-workflows/modeling/manage-time-zone-objects/update-a-time-zone-object.md
+++ b/docs/common-workflows/modeling/manage-time-zone-objects/update-a-time-zone-object.md
@@ -8,7 +8,7 @@ description: This workflow sample demonstrates how to update an existing custom
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-4845cf11-1e66-4530-b33f-730143143498?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-transformation-objects/create-a-transformation-object.md b/docs/common-workflows/modeling/manage-transformation-objects/create-a-transformation-object.md
index 41651011a..890a8066d 100644
--- a/docs/common-workflows/modeling/manage-transformation-objects/create-a-transformation-object.md
+++ b/docs/common-workflows/modeling/manage-transformation-objects/create-a-transformation-object.md
@@ -10,13 +10,13 @@ description: The workflow to create a transformation object.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-ad947705-6f6c-433c-ae10-cfe90ba9a364?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 ## Create a transformation object
 
-In this workflow sample, you want to create a `"Last year’s"` transformation object under the My Personal Objects/My Objects (MSTR User/My Objects) folder in the MicroStrategy Tutorial project. The folder object ID is `9B25D45A4834A213A70C10B1703D4A77`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to create a `"Last year’s"` transformation object under the My Personal Objects/My Objects (MSTR User/My Objects) folder in the Strategy Tutorial project. The folder object ID is `9B25D45A4834A213A70C10B1703D4A77`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -38,7 +38,7 @@ To create a transformation, in the request body, `"attributes"` contains a list
 
 `"forms"`: A list of transformation attribute forms, which are generated according to the base attribute key form. Each transformation attribute form contains a `"lookupTable"` and `"expression"`. The `"expression"` needs to be in either `"tree"` or `"tokens"` format.
 
-Tokens are a semi-structured representation of a MicroStrategy expression text including object references. For example, let’s say a filter expression is `"Revenue > Cost"`. When represented as tokens, the text is broken down into pieces (tokens) with information of what these parts represent in the metadata: (`"Revenue"`, `Revenue_ID`), (`">"`, `GreaterThan_ID`), (`"Cost"`, `Cost_ID`)
+Tokens are a semi-structured representation of a Strategy expression text including object references. For example, let’s say a filter expression is `"Revenue > Cost"`. When represented as tokens, the text is broken down into pieces (tokens) with information of what these parts represent in the metadata: (`"Revenue"`, `Revenue_ID`), (`">"`, `GreaterThan_ID`), (`"Cost"`, `Cost_ID`)
 
 `"mappingType"`: Defines a mapping relationship. This can be either `“one_to_one”` or `“many_to_many”`.
 
diff --git a/docs/common-workflows/modeling/manage-transformation-objects/manage-transformation-objects.md b/docs/common-workflows/modeling/manage-transformation-objects/manage-transformation-objects.md
index 7b4125ff5..dee915425 100644
--- a/docs/common-workflows/modeling/manage-transformation-objects/manage-transformation-objects.md
+++ b/docs/common-workflows/modeling/manage-transformation-objects/manage-transformation-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and update table
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-f3672b04-f9fa-4eab-8077-903d754d1797?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/common-workflows/modeling/manage-transformation-objects/retrieve-a-transformations-definition.md b/docs/common-workflows/modeling/manage-transformation-objects/retrieve-a-transformations-definition.md
index 2d0bea3ad..f319eea45 100644
--- a/docs/common-workflows/modeling/manage-transformation-objects/retrieve-a-transformations-definition.md
+++ b/docs/common-workflows/modeling/manage-transformation-objects/retrieve-a-transformations-definition.md
@@ -10,7 +10,7 @@ description: This topic covers the following workflows for retrieving an transfo
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-3fa0dd24-d717-46ba-831c-29cbfe75c3ba?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -18,7 +18,7 @@ This topic covers the following workflows for retrieving an transformation’s d
 
 ## Retrieve a transformation's definition
 
-In this workflow sample, you want to get the definition of the `"2 Weeks Ago"` transformation object. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definition of the `"2 Weeks Ago"` transformation object. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -92,7 +92,7 @@ Response Code: 200 (The transformation's definition is returned successfully.)
 
 ## Retrieve a transformation's definition within a changeset
 
-In this workflow sample, you want to get the definition of the same transformation object mentioned in [Retrieve a transformation's definition](#retrieve-a-transformations-definition), while within a changeset. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definition of the same transformation object mentioned in [Retrieve a transformation's definition](#retrieve-a-transformations-definition), while within a changeset. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 Changesets are used in this workflow. For information on how to create and use changesets, see [Changesets](/docs/common-workflows/modeling/changesets.md). If you plan to use the response of `GET /api/model/transformations/{transformationId}` to create a new table or update a specific table's definitions, you should associate all requests with one changeset.
 
@@ -168,13 +168,13 @@ Sample Response Code: 200 (The transformation's definition is returned successfu
 
 ## Retrieve a transformation's definition with transformation attribute form expressions in tree and tokens formats
 
-In this sample workflow, you want to get the definition of the `"2 Weeks Ago"` transformation object, with its transformation attribute form expressions returned in tree and tokens formats. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this sample workflow, you want to get the definition of the `"2 Weeks Ago"` transformation object, with its transformation attribute form expressions returned in tree and tokens formats. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 Expressions are presented in the following formats:
 
 - "text": A human-readable, but non-parsable text, describing the expression. This is the default format that is always returned in the response.
 - "tree": A tree data structure fully defining the expression. This format can be used if you want to examine and modify the expression programmatically.
-- "tokens": A list of parsed tokens. This format can be used if you want to examine and modify the expression using the parser component. Be aware that generating tokens requires additional time. Tokens are a semi-structured representation of MicroStrategy expression text that includes object references. For example, let’s say a filter expression is "Revenue > Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", `(">"`, `GreaterThan_ID`), (`"Cost"`, `Cost_ID`).
+- "tokens": A list of parsed tokens. This format can be used if you want to examine and modify the expression using the parser component. Be aware that generating tokens requires additional time. Tokens are a semi-structured representation of Strategy expression text that includes object references. For example, let’s say a filter expression is "Revenue > Cost". When the fact expression is represented as tokens, the text is broken down into pieces (tokens) with information about what these pieces represent in the metadata: ("Revenue", Revenue_ID), ("-", `(">"`, `GreaterThan_ID`), (`"Cost"`, `Cost_ID`).
 
 If `showExpressionAs` is omitted, the expression is returned in "text" format.
 
diff --git a/docs/common-workflows/modeling/manage-transformation-objects/update-a-transformations-definition.md b/docs/common-workflows/modeling/manage-transformation-objects/update-a-transformations-definition.md
index cde7f2f91..562dae998 100644
--- a/docs/common-workflows/modeling/manage-transformation-objects/update-a-transformations-definition.md
+++ b/docs/common-workflows/modeling/manage-transformation-objects/update-a-transformations-definition.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to update an existing transfo
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-ad947705-6f6c-433c-ae10-cfe90ba9a364?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to update an existing transformation through the Modeling service.
 
-In this workflow sample, you update an existing `"Last year’s"` transformation object under the My Personal Objects/My Objects (MSTR User/My Objects) folder in the MicroStrategy Tutorial project. The folder object ID is `9B25D45A4834A213A70C10B1703D4A77`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you update an existing `"Last year’s"` transformation object under the My Personal Objects/My Objects (MSTR User/My Objects) folder in the Strategy Tutorial project. The folder object ID is `9B25D45A4834A213A70C10B1703D4A77`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-user-hierarchy-objects/create-a-user-hierarchy.md b/docs/common-workflows/modeling/manage-user-hierarchy-objects/create-a-user-hierarchy.md
index cf5447f32..2b3f94416 100644
--- a/docs/common-workflows/modeling/manage-user-hierarchy-objects/create-a-user-hierarchy.md
+++ b/docs/common-workflows/modeling/manage-user-hierarchy-objects/create-a-user-hierarchy.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to create a user hierarchy ob
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c257416e-ee2c-46fc-9a71-f2ea390c8452?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to create a user hierarchy object through the Modeling service.
 
-You want to create a Time user hierarchy object, in the MicroStrategy Tutorial project, which contains the relationship between the Year, Month of Year, Quarter, Month, and Day attributes. The folder object ID is `8A1831FF494F528D02A4A8BF5FB73459`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a Time user hierarchy object, in the Strategy Tutorial project, which contains the relationship between the Year, Month of Year, Quarter, Month, and Day attributes. The folder object ID is `8A1831FF494F528D02A4A8BF5FB73459`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-user-hierarchy-objects/manage-user-hierarchy-objects.md b/docs/common-workflows/modeling/manage-user-hierarchy-objects/manage-user-hierarchy-objects.md
index ff86480fa..8bc12de7b 100644
--- a/docs/common-workflows/modeling/manage-user-hierarchy-objects/manage-user-hierarchy-objects.md
+++ b/docs/common-workflows/modeling/manage-user-hierarchy-objects/manage-user-hierarchy-objects.md
@@ -9,7 +9,7 @@ description: You can use REST API requests to retrieve, create, and delete user
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-6d8c1099-18f5-45c5-95ce-478e0299fe22?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -23,6 +23,6 @@ You can use REST API requests to retrieve, create, and delete user hierarchy obj
 
 For more information about the Modeling service, see [Configuring the Modeling Service](https://www2.microstrategy.com/producthelp/Current/InstallConfig/en-us/Content/modeling_service.htm).
 
-See [KB485058](https://community.microstrategy.com/s/article/Scope-and-limitations-of-the-User-Hierarchy-REST-APIs-in-MicroStrategy-2020-Update-2?language=en_US) for more information about the scope and limitations of user hierarchies in MicroStrategy 2020 Update 2.
+See [KB485058](https://community.microstrategy.com/s/article/Scope-and-limitations-of-the-User-Hierarchy-REST-APIs-in-Strategy-2020-Update-2?language=en_US) for more information about the scope and limitations of user hierarchies in Strategy 2020 Update 2.
 
 You cannot manage system hierarchies using the user hierarchies REST APIs mentioned in this section.
diff --git a/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-list-of-available-user-hierarchies.md b/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-list-of-available-user-hierarchies.md
index 10efea294..4ad5384a8 100644
--- a/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-list-of-available-user-hierarchies.md
+++ b/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-list-of-available-user-hierarchies.md
@@ -8,7 +8,7 @@ description: This workflow sample demonstrates how to retrieve the list of avail
 
 This workflow sample demonstrates how to retrieve the list of available user hierarchies in one project within a changeset.
 
-You want to get all available user hierarchies in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get all available user hierarchies in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-user-hierarchys-definition.md b/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-user-hierarchys-definition.md
index 05b79712f..013ae803f 100644
--- a/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-user-hierarchys-definition.md
+++ b/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-user-hierarchys-definition.md
@@ -10,13 +10,13 @@ description: This workflow sample demonstrates how to retrieve an user hierarchy
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-6403c6f8-0173-4b2c-826c-029742877689?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 This workflow sample demonstrates how to retrieve an user hierarchy's definition within a changeset.
 
-You want to get the definition of the Time user hierarchy object, in the MicroStrategy Tutorial project, which contains the relationship between the Year, Month of Year, Quarter, Month, and Day attributes. The object ID of the user hierarchy is `B793B55C11D3E4E51000E887EC6DE8A4`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the Time user hierarchy object, in the Strategy Tutorial project, which contains the relationship between the Year, Month of Year, Quarter, Month, and Day attributes. The object ID of the user hierarchy is `B793B55C11D3E4E51000E887EC6DE8A4`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-user-hierarchy-objects/update-a-user-hierarchys-definition.md b/docs/common-workflows/modeling/manage-user-hierarchy-objects/update-a-user-hierarchys-definition.md
index 1b1e6724d..686ee70c8 100644
--- a/docs/common-workflows/modeling/manage-user-hierarchy-objects/update-a-user-hierarchys-definition.md
+++ b/docs/common-workflows/modeling/manage-user-hierarchy-objects/update-a-user-hierarchys-definition.md
@@ -10,7 +10,7 @@ description: This workflow sample demonstrates how to update an user hierarchy's
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-c257416e-ee2c-46fc-9a71-f2ea390c8452?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
diff --git a/docs/getting-started/authentication.md b/docs/getting-started/authentication.md
index 0a7670ef7..2592dbe74 100644
--- a/docs/getting-started/authentication.md
+++ b/docs/getting-started/authentication.md
@@ -6,7 +6,7 @@ description: The REST API provides authentication endpoints to initiate a sessio
 
 The REST API provides authentication endpoints to initiate a session with the Intelligence Server. It supports multiple authentication modes such as Standard, LDAP, SAML, and so on.
 
-The diagram below shows the workflow when the MicroStrategy REST API is used to authenticate a user.
+The diagram below shows the workflow when the Strategy REST API is used to authenticate a user.
 
 ![REST_Login_Workflow](../images/REST_Login_Workflow.png)
 
@@ -18,7 +18,7 @@ The diagram below shows the workflow when the MicroStrategy REST API is used to
 
 :::tip
 
-The MicroStrategy REST server maintains an HTTP session for every client connecting to it.
+The Strategy REST server maintains an HTTP session for every client connecting to it.
 
 :::
 
@@ -30,7 +30,7 @@ Once the REST API layer has validated the user's credentials using the specified
 
 - **Session cookie**
 
-The MicroStrategy REST framework currently relies on an HTTP session. The Java EE server (for example, Tomcat) sends a session cookie in the response header for the client to maintain. If a browser is handling requests, it will also handle the cookies. However, if you are using your own client, you need to maintain the cookie and include it in further requests, together with the authorization token.
+The Strategy REST framework currently relies on an HTTP session. The Java EE server (for example, Tomcat) sends a session cookie in the response header for the client to maintain. If a browser is handling requests, it will also handle the cookies. However, if you are using your own client, you need to maintain the cookie and include it in further requests, together with the authorization token.
 
 - **Session timeout**
 
diff --git a/docs/getting-started/configure-clustered-environments.md b/docs/getting-started/configure-clustered-environments.md
index 2d1a478eb..554f2025b 100644
--- a/docs/getting-started/configure-clustered-environments.md
+++ b/docs/getting-started/configure-clustered-environments.md
@@ -3,7 +3,7 @@ title: Configure clustered environments
 description: This page provides information for clustered environment configuration.
 ---
 
-The MicroStrategy REST platform provides a highly scalable solution to meet your performance needs by installing multiple instances of REST servers that can communicate with an Intelligence Server cluster.
+The Strategy REST platform provides a highly scalable solution to meet your performance needs by installing multiple instances of REST servers that can communicate with an Intelligence Server cluster.
 
 ![REST Configuration](../images/REST_Configuration.png)
 
@@ -22,9 +22,9 @@ You must configure certain properties for horizontal scaling of REST Servers.
   - /WEB-INF/classes/config/\*
   - /WEB-INF/classes/auth/\*
 
-- The MicroStrategyLibrary REST Server provides an admin page to modify some of the configuration settings.
+- The StrategyLibrary REST Server provides an admin page to modify some of the configuration settings.
 
-  The MicroStrategy REST Server contains default values for configuration in …/config/configDefaults.properties. The configDefaults.properties file contains key-value pairs of configuration options. To specify a configuration option, the desired key can be copied from the configDefaults.properties file, and saved into configOverride.properties with a different value.
+  The Strategy REST Server contains default values for configuration in …/config/configDefaults.properties. The configDefaults.properties file contains key-value pairs of configuration options. To specify a configuration option, the desired key can be copied from the configDefaults.properties file, and saved into configOverride.properties with a different value.
 
   However, if you use this method to make configuration changes and your REST Server is running in a clustered environment, only one of the nodes in the cluster is modified. To resolve this problem, you can use a shared drive across all nodes via Mount or Symbolic links. If you use Symbolic links, you need to enable the Tomcat property allowLinking. Refer to the Apache Tomcat Configuration Reference.
 
diff --git a/docs/getting-started/embedding-sdk.md b/docs/getting-started/embedding-sdk.md
index d115cf24d..e819afc83 100644
--- a/docs/getting-started/embedding-sdk.md
+++ b/docs/getting-started/embedding-sdk.md
@@ -1,11 +1,11 @@
 ---
 title: Using REST API with Embedding SDK
-description: You can use MicroStrategy REST API together with MicroStrategy Embedding SDK.
+description: You can use Strategy REST API together with Strategy Embedding SDK.
 ---
 
 ## What is the Embedding SDK?
 
-The Embedding SDK allows you to quickly integrate a MicroStrategy dashboard into a web application in a responsive manner. It also provides resources to add functionality such as controlling navigation, retrieving and applying filters, setting properties, and managing events, and supports different authentication environments.
+The Embedding SDK allows you to quickly integrate a Strategy dashboard into a web application in a responsive manner. It also provides resources to add functionality such as controlling navigation, retrieving and applying filters, setting properties, and managing events, and supports different authentication environments.
 
 ## Common use cases of REST API with Embedding SDK
 
diff --git a/docs/getting-started/getting-started.md b/docs/getting-started/getting-started.md
index 190edface..e9605c6ea 100644
--- a/docs/getting-started/getting-started.md
+++ b/docs/getting-started/getting-started.md
@@ -1,9 +1,9 @@
 ---
 title: Getting started
-description: The following topics are designed to help you get started using the MicroStrategy REST API.
+description: The following topics are designed to help you get started using the Strategy REST API.
 ---
 
-To get started, view the following topics to know the basics of the MicroStrategy REST API:
+To get started, view the following topics to know the basics of the Strategy REST API:
 
 - [REST API architecture](rest-api-architecture.md)
 - [REST API families](rest-api-families.md)
@@ -18,7 +18,7 @@ After learning the basics, view the following topics to understand some general
 
 You can use the REST API Explorer and Playground as tools to learn more and run live REST API calls:
 
-- [MicroStrategy REST API Explorer](microstrategy-rest-api-explorer.md)
-- [MicroStrategy REST API Playground](playground.md)
+- [Strategy REST API Explorer](microstrategy-rest-api-explorer.md)
+- [Strategy REST API Playground](playground.md)
 
 For more specific REST API topics, view the [common workflows](../common-workflows/common-workflows.md).
diff --git a/docs/getting-started/handle-rest-api-exceptions.md b/docs/getting-started/handle-rest-api-exceptions.md
index 84af7b44a..2d68cbf34 100644
--- a/docs/getting-started/handle-rest-api-exceptions.md
+++ b/docs/getting-started/handle-rest-api-exceptions.md
@@ -1,9 +1,9 @@
 ---
 title: Handle REST API errors
-description: This page provides a guidance on designing exception workflows when using MicroStrategy REST API.
+description: This page provides a guidance on designing exception workflows when using Strategy REST API.
 ---
 
-When developers use MicroStrategy REST APIs to build dynamic applications, they need to add code to handle error conditions. The instructions below are designed to provide a guidance on designing exception workflows when using MicroStrategy REST API.
+When developers use Strategy REST APIs to build dynamic applications, they need to add code to handle error conditions. The instructions below are designed to provide a guidance on designing exception workflows when using Strategy REST API.
 
 ## 1. Understand the status code
 
@@ -33,12 +33,12 @@ When you encounter REST API error, you may receive an error message that looks l
 ```json
 {
   "code": "ERR001",
-  "message": "MicroStrategy Intelligence Server is not configured to support LDAP authentication.",
+  "message": "Strategy Intelligence Server is not configured to support LDAP authentication.",
   "iServerCode": -214720549
 }
 ```
 
-The value of `code` is a MicroStrategy REST API Server code. The table below provides a general description of each error code. Use the error code to create meaningful text for the error message that will help users when they encounter errors.
+The value of `code` is a Strategy REST API Server code. The table below provides a general description of each error code. Use the error code to create meaningful text for the error message that will help users when they encounter errors.
 
 | Error code | Description                     |
 | :--------- | :------------------------------ |
@@ -65,7 +65,7 @@ The value of `code` is a MicroStrategy REST API Server code. The table below pro
 
 ## 4. IServer error code
 
-The MicroStrategy error message may also contain an integer value for `iServerCode`. This integer value maps to a constant value in the [WebAPIErrorCodes](https://www2.microstrategy.com/producthelp/Current/ReferenceFiles/reference/com/microstrategy/utils/localization/WebAPIErrorCodes.html) class. There are many error codes in this class. You should look at the `iServerCode` error and decide if you think it provides meaningful context. If so, you may want to handle it in your code.
+The Strategy error message may also contain an integer value for `iServerCode`. This integer value maps to a constant value in the [WebAPIErrorCodes](https://www2.microstrategy.com/producthelp/Current/ReferenceFiles/reference/com/microstrategy/utils/localization/WebAPIErrorCodes.html) class. There are many error codes in this class. You should look at the `iServerCode` error and decide if you think it provides meaningful context. If so, you may want to handle it in your code.
 
 If needed, you can also find more information in the Library Sever's error log, such as stack traces.
 
@@ -140,7 +140,7 @@ Example:
 
 #### 404 Not Found
 
-A 404 error means the requested endpoint doesn't exist, or the endpoint is valid but the resource does not exist. You might not always get a response JSON for this status code depending on your URL. MicroStrategy REST API also uses this status code for not supported HTTP methods.
+A 404 error means the requested endpoint doesn't exist, or the endpoint is valid but the resource does not exist. You might not always get a response JSON for this status code depending on your URL. Strategy REST API also uses this status code for not supported HTTP methods.
 
 Example:
 
diff --git a/docs/getting-started/improve-performance-by-working-with-partial-resources/field-selection-for-data-api-v2-result-fetching-endpoints.md b/docs/getting-started/improve-performance-by-working-with-partial-resources/field-selection-for-data-api-v2-result-fetching-endpoints.md
index bb5641fb6..18027dc01 100644
--- a/docs/getting-started/improve-performance-by-working-with-partial-resources/field-selection-for-data-api-v2-result-fetching-endpoints.md
+++ b/docs/getting-started/improve-performance-by-working-with-partial-resources/field-selection-for-data-api-v2-result-fetching-endpoints.md
@@ -1,17 +1,17 @@
 ---
 title: Field selection for data API v2 result-fetching endpoints
-description: For Data API v2 result-fetching endpoints, the MicroStrategy REST API provides a specialized flavor of field selection support. It is tailored for Data API specific use cases using a similar syntax.
+description: For Data API v2 result-fetching endpoints, the Strategy REST API provides a specialized flavor of field selection support. It is tailored for Data API specific use cases using a similar syntax.
 ---
 
 :::tip
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-a6457d75-f616-4092-9485-e6007627b73d?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
-For Data API v2 result-fetching endpoints, the MicroStrategy REST API provides a specialized flavor of field selection support. It is tailored for Data API specific use cases using a similar syntax.
+For Data API v2 result-fetching endpoints, the Strategy REST API provides a specialized flavor of field selection support. It is tailored for Data API specific use cases using a similar syntax.
 
 The endpoints are:
 
@@ -27,7 +27,7 @@ The endpoints are:
 Keep in the mind the following specific considerations for Data API v2 result-fetching endpoints:
 
 - When performance is a concern, we encourage reducing computations. Rather than just transferring data to the client, use existing [filter functionality](../../common-workflows/analytics/filter-data/filter-data.md), such as `requestedObjects`, view filters, and metric limits.
-- General top-level field selection has been supported since the MicroStrategy 2020 release. However, for the Data API, you rarely exclude top-level fields. If the client only needs a definition, and not data, it is simpler to use the Get Definition endpoints instead.
+- General top-level field selection has been supported since the Strategy 2020 release. However, for the Data API, you rarely exclude top-level fields. If the client only needs a definition, and not data, it is simpler to use the Get Definition endpoints instead.
 - Using field selection instead of the recommended ways above, while reducing data transfer size, may lead to unused computations and unnecessary post-computation filtering costs. This is suboptimal in terms of performance.
 
 Therefore, general field selection is designed to not apply to these endpoints. On the other hand, we are also aware of valid client use cases and make them possible through field selection syntax in a disciplined way.
@@ -45,9 +45,9 @@ Some things to keep in mind:
 
 ## Supported rule: Filtering metric value representations and other per metric-cell information
 
-MicroStrategy Library Server 2020 Update 2 and above
+Strategy Library Server 2020 Update 2 and above
 
-MicroStrategy Intelligence Server 2020 Update 2 and above
+Strategy Intelligence Server 2020 Update 2 and above
 
 By default, metric values are returned in both raw representation (data.metricValues.raw) and formatted representation (`data.metricValues.formatted`). Other metric cell information under extras, such as optional thresholds, are returned as well.
 
@@ -59,7 +59,7 @@ Clients can request part of these fields by using the following exclusion rules:
 
 Exclusion rules can significantly improve the performance of certain clients, such as the ones mentioned below, roughly halving the size of data transfers:
 
-- Frontend apps and exporters that render results similarly as MicroStrategy client products, by focusing on human-reader formatted values that can be rendered directly. These frontend apps and exporters may need extras for determining advanced formatting.
+- Frontend apps and exporters that render results similarly as Strategy client products, by focusing on human-reader formatted values that can be rendered directly. These frontend apps and exporters may need extras for determining advanced formatting.
 
 - Data connectors that focus on raw values are compact and easily parsed and post-processed.
 
diff --git a/docs/getting-started/improve-performance-by-working-with-partial-resources/improve-performance-by-working-with-partial-resources.md b/docs/getting-started/improve-performance-by-working-with-partial-resources/improve-performance-by-working-with-partial-resources.md
index acb04011b..71c99a025 100644
--- a/docs/getting-started/improve-performance-by-working-with-partial-resources/improve-performance-by-working-with-partial-resources.md
+++ b/docs/getting-started/improve-performance-by-working-with-partial-resources/improve-performance-by-working-with-partial-resources.md
@@ -7,13 +7,13 @@ description: While API endpoints define full response models, you may only need
 
 You can try these workflows with [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-ea1451c1-67fc-44c2-9f08-427b6cd60393?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
 While API endpoints define full response models, you may only need a subset of the available data. You can ask the server to only send the fields you need and get a partial response instead. This helps improve performance, since extra resources are not devoted transferring, parsing, and storing unnecessary fields.
 
-MicroStrategy supports top-level field selection on most endpoints.
+Strategy supports top-level field selection on most endpoints.
 
 - For endpoints that return a JSON object, the client specifies which fields to include for the root object.
 - For endpoints that return a JSON array, the client specifies which fields to include for every element of the root array.
@@ -56,7 +56,7 @@ The fields query parameter is exposed on endpoints that support field selection.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-6ea58912-5546-4576-a94b-01db9437118d?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -67,7 +67,7 @@ Here is an example using `GET /api/projects/MicroStrategy%20Tutorial?fields=id,n
 ```json
 {
   "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-  "name": "MicroStrategy Tutorial",
+  "name": "Strategy Tutorial",
   "owner": {
     "name": "Administrator",
     "id": "54F3D26011D2896560009A8E67019608"
@@ -81,10 +81,10 @@ Here is an example of full representation without fields.
 {
   "acg": 255,
   "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-  "name": "MicroStrategy Tutorial",
+  "name": "Strategy Tutorial",
   "status": 0,
   "alias": "",
-  "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+  "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
   "dateCreated": "2001-01-02T20:42:04.000+0000",
   "dateModified": "2019-06-28T03:32:24.000+0000",
   "owner": {
@@ -100,7 +100,7 @@ Here is an example of full representation without fields.
 
 You can try out this workflow at [REST API Playground](https://www.postman.com/microstrategysdk/workspace/microstrategy-rest-api/folder/16131298-2f86322d-d0b2-4005-881e-f8b878c83680?ctx=documentation).
 
-Learn more about MicroStrategy REST API Playground [here](/docs/getting-started/playground.md).
+Learn more about Strategy REST API Playground [here](/docs/getting-started/playground.md).
 
 :::
 
@@ -116,7 +116,7 @@ Here is an example using `GET /api/projects?fields=id,name`.
   },
   {
     "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-    "name": "MicroStrategy Tutorial"
+    "name": "Strategy Tutorial"
   }
 ]
 ```
diff --git a/docs/getting-started/microstrategy-rest-api-explorer.md b/docs/getting-started/microstrategy-rest-api-explorer.md
index 669968f45..fe7cb6a28 100644
--- a/docs/getting-started/microstrategy-rest-api-explorer.md
+++ b/docs/getting-started/microstrategy-rest-api-explorer.md
@@ -1,13 +1,13 @@
 ---
-title: MicroStrategy REST API Explorer
-description: Instructions for using MicroStrategy REST API Explorer, our official REST API documentation.
+title: Strategy REST API Explorer
+description: Instructions for using Strategy REST API Explorer, our official REST API documentation.
 ---
 
 ## Overview
 
-[MicroStrategy API Explorer](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs) serves as the REST API reference guide, providing a comprehensive list of the available MicroStrategy REST APIs grouped into REST API families. Common MicroStrategy platform capabilities are exposed in a RESTful web service.
+[Strategy API Explorer](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs) serves as the REST API reference guide, providing a comprehensive list of the available Strategy REST APIs grouped into REST API families. Common Strategy platform capabilities are exposed in a RESTful web service.
 
-It is hosted on [demo.microstrategy.com](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs). You can also use the API Explorer shipped in your MicroStrategyLibrary server. Once the MicroStrategyLibrary server is started, you access the MicroStrategy REST API Explorer at `{YOUR_LIBRARY_SERVER_URL}/api-docs/`, e.g., `https://env-263053.customer.cloud.microstrategy.com/MicroStrategyLibrary/api-docs`.
+It is hosted on [demo.microstrategy.com](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs). You can also use the API Explorer shipped in your StrategyLibrary server. Once the StrategyLibrary server is started, you access the Strategy REST API Explorer at `{YOUR_LIBRARY_SERVER_URL}/api-docs/`, e.g., `https://env-263053.customer.cloud.microstrategy.com/MicroStrategyLibrary/api-docs`.
 
 When you access the server, you are able to see the available APIs. You can drill down into these to see HTTP headers and input and output information for each request, and enter values to try out the APIs.
 
diff --git a/docs/getting-started/playground.md b/docs/getting-started/playground.md
index 3e66bfb15..9d059c876 100644
--- a/docs/getting-started/playground.md
+++ b/docs/getting-started/playground.md
@@ -1,18 +1,18 @@
 ---
-title: MicroStrategy REST API Playground
-description: MicroStrategy REST API Playground is a place you can see live demos of our REST API, API specifications, and code examples. You can also play with it without writing a single line of code.
+title: Strategy REST API Playground
+description: Strategy REST API Playground is a place you can see live demos of our REST API, API specifications, and code examples. You can also play with it without writing a single line of code.
 ---
 
 ## What is the playground?
 
-MicroStrategy REST API Playground is a place you can see live demos of our REST API, API specifications, and code examples. You can also play with it without writing a single line of code.
+Strategy REST API Playground is a place you can see live demos of our REST API, API specifications, and code examples. You can also play with it without writing a single line of code.
 
 [This GitHub Page](https://github.com/MicroStrategy/rest-api-playground) provides the instructions for you to set up and start to use it. You can access the playground at [https://www.postman.com/microstrategysdk](https://www.postman.com/microstrategysdk). If you are not familiar Postman interface, be sure to check out [the documentation](https://learning.postman.com/docs/getting-started/introduction/) on Postman's learning center.
 
 There are two collections in the workspace:
 
-- MicroStrategy REST API: Use it as API Documentation. It contains examples and built-in scripts to save the context information after some requests, such as `authToken`, `userId`.
-- MicroStrategy REST API Workflows: It contains workflow examples. You can pick a folder and run all the requests.
+- Strategy REST API: Use it as API Documentation. It contains examples and built-in scripts to save the context information after some requests, such as `authToken`, `userId`.
+- Strategy REST API Workflows: It contains workflow examples. You can pick a folder and run all the requests.
 
 You need to pick an environment to run the requests. There are two environments shipped:
 
diff --git a/docs/getting-started/rest-api-architecture.md b/docs/getting-started/rest-api-architecture.md
index 2774c5cb3..05f18be12 100644
--- a/docs/getting-started/rest-api-architecture.md
+++ b/docs/getting-started/rest-api-architecture.md
@@ -1,9 +1,9 @@
 ---
 title: REST API architecture
-description: The MicroStrategy REST framework follows REST conventions to provide a simplified interface for utilizing platform capabilities through JSON data via HTTP(s) protocol.
+description: The Strategy REST framework follows REST conventions to provide a simplified interface for utilizing platform capabilities through JSON data via HTTP(s) protocol.
 ---
 
-The MicroStrategy REST framework follows REST conventions to provide a simplified interface for utilizing platform capabilities through JSON data via HTTP(s) protocol. You can use the REST framework to perform actions such as:
+The Strategy REST framework follows REST conventions to provide a simplified interface for utilizing platform capabilities through JSON data via HTTP(s) protocol. You can use the REST framework to perform actions such as:
 
 - [Authentication](authentication.md)
 - [Retrieve data](../common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md)
@@ -12,7 +12,7 @@ The MicroStrategy REST framework follows REST conventions to provide a simplifie
 
 The REST framework is scalable, allowing you to configure a clustered environment that supports multiple instances of REST servers communicating with an Intelligence Server cluster.
 
-The REST Framework layer is built on top of the existing WebObjects and XML API layers. It provides a comprehensive set of APIs that allow developers to quickly and easily customize MicroStrategy BI functionality.
+The REST Framework layer is built on top of the existing WebObjects and XML API layers. It provides a comprehensive set of APIs that allow developers to quickly and easily customize Strategy BI functionality.
 
 ![REST Architecture](../images/REST_architecture.png)
 
diff --git a/docs/getting-started/rest-api-families.md b/docs/getting-started/rest-api-families.md
index 03302fc15..3acec6eff 100644
--- a/docs/getting-started/rest-api-families.md
+++ b/docs/getting-started/rest-api-families.md
@@ -1,10 +1,10 @@
 ---
 sidebar_label: REST API families
-title: MicroStrategy REST API families
-description: The MicroStrategy REST API Explorer lets you drill down into the individual APis. You can see HTTP headers and input and output information for each request, and enter values to try out the APIs.
+title: Strategy REST API families
+description: The Strategy REST API Explorer lets you drill down into the individual APis. You can see HTTP headers and input and output information for each request, and enter values to try out the APIs.
 ---
 
-The [MicroStrategy REST API Explorer](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/) lets you drill down into the individual APis. You can see HTTP headers and input and output information for each request, and enter values to try out the APIs.
+The [Strategy REST API Explorer](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/) lets you drill down into the individual APis. You can see HTTP headers and input and output information for each request, and enter values to try out the APIs.
 
 ## [Authentication API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication)
 
@@ -48,11 +48,11 @@ The Custom Groups API family allows developers to obtain a custom group's defini
 
 ## [Datasets API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasets)
 
-The Datasets API family allows developers to push external data directly to the MicroStrategy Intelligence Server. This data can be used to create a dataset or to modify an existing dataset in a Data Import cube. Once the data has been pushed to the Intelligence Server, developers can use the Cubes API or the Reports API to manipulate that data. This API is often referred to as the Push Data API.
+The Datasets API family allows developers to push external data directly to the Strategy Intelligence Server. This data can be used to create a dataset or to modify an existing dataset in a Data Import cube. Once the data has been pushed to the Intelligence Server, developers can use the Cubes API or the Reports API to manipulate that data. This API is often referred to as the Push Data API.
 
 ## [Datasource management API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management)
 
-The Datasource Management API family allows administrators to create, update, and delete database connections in the MicroStrategy metadata. This functionality can be used to automate the update of data source credentials.
+The Datasource Management API family allows administrators to create, update, and delete database connections in the Strategy metadata. This functionality can be used to automate the update of data source credentials.
 
 ## [Derived elements API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Derived%20Elements)
 
@@ -68,7 +68,7 @@ The Drivers API family allows developers to obtain drivers' definition and updat
 
 ## [Emails API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Emails)
 
-The Emails API family allows administrators and developers to send emails using MicroStrategy Distribution Services email transmitters.
+The Emails API family allows administrators and developers to send emails using Strategy Distribution Services email transmitters.
 
 ## [Facts API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Facts)
 
@@ -88,7 +88,7 @@ The Library API family exposes the publishing workflow, allowing requests to pub
 
 ## [Object management API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Object%20Management)
 
-The Object Management API family exposes the ability to programmatically manage objects in the MicroStrategy metadata. Endpoints can be used to certify or de-certify a report or dashboard, delete objects, and update object info for any object type.
+The Object Management API family exposes the ability to programmatically manage objects in the Strategy metadata. Endpoints can be used to certify or de-certify a report or dashboard, delete objects, and update object info for any object type.
 
 ## [Packages API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Packages)
 
@@ -124,7 +124,7 @@ The Security Roles API family allows administrators and developers to obtain a l
 
 ## [System administration API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System%20Administration)
 
-The System Administration API family allows administrators and developers to programmatically configure the settings related to the MicroStrategy Library web application. For example, this functionality can be used to configure default values related to the authentication process, set up trust relationships to the Intelligence Server, and more.
+The System Administration API family allows administrators and developers to programmatically configure the settings related to the Strategy Library web application. For example, this functionality can be used to configure default values related to the authentication process, set up trust relationships to the Intelligence Server, and more.
 
 ## [System hierarchy API](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System%20Hierarchy)
 
diff --git a/docs/index.md b/docs/index.md
index 8151998f6..b6f98b5d0 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -2,24 +2,24 @@
 title: Introduction to REST API
 date: Last Modified
 slug: /
-description: The MicroStrategy REST API is a RESTful application that uses HTTP requests such as POST, DELETE, and GET. It is designed to help developers build data-driven client applications quickly and easily. It does this by providing light-weight JSON data that is easy to consume because it includes raw data without direct formatting. Developers can use the MicroStrategy REST API programmatically in their own code, or in a tool like curl.
+description: The Strategy REST API is a RESTful application that uses HTTP requests such as POST, DELETE, and GET. It is designed to help developers build data-driven client applications quickly and easily. It does this by providing light-weight JSON data that is easy to consume because it includes raw data without direct formatting. Developers can use the Strategy REST API programmatically in their own code, or in a tool like curl.
 ---
 
-The MicroStrategy REST API is a RESTful application that uses HTTP requests such as POST, DELETE, and GET. It is designed to help developers build data-driven client applications quickly and easily. It does this by providing light-weight JSON data that is easy to consume because it includes raw data without direct formatting. Developers can use the MicroStrategy REST API programmatically in their own code, or in a tool like curl.
+The Strategy REST API is a RESTful application that uses HTTP requests such as POST, DELETE, and GET. It is designed to help developers build data-driven client applications quickly and easily. It does this by providing light-weight JSON data that is easy to consume because it includes raw data without direct formatting. Developers can use the Strategy REST API programmatically in their own code, or in a tool like curl.
 
-The following topics are designed to help you understand and use the MicroStrategy REST API.
+The following topics are designed to help you understand and use the Strategy REST API.
 
 ## [Getting started](getting-started/getting-started.md)
 
-Quick overviews introduce you to the MicroStrategy REST framework, configuring clustered environments, handling exceptions, and the MicroStrategy REST API Explorer, which serves as the REST API reference guide.
+Quick overviews introduce you to the Strategy REST framework, configuring clustered environments, handling exceptions, and the Strategy REST API Explorer, which serves as the REST API reference guide.
 
 ## [REST API families](getting-started/rest-api-families.md)
 
-MicroStrategy REST APIs are grouped into API families. These families represent functionality, such as Authentication or Browsing, or categories, such as Cubes or Security Roles.
+Strategy REST APIs are grouped into API families. These families represent functionality, such as Authentication or Browsing, or categories, such as Cubes or Security Roles.
 
 ## [Common REST API workflows](common-workflows/common-workflows.md)
 
-Descriptions and quick start guides are provided for common MicroStrategy REST API workflows, such as authentication, folder browsing, filtering data, searching, retrieving data from the Intelligence Server (referred to as the JSON Data API), uploading external data (referred to as the Push Data API), and manage attributes, relationships, facts, tables, filters, prompts, derived elements, and security filters through the Modeling service.
+Descriptions and quick start guides are provided for common Strategy REST API workflows, such as authentication, folder browsing, filtering data, searching, retrieving data from the Intelligence Server (referred to as the JSON Data API), uploading external data (referred to as the Push Data API), and manage attributes, relationships, facts, tables, filters, prompts, derived elements, and security filters through the Modeling service.
 
 ## [REST API samples](microstrategy-rest-api-samples/microstrategy-rest-api-samples.md)
 
diff --git a/docs/microstrategy-rest-api-samples/create-reports-on-the-fly.md b/docs/microstrategy-rest-api-samples/create-reports-on-the-fly.md
index 800252387..ee7c679ef 100644
--- a/docs/microstrategy-rest-api-samples/create-reports-on-the-fly.md
+++ b/docs/microstrategy-rest-api-samples/create-reports-on-the-fly.md
@@ -8,7 +8,7 @@ This interactive REST API sample highlights the ability to create reports on the
 
 This sample gets data from an Intelligent cube or a report. It uses the attributes and metrics from the report definition to populate two list boxes. When a user selects attributes and metrics from the list boxes, an ad-hoc report is run on the cube and the results are displayed. A specified number of rows are returned, with additional rows displayed each time the user clicks the forward and backward arrows. Two types of view filters allow the user to narrow the results that are displayed. An auto-load button lets a user decide whether to automatically apply changes as they are made.
 
-You can [view a live demo](https://microstrategy.github.io/data-api-demo/site/) of the sample. You can also [download the code](https://github.com/microstrategy/data-api-demo/) for this sample to help you understand and use MicroStrategy REST APIs in your application.
+You can [view a live demo](https://microstrategy.github.io/data-api-demo/site/) of the sample. You can also [download the code](https://github.com/microstrategy/data-api-demo/) for this sample to help you understand and use Strategy REST APIs in your application.
 
 ## Understand the REST API workflow in the sample
 
@@ -16,7 +16,7 @@ This sample uses REST APIs to authenticate the user, get a list of reports and c
 
 **1.** `POST /api/auth/login`
 
-This REST API authenticates a user. It creates a MicroStrategy session using credentials for the user and a specified authentication mode. It returns an authorization token, which is used by subsequent REST API calls. In this sample, the API is used to create a configuration session.
+This REST API authenticates a user. It creates a Strategy session using credentials for the user and a specified authentication mode. It returns an authorization token, which is used by subsequent REST API calls. In this sample, the API is used to create a configuration session.
 
 **2.** `GET /api/searches/results`
 
@@ -57,7 +57,7 @@ The config.js file is used to configure the sample for your environment. Set val
 | Variable name | Variable description                                                                                                                               |
 | :------------ | :------------------------------------------------------------------------------------------------------------------------------------------------- |
 | restServerURL | Base URL of the REST API. For example, `http://localhost:8080/MicroStrategyLibrary/api`. The REST API endpoints will be appended to this base URL. |
-| projectId     | ID of the MicroStrategy project that will be used by the REST API endpoints. For example, "B19DEDCC11D4E0EFC000EB9495D0F44F".                      |
+| projectId     | ID of the Strategy project that will be used by the REST API endpoints. For example, "B19DEDCC11D4E0EFC000EB9495D0F44F".                           |
 | username      | Username that will be authenticated. The default value is "administrator".                                                                         |
 | password      | Password for username that will be authenticated.                                                                                                  |
 | cubes         | Array of cube IDs. These cubes are listed in the Datasets panel on the left of the sample, under Cubes. Be sure to use valid cube IDs.             |
diff --git a/docs/microstrategy-rest-api-samples/microstrategy-rest-api-samples.md b/docs/microstrategy-rest-api-samples/microstrategy-rest-api-samples.md
index a4beccdee..6ddbc638d 100644
--- a/docs/microstrategy-rest-api-samples/microstrategy-rest-api-samples.md
+++ b/docs/microstrategy-rest-api-samples/microstrategy-rest-api-samples.md
@@ -1,5 +1,5 @@
 ---
-title: MicroStrategy REST API samples
+title: Strategy REST API samples
 description: A variety of samples are provided to illustrate how to use REST APIs
 ---
 
diff --git a/docs/whats-new.md b/docs/whats-new.md
index 59600985b..4830671f5 100644
--- a/docs/whats-new.md
+++ b/docs/whats-new.md
@@ -4,15 +4,15 @@ sidebar_label: What's new
 Description: What's New in the REST API.
 ---
 
-## MicroStrategy ONE (September 2024)
+## Strategy ONE (September 2024)
 
 - [Managing bookmarks](common-workflows/administration/manage-bookmarks/manage-bookmarks.md). Retrieve, create, update, and delete bookmarks.
 
-## MicroStrategy ONE (June 2024)
+## Strategy ONE (June 2024)
 
 - [Question with Bot Routing APIs](common-workflows/analytics/question-with-bot-routing-api/question-api.md). Leverage bot routing to ensure user questions are directed to the most appropriate bot with no need to manually switch bots.
 
-## MicroStrategy ONE (March 2024)
+## Strategy ONE (March 2024)
 
 - Rename 'dossier' into 'dashboard'.
 - [Bot APIs](common-workflows/analytics/use-bot-api/use-bot-api.md)
@@ -79,7 +79,7 @@ Description: What's New in the REST API.
 - [Create and edit incremental refresh reports (IRR).](common-workflows/analytics/manage-reports/manage-incremental-refresh-report/manage-incremental-refresh-report.md)
 - [Create and manage cube objects](common-workflows/analytics/manage-datasets/manage-cube-objects/manage-cube-objects.md) with advanced properties.
 - [Create and manage SAP HANA tables with input parameters using the modeling schema.](common-workflows/modeling/manage-table-objects/manage-table-objects.md)
-- [Create and import migration packages](common-workflows/administration/migrations/migrations-in-workstation/migrations-in-workstation.md) just as in Workstation. This allows all packages to be managed by the MicroStrategy Storage Service so migration processes can be monitored in Workstation.
+- [Create and import migration packages](common-workflows/administration/migrations/migrations-in-workstation/migrations-in-workstation.md) just as in Workstation. This allows all packages to be managed by the Strategy Storage Service so migration processes can be monitored in Workstation.
 
 ## 2021 Update 5
 
@@ -141,14 +141,14 @@ Description: What's New in the REST API.
 - Enhancement to APIs returning data from reports and cubes to allow the modification of attribute and metric template positioning.
 - Enhancement to APIs that execute reports, cubes, and dashboards to allow the request for asynchronous executions.
 - [Monitor and manage cubes](common-workflows/administration/monitors/monitor-and-manage-cube-caches.md). This includes viewing and changing the status of a cube.
-- Additional [server](common-workflows/administration/server-management/manage-server-settings.md) and [application level settings](common-workflows/analytics/project-management/manage-project-settings.md) from MicroStrategy Developer are available in MicroStrategy Workstation.
+- Additional [server](common-workflows/administration/server-management/manage-server-settings.md) and [application level settings](common-workflows/analytics/project-management/manage-project-settings.md) from Strategy Developer are available in Strategy Workstation.
 - Ability to [request object lineage information](common-workflows/analytics/object-discovery/data-lineage-analysis-via-rest-apis.md).
 - Create, list, and delete multi-content subscriptions.
 
 ## 2020 Update 2
 
 - [Asynchronously extract data from reports, cubes. and dashboards.](common-workflows/analytics/retrieve-data-from-the-intelligence-server/asynchronous-execution-of-reports-and-cubes.md)
-- [Exclude raw or formatted values](https://community.microstrategy.com/s/article/KB484350-Data-API-Filtering-Enhancement-to-Improve-Performance-in-MicroStrategy-2020-Update-2) to reduce the volume of data transferred when using report, cube, and dashboard data APIs.
+- [Exclude raw or formatted values](https://community.microstrategy.com/s/article/KB484350-Data-API-Filtering-Enhancement-to-Improve-Performance-in-Strategy-2020-Update-2) to reduce the volume of data transferred when using report, cube, and dashboard data APIs.
 - List available schedules and schedule metadata, such as schedule type and next delivery.
 - List subscriptions and their recipients, content, and delivery information.
 - Delete subscriptions.
@@ -171,7 +171,7 @@ Description: What's New in the REST API.
 - Manage projects by loading and unloading across the nodes in a cluster.
 - New Security Role management APIs that allow you to create and assign privileges and manage memberships.
 - View and disconnect database connections.
-- The following settings are being retired beginning with MicroStrategy 2020 Update 1. While still exposed, the settings will not take effect if set below the default value for the setting. See, [Server-Side Behavior Changes for Cache Settings](https://www2.microstrategy.com/producthelp/2020/SystemAdmin/WebHelp/Lang_1033/Content/cache_settings_behavior.htm) for more information.
+- The following settings are being retired beginning with Strategy 2020 Update 1. While still exposed, the settings will not take effect if set below the default value for the setting. See, [Server-Side Behavior Changes for Cache Settings](https://www2.microstrategy.com/producthelp/2020/SystemAdmin/WebHelp/Lang_1033/Content/cache_settings_behavior.htm) for more information.
 
 | Setting Name                                   | Corresponding REST API key | Default Value |
 | ---------------------------------------------- | -------------------------- | ------------- |
@@ -183,7 +183,7 @@ Description: What's New in the REST API.
 
 - [Push Data API has been enhanced](common-workflows/analytics/manage-datasets/make-external-data-available/create-a-dataset-incrementally-with-multiple-requests/create-a-dataset-incrementally-with-multiple-requests.md).
 
-The ability to make external data available to MicroStrategy—often referred to as the Push Data API—has been enhanced. The newest version of the Push Data API supports complex scenarios where a large number of columns/metrics need to be managed at a different update/load/refresh schedule. This is accomplished by separating dataset definition, data upload, and dataset creation, using multiple requests to incrementally add data before publication.
+The ability to make external data available to Strategy—often referred to as the Push Data API—has been enhanced. The newest version of the Push Data API supports complex scenarios where a large number of columns/metrics need to be managed at a different update/load/refresh schedule. This is accomplished by separating dataset definition, data upload, and dataset creation, using multiple requests to incrementally add data before publication.
 
 Performance was significantly improved for [Data import using the Push Data API (with multiple requests)](common-workflows/analytics/filter-data/filter-data.md), and issues were addressed for stability improvements.
 
@@ -211,7 +211,7 @@ The REST API has been enhanced to support the ability to pass filters into the R
 
 - The stand-alone JSON Data API Server has been removed.
 
-The [JSON Data API](common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md) is made up of four different MicroStrategy API families. All of these families are part of the MicroStrategy REST Server, which is shipped inside the MicroStrategyLibrary.war web application.
+The [JSON Data API](common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md) is made up of four different Strategy API families. All of these families are part of the Strategy REST Server, which is shipped inside the StrategyLibrary.war web application.
 
 ## 10.10
 
@@ -221,7 +221,7 @@ The [JSON Data API](common-workflows/analytics/retrieve-data-from-the-intelligen
 
 ## 10.9
 
-- The MicroStrategy REST API has been unified and expanded to include the following [REST API families](getting-started/rest-api-families.md):
+- The Strategy REST API has been unified and expanded to include the following [REST API families](getting-started/rest-api-families.md):
   - Authentication API
   - Browsing API
   - Cubes API
@@ -237,12 +237,12 @@ The [JSON Data API](common-workflows/analytics/retrieve-data-from-the-intelligen
   - System Administration API
   - User Management API
 - The /reports endpoint accepts the `requestedObjects` parameter, allowing the caller to dynamically decide which objects to include on the template when the data is returned. Previously, only the /cubes endpoint accepted the `requestedObjects` parameter. However ,there is a difference in the implementation for reports and cubes. When `requestedObjects` is null for the /reports endpoint, the result of the original template is returned and nothing is done; for the /cubes endpoint, all attributes and metrics in the working set are added to the template and the result is run.
-- You can view and use all of the MicroStrategy REST API endpoints in the [MicroStrategy REST API Explorer](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/).
-- Quick Start Guides illustrate how to use the MicroStrategy REST API for common workflows, including [folder browsing](common-workflows/analytics/object-discovery/folder-browsing.md), [searcommon-workflows/modeling/object-discovery/search-for-objects.mdects.md), creating and modifying datasets, and [exporting a document to PDF](common-workflows/analytics/export-to-pdf.md).
-- The JSON Data API and Push Data API are part of the unified MicroStrategy REST platform. This platform is contained within the MicroStrategyLibrary war file, which can be deployed to application servers.
+- You can view and use all of the Strategy REST API endpoints in the [Strategy REST API Explorer](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/).
+- Quick Start Guides illustrate how to use the Strategy REST API for common workflows, including [folder browsing](common-workflows/analytics/object-discovery/folder-browsing.md), [searcommon-workflows/modeling/object-discovery/search-for-objects.mdects.md), creating and modifying datasets, and [exporting a document to PDF](common-workflows/analytics/export-to-pdf.md).
+- The JSON Data API and Push Data API are part of the unified Strategy REST platform. This platform is contained within the StrategyLibrary war file, which can be deployed to application servers.
 - The current packaging of the [JSON Data API](common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md) (jar deployment) has been deprecated. It will be supported until the next platform release.
-- X-MSTR-ProjectID has been added for every endpoint to provide context. The X-MSTR-AuthToken stores a reference to all of the user's sessions in memory on the MicroStrategy REST Server, abstracting project session creation and management from the end user.
-- The result format for error cases has been changed. This information is available in the [MicroStrategy REST API Explorer](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/).
+- X-MSTR-ProjectID has been added for every endpoint to provide context. The X-MSTR-AuthToken stores a reference to all of the user's sessions in memory on the Strategy REST Server, abstracting project session creation and management from the end user.
+- The result format for error cases has been changed. This information is available in the [Strategy REST API Explorer](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/).
 - The version information included in the contentType and Accept headers has been removed.
 
 ## 10.8
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 66e18286b..c4ae4c6bf 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -62,7 +62,7 @@ const config = {
     ({
       navbar: {
         logo: {
-          alt: "MicroStrategy Developer",
+          alt: "Strategy Developer",
           src: "img/dev-docs-logo.png",
           href: "https://microstrategy.github.io/",
         },
diff --git a/postman.json b/postman.json
index 4aebbc9e2..91083bd23 100644
--- a/postman.json
+++ b/postman.json
@@ -2,7 +2,7 @@
   "data": [
     {
       "id": "16131298-15ac2bcb-1b3c-4be4-81b2-c3defec602ad",
-      "name": "MicroStrategy REST API",
+      "name": "Strategy REST API",
       "folders_order": [
         "c3e9496b-0d87-4a9e-908c-2ac6072cc4ac",
         "e1477e3c-37b0-4778-8729-1dd86275ee70",
@@ -7975,7 +7975,7 @@
             },
             {
               "id": "16131298-ac58f345-f38f-4703-abf6-5cf4900b8ca9",
-              "name": "Update MicroStrategy Web configuration settings",
+              "name": "Update Strategy Web configuration settings",
               "method": "PUT",
               "collection": "16131298-15ac2bcb-1b3c-4be4-81b2-c3defec602ad",
               "folder": "16131298-c75abd47-feaf-44cb-ae44-59232bbfe566",
@@ -8208,7 +8208,7 @@
             },
             {
               "id": "16131298-e2d1b1d8-b956-49ab-ae90-d1fc4200e853",
-              "name": "Update MicroStrategy Web configuration settings",
+              "name": "Update Strategy Web configuration settings",
               "method": "PUT",
               "collection": "16131298-15ac2bcb-1b3c-4be4-81b2-c3defec602ad",
               "folder": "16131298-c75abd47-feaf-44cb-ae44-59232bbfe566",
@@ -11550,7 +11550,7 @@
     },
     {
       "id": "16131298-9ba9a108-18ee-438e-8f4f-df058f265f1b",
-      "name": "MicroStrategy REST API Workflows",
+      "name": "Strategy REST API Workflows",
       "folders_order": [
         "b999a521-d7c7-45b6-9da8-41e22b5491ec",
         "6aebd4c5-6eae-4ce4-9ecc-4c8769f68208",
diff --git a/scripts/convert_title_to_sentence_case.py b/scripts/convert_title_to_sentence_case.py
index 0d1b73ca2..08a69901b 100644
--- a/scripts/convert_title_to_sentence_case.py
+++ b/scripts/convert_title_to_sentence_case.py
@@ -6,12 +6,12 @@
 
 # reserved phrases dictionary, key: all lowercase letters, value: correct format
 reserved_phrases = {
-  'microstrategy': 'MicroStrategy',
+  'microstrategy': 'Strategy',
   '.microstrategy.': '.microstrategy.',
   'microstrategy.': 'microstrategy.',
   'microstrategy-rest-api-samples': 'microstrategy-rest-api-samples',
   './microstrategy-rest-api-explorer.md': './microstrategy-rest-api-explorer.md',
-  '#working-in-the-microstrategyrest-api-docs-repository': '#working-in-the-microstrategyrest-api-docs-repository',
+  '#working-in-the-strategyrest-api-docs-repository': '#working-in-the-strategyrest-api-docs-repository',
   'embedding sdk': 'Embedding SDK',
   'embedding sdk playground': 'Embedding SDK Playground',
   'rest api playground': 'REST API Playground',
@@ -20,7 +20,7 @@
   'samesite': 'SameSite',
   'cross-origin resource sharing': 'Cross-Origin Resource Sharing',
   'developer': 'Developer',
-  'microstrategy developer': 'MicroStrategy Developer',
+  'microstrategy developer': 'Strategy Developer',
   'json data api': 'JSON Data API',
   'push data api': 'Push Data API',
   'api explorer': 'API Explorer',
@@ -44,9 +44,9 @@
   'to the library': 'to the Library',
   'modeling service': 'Modeling service',
   'shared reports': "Shared Reports",
-  'microstrategy docs': 'MicroStrategy Docs',
+  'microstrategy docs': 'Strategy Docs',
   'github docs': 'GitHub Docs',
-  '#keep-contributing-as-you-use-microstrategy-docs': '#keep-contributing-as-you-use-microstrategy-docs',
+  '#keep-contributing-as-you-use-strategy-docs': '#keep-contributing-as-you-use-strategy-docs',
 }
 
 def is_word_in_camel_case(word):
diff --git a/sidebars.js b/sidebars.js
index 0b90fb9ab..3fc93108a 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -1066,7 +1066,7 @@ const sidebars = {
         type: "doc",
         id: "microstrategy-rest-api-samples/microstrategy-rest-api-samples",
       },
-      label: "MicroStrategy REST API samples",
+      label: "Strategy REST API samples",
       items: [
         "microstrategy-rest-api-samples/create-reports-on-the-fly",
         "microstrategy-rest-api-samples/react-user-manage-sample",
diff --git a/src/css/custom.css b/src/css/custom.css
index 41377d689..49c745f0a 100644
--- a/src/css/custom.css
+++ b/src/css/custom.css
@@ -6,7 +6,7 @@
 
 /* You can override the default Infima variables here. */
 :root {
-  --ifm-color-primary: #D9232E;
+  --ifm-color-primary: #FA660F;
   --ifm-color-primary-dark: #29784c;
   --ifm-color-primary-darker: #277148;
   --ifm-color-primary-darkest: #205d3b;
@@ -21,7 +21,7 @@
 
 /* For readability concerns, you should choose a lighter palette in dark mode. */
 [data-theme='dark'] {
-  --ifm-color-primary: #D9232E;
+  --ifm-color-primary: #FA660F;
   --ifm-color-primary-dark: #21af90;
   --ifm-color-primary-darker: #1fa588;
   --ifm-color-primary-darkest: #1a8870;
diff --git a/static/img/dev-docs-logo.png b/static/img/dev-docs-logo.png
index 4937fe0a01de6382df6ac085169c2d6905f0dba7..7de01815e8151467786bc699f24bd3ef95c2d13b 100644
GIT binary patch
literal 10610
zcmdUV1y>wRuqYw$C4}G>Ah^2)4-lM1g9gpw?y$HAcXtUc!DVrGHbBtDZSlongTo{D
zp7$f}oHIQ=Q!-uMQ#D-@@l{zC;~mL6BqSsZfSi;X5)$&lOW)(|e=qIG*O0!K3!0;x
zjtdeJA>F_86+n&l?B(Gr7d2T4r0R)}2QN1$7UD|cNJw>Y=nqDyNJva?08-)_9<Ppb
z#+^xJQ^6`)IM~M#2^%@I9Bud_7p?=WiUxr_EVZtvLDWOZ7JP}-UuFruuDI$QqUN(;
zgHVI3zg!tpch$E4IO|Jw!$9z-0s_jiT`Jz0J|bs?^id#0apJ=z9?i`)J3TM91*Kj_
z@PF}0MVCejDBiq2CCP=u3valU4iAcnI_+-nO@B>k6`c<H*9abl-gQA=<{b%%6&3T<
z{|d?c8kzKedI9eOd;TpG64FnJd0VadIFgtdlcf*2)1k0Cpp6=a^lZ4_F|)H*Kh@(=
z^_0=^{r4~=Bs}8JmPeM;q`gEy{^{<hNzij|%JS4H=|KkG>o5|O7iIy)y_SivjdmGz
zo5x_E#I*KBh`xH<F)VERR~m1cP<k-x7g5$+tQ$Y8=}(M@v&n67_wQfGv_G4mx?xX!
zfp?YzpQ5!IPZ^ugA$&*xW}F3_&-Jsq_mF3Qz`wz2e+Us>D1AoMT(9K&>CHs}t=bBG
zegCYtIlI=+wMZfbjGc!m>&axl{fCTB^UV+o%r2Hd)Kn)NPL`|o#E*iMjut3P^bblX
zBV(9X57J3mDj`-=pHN3eN}q;t{j|SH=w|3CROY72_=i=CjjJj(u(x!Lz#PXdUOv3X
zTJ6ZYTj$d?{c;Sn1d70w2uX<W)rkU{Ktd16kb{CAvb9xJdfC9!B#f#nJZX)6Yu+2S
zn<}M$%+iI?0y}r_uW!swrrs0VbZU9Uy%!L{Wc4JwLrGAMzo{p!@~O0sj~K+O#7A`h
z#k}oqhtbR4z01FUAr6pEaKtfkS}oAQ)vm#jc^|-h*5qYywe0ER^^f=OES^BJRtt|$
zk{jL_UqAwF9<CB5+sH2v?GG00)MNP$jr79FOPY~?W$UVBGsu1ObQ68qTkY#kd69mi
zV6K(~d8e{180b>owTChg)2C4APTz{p4DJ)WyjdlLC$I{XT(O89HoMxi*ZFu;Zz*9Q
zE86W3U2yYRB1f~+u6b34c|OPh<d5>J@fTeed?&tlSNQyuWiC0o<~88<WG3T@;;ghA
zL^mQ(-sGk3{`SP!W$SRx-^RH&4Q+M7?6rIx28URS{o`30@M$l;N6q<oX`HOOw86av
zR<;WCe{{<Gx1iVyZF83I<-CXV>Uh15Z^P>NPc1ef4Rg=cQ=834|9vk(N|t1L#wr})
zGRB$T_OA-NQ#H!=BG$=Nze-mHLwjX$?wK`aVHf?@*3PBvf@cSS=iVK#Ysa~5I`0_F
zKT{)Us%+PB!6M(UK_T$fpzqz&<1-vrn}phF^`q~#Z;Wj<5^H+Tn|s%s%1Y?Au!G{a
zD*tsGXx=qB4${w$x=pms(LO%YH9-Q1kgZHio4hH$@mGW+SO!3fl!?D%(81Ib8i1{|
zA;H<rjB%^)fU)=K;hdP~i{?-gg~<nC8zQk%$%Cx(%Exu|Y6i)+P2poKgd>yml_Yc{
z8MR_3oN^=Lw8J_~x~z>@T@M!}IZiJ+EQ*8cRIB79(R~QufJUHj%)(siCgxcijzhOc
zX_=Y(g%B4ga-1kN2c%$ZuXAh*#2y9TX#9;}4C!BGU^7Oktu%K|6iMa1!Cy|W<V6Wo
zlkS{5Q&VSG?T@HpohXIq+J^h`;-K^!D8?ET6AD#aW&e)?@oJsMv#(;9`nkBU9OkE-
z;~`i=|HWVOfHTMzHSO`jD@!i+6VZuFzWZ?1hCtiqJv+3aOX-%Ke$7$Nq2~Kz1>)&3
z&hbU113u(qf%`dR)~(wy>ICMJ+r-ABK9BHOr0dhaa^R^IUgx=zrAuOKmR<jG7A!Be
zx#`Zaz?;E?yQ6D!yN*up7W0<{uPq#tK#u^5e>?;!zXIt|v!nia$a}}3UTx(ePdYZ&
ztho=}8x$7p1pzz+!fIk>sZI|NjFG=J_L#M%o{Ljq^*4zCXNm^1Q8PEW>IS`Mms8t%
z%^kDb1TP<U{;|l8-qXf@iDt8o-nurGxw>AhotRe?-QA#Donx0ht2tv(Eyz=LFT$qS
zZIHKk-=iGu&vzeW*N2BU-S>$A@EG^2))q2Ju|vb^n3f-mATL>)Ju0(Z`2Jr6-2dSW
zUgJMpB!q+%{#IWq)Gs2v)!51S71ZC+v!;>PGcf#Tl1tn`hDAeF_#Z<#y$9na!sm+^
z<h%upTZ0G1w9f1;=s@Z(GD4_(S(*N}ZtK&|lBq9Yk8Fw6$&8#xIM&Gqzc1}D#)BvN
zn3|8<fkt<ZlMde<Mfq%YAZ2|Rd+bp{pfHeIHqboCi<Z!+0=wK~{9cJ|cOtco<C0Zz
zutPDR>#6{nC?}O13mpgfbj<Z+$IwX*+_by<!&DV4l4AZNrW)@f6<tI^!hX?B)qyzf
zRCb3?su9xj%Sly3ZqMDMESpJ0;aGNgt=zR6fC}g32m>QQGFH9YaK?{l@ad$vA~Hu=
z>0ofo8G-5~;>_)+sPnVAeyXjGul5jy$N2RiH9Vub20tUDT4R=gi`+*d&wR!kBzXd;
z2>5x~LnD$w(YVCA4AAzTT24D=0*PRrhvPofr6qo~eD?Up<j>!wZ`0}@#zT?v8Yw_?
z(>9SNDjWKVjFeR|7lm+Wq@cBuP!DHR$}K@%B8ne<suFebKb5ht?B9QGB(MYFn72M-
z=<rWl%Fd?7f%v~bl!p)tteCOsZlyUByTR12X)AoXL!=|YQj$=TsyPKPw!?pUM4hAv
zB8sjLLWlpIZgVMNFHh_Id^ZCBe1;IMdPb}ml)m5m%e*?pC=!XZ+y63;X?F)jg#7*K
z%P*FCf?iMvv#Ci%6HSccBI%?)-nz#3<cJ+IKzDv`YP69+H|6NfOE`0gVrQk?OyceX
z?5=kf;tytv7iO)udXzrZSvw7EA^Zg*NRN|neXUSyv?!}}WKnYL_LUT-melO84hOxO
zDx2Xsp(T?cOQ9y2PRJZm5sge*muKCs@3`t{RwC%h3AI@9e5C)*ProB}Gby9q{&dR&
zabK%7bcpMUeYi8ZM3cGtl-GSR2hUW<sh|(eouoPI-gR4yricp)W;=}0EquKB7^G?L
z>+5*EUF3$ZTO*5tW+$Y9Jb6hnJj~k~XMg!v*SkZoT$5VFAEw)0vlzL?wFum==T?kv
zYhgcrx`3z@kBP}IBzehZ4x?Z_E+EJ<K9Q)r>xTqc3hTn5gk9%6;)fgC+iD6n&v52L
zN{qD4Bt~{`srrXLzOVit$c1%e9t;kT$M3Jjn#v_)p!ymd51#!ywZM|^_0V6yF8}A|
ziTz~+9Jsn^vW6b#E!rGd<Mf|{Ij6$}3b-TSmJV93{oqMmq@4}c{v(1J8cY-?n~JY|
zq^oM$vQBX*lDWyoO072l)Ln>JFcEK2LjS^q(8#)%i>oYKma*AuRl(1bD~*iEmvCIS
zH^9Ns-B;tf`T<_fPuvEPx3IG0gr}?X$0Wt!zN;3{#fdWInCf*7%9ymfl@*Hrv3^BP
zib>*mu>HDs+}OetrL6PD;s8@6dGG>FY>!+}*~54-B}iE^Ntv#9B4wfxZy+tuzInOb
z3-QaKKx!GQa={752>EnxbQHjuM`t-~6qF@3=qcpEk3k`g=8&t5t4keTZP4z?u=eWA
z_pawT<s%u|0Eh+r6Ed9cK_MmKA19`iGecNtlj5Cx+K^9sWi=_BF)6noPgdJfU5Qzb
zLN>X3d#xTJI+M~}ZE)`{+SNTiY+D3jx??w+-7*nlazCOi^b!<Jy&RQM5~v|Mz@JiX
z^#TBEyzs=pr+U8^U$MwiWB%pzv6|?cJ^}<qYbr9Ta@N@tI}L7GkwHH1kGk7|4XHYb
zu8RqbI3SkdC<R&>=t}CqBg>#t*-%BB&WS}B3V*^u-v{QfE&!WQWyKFp>Kglx#ohV1
zBQ7$z{GoQAIgzg<o4M{yMn4CwUnR`(P-j#6QQ;m{)?DWSgb>?mrGU^EYl`!bif$%s
zg+>uIoF@Wsqv><(Ydbg#ynYWJCFfizApj0RMW(9Mqzcs}yF^*~H5I^{c6%3V3EI1?
z)fPH$@DeZy(eEunhp!7vD3WuuA;az8O1{&MPB$WOa~u2(J#A})Xi?lakB(6Ma(Jj}
z&1;qv28Xy?g*;?z&K-X`&zc{*Af)&2m)oiQ6=uVGR{J&toPbNb>;7_t60U^d#k0mB
z9-tu$yvhC>lk$(zu#8%(xkT{YeUUlt<pQ+alM=Ul$hp2yyV_+X&MQec{4l}pDskrd
z4(jb?Yk@dQZzcPg;zM47&EodSl|qtqJn91)Mpcx|oBj*PyBi)|28N~|PRMb~Cw>>g
zb;WLWKUgF5zp353<;5(UXIs9nDQ{64<Lfw{sFeQqpX%t>di=3vF|sYRQST`nGm`3p
z?F8IfPy)D_dfS#0p|R<(?hcEw6n*dWO&%0WNAQrczR6IG#l@lI_tBCbQ82rrcEQCW
zCWTx2ka|O`C!R2GBcQ3;T~p6F3vuLZ$yU`(58%&2U=E#E((i{J4R;)@Xg)91Sy9)^
zCLJNe5xCJPBZz%Qa1B~g<pOvfp6Sfo@LeIJtxJ`$OOhFYUry)rIHBw5p5$c7pvRGz
z9r|Kq=L{i;R=P}Ko@w!9Kt4U0l#>m2PC8kej^OcctcN2xcln*0qB*vl8LkL1tZxLx
z+0fC`B>2%vWEwun77X&d3ItO4oWE>S__r@lR#kv!Ez211wh9^YjHoA6ln+A+jT3&!
zGk}KXU1C~Ha><p5;Vf*aaGxngc15q3t%s{`es@)>rO@JEobc8~#g8dM@n?~O5)Cwa
zCc1B;hpF!gQu?g!y4raT7OEARX`Pi~7r;Vpb?I1e>BGLF@1_)+T}K<2Dgz07r|q$@
zbqvUSCl!>K3{M~FU8mzP?T@k`^6mic(a(2!-x^1UdeK?UP>&pVV=KKw@DfduS1g91
zSGx6!s6Yd2ltnnc9;mTN`}6{GE8`<hTM?_sS1qVN#3eS#SUzD&gh5EbOZX?rN2<^z
z!3bPOh*HkM{-cB%GKGZ05}8|F)j%gwK|`DvSO01W3~8uuWReswFw^%+5X)Dg-i<#G
z53q;kJ@ddCn5L|TCVaonCZIW608^gd02n1hFOjE@dqNGlD_isiHk`9Fu0_-K#2Dvu
z7j&OmEbDEJyi?Jl<yR^A)hO}!??IiV$lcI|3ocNO(4=dp!soN$BniU*>{Q-Rap5gH
zldWc^sPJJGH{Wz?2)6Q9T$~dSy&m1SZ18tt`xy-h=_ZwC$lp3PE!a5ITsmZ<E@qs<
z&?9Yz`E5~8vm21CV8expv2P(Ic|_MyJ^_U;K3TZc281f^3`(`hZCjVi00&6W<$TK}
zfjgRf+sBo>?ZV$XiI;veDy{1EB7W@;Lh+VgSQQy;y<MVhf*0%1S$qD2X0_X;b+6}r
zviKq-_@L-XP(zgDrs3K-WjfU!mHp?Pd7S!HKO=E)IE}$${8?YWBP!L<5bZD{&lS7z
z7m4x+%J?&ri-fd}<U(y9JJ!+$%HcFHk{!N|_|n@n*vUYr)pKqYW$Yn?i8w`y1%5#_
zejrP7uFo1xWaWZO!*_VC3-_HA-u-XZ_Gv(dL<>g4Fq0hye-Y{PRv9jhTvwa$D28m4
zCv8bylWA7t%!(I(^c!|Njt`H3SZu!kyg>c9^VUD?y@=7*`u-B%j)M~w5Ho-+U2O5b
z0&|{v*F1-+oW6<nn+OJIu}m&RmaE^~En}Iu;VG%{%PxXnsUR&}ZdP|)iS2J6Bheg=
zTielK(^ri*wo+c&YnlTO3yDXJ!;$ue9SPywR!+zEnTjJRplJjyxX>%(o{v#193B<N
zWA)-%GCH~c$e#<om$EW9CFU2o+oWYlxfr#+vB)k~dMnIIak8XX|BD3nmZa-aCUi_m
zv^rwr9csR8Xu38IU8CL~as@R~lqvCOR&9-0s>Z9%?^3hjnVIazE%I0tEM~gq#T#wU
zRILNu5_}_!fkw9WIE#MZ!W|`7JiuJL-RCpT0b^_Sfca}J-qu*{vuVleu9{(e2&eCQ
zqtbxpgGX$VE!0?v&AB+7H9BY3IO|%)Yt=15U=04*(E?T%lOBlz>?<3TiB!Y$i&8xh
z+FzOv)HZ}cN^r9IhA|=2Dq_&jXrA91mHbL$bC;kB7hNgJs5&tF%-Gz3IrD-Zaw-ng
zx<BEXssrE-jrR;~1e<KkI2d})47y?l(#@mze&um^P$%;b<z}p&U5z0qT)z<sqYTHQ
zoFYlWVl>E6Mx&Tf;VgLY`^7sZ7H~_&pCF$ar37zRUDX;MyqgDhHZFNVtwOt2zjc#C
zO?`95r}lx@{zep79rIXyX!KPJ-HV{ZG_<O5q3^d6!%bcM)HaR`UD07@!zt^K?Y2fE
zW4oA%W@6y3z#w2TnM71RX9i9UO*wB_E=L`&P@B5+%M_fqfycIltDjTFa<DK692YY0
z+|Ij{+W)TODa6j<HhP*?btzIeg3)kj`D<5;kwv4rWsmrpwm&`e$5=|3mK(u(9bXw)
z4|Fe3M!web7U3R{`7C{c#uL%UiMiJ}@bw<~Pb!ukq>K{n@R4%JnTdt3Ij$J|J?jpa
zLoC*!0c;nX%4nogfU$3M-nsRwF-x=ceT(WFj@Bv{C*$Kw0<T-hWw5eUZ$kYAVS7(i
z4c6b8zLDR@)Gl5B6IIAIRQ_OolWxZ>PWv5;AzOi|1uy<2+|>@28aEO(eX*1FY%~{J
zY+r_wnq)Imh+Vwa>#6FJ>}*$kjS;94s)j5aOB+|-edDN*)cI%1`l(=Y^1V3G7IC$^
zB};Cyus`r<CPY?}3zlfcT_E>0g#?GuW)QOyN{E)RYuy=JpsoMjiLA)~#<0#SP2Onp
zZvkk_Y>WdjeO<3iO#eX8Dm(sXHHbnDd6sET9BuSQ+*{g4M)JaJg?+lOQoXT2dte6d
z`4Hi^d6%@I8aU8CMk^Gx=yw30^;3WbzP+sU{$rK&`yd&V7Jn2udTKK0%X16L#(MO)
z@$#1=hdwX4>dhpOJ94G#8pgf-zE6lZ985{lm+kZ$*oPN}^;-U>sG4ljr$9T@Dk<i7
z1ba%sgXFJd0==YL&ayy6CPkZ=%G=_FLN2b9CbfI+H(w-rW9UPtqt8ZfgUrJV88=;y
z<Dao$F>{TZLNRh3J#>8-DFaiZZLW=ceySX#@>Vl@QE5xn3IyB}G1PW;W|^=Rsf!g!
z{pRmCvBIL?RifHYlDojGH$;T-ZkIUk<j_I9h>nWwzkESFY+82Vl@AdYWSIBFfo!Vw
zYQslLu#yCtL=j}lFy0F6y5H7$V>gE57*%_x&)G7prH@texhaP7eQlPtAv&aH7wDA>
zyNeUil~5y%<ao|tN;-+4h!kJb1kpw7#u>a|cqI9+JsubFgQ4!)x7k*u+UmMxf_#KW
z8Msn}7a-%sjlw6{TW_6GqDlz{fwUtLRod(nqHg<jXifF^PQcCw^VF7VJ?&6qyH2-b
za}K}igshQ<4usCbdPM0FVOk8(?>4UwGX?gZq${sh$J56yQ$A^NwvY);y?_BecKyh-
z9&xvK!%uiLlymluwap+B<mD+vtNz@d-xy(Zl)lApV9?3f)OO95&PI&x7LQi7z1^>#
zX*~_AH*$m7*!j9h<6(*u*67oQ9Ml`5;s7)TX-NBmsKYcOrZb$+EmMm^7koQEPbN1l
z>Q!i6NaujD-&K2;Z`=wlzjy2399`g^EmxgCx2JyU+;02i7MwbWn1)j5ExJrNRVk>)
z6OMjXGn|5D+oRCfan1;ynjGBxd0)rX5}*<l-IJ<l`5M?AW8A50bdNl}beoY%2+Ku;
zHZgwu?a!UWO~h;fP*mF)rk@V8qYdFc{)AOL7WTkmjFTYAT$<_>X!)D@PUVBQ=xx1o
z&TYH;E8)=oqf6WDV)r`JdWYS%2)R<KEV<&2b$0EKzy6%RB1#I5l4I1OM*lJG{a6J7
zLO)tSXWtED(Jn8{E8Jha=V8kLeJI$+T{exZ|81%LDlv79U$05EX)a}X4$Eg;sW2s{
z=P_TYL_;HWt9ixWvDk#i(}^_@aVMFkmAxc;h<P|_#$XhEW1+!SEk&R<YBqBt@GZt|
zK{vH4BH4O|A+`tyD#T^G#`HbSYt+`mI<GlrUTNb!l+57+&ieANZw_vZyLx1U_G_^<
z42#C<S-P^q5!IkPW)pUo_q+1B3d2WnI(D7gMGkK$DGz?+;IJIx=rx?yeo2&iXGhX+
z2*1Gd`wAXGZUT3((@82heB^E@k$3BS^5_2x_s`9?rDiNeRg84JpFM}m{Q8e@EK(ZW
zDrX$XVy5AJJ{d8;UI9^)cp_$iWqi?rBks5m|1}ly8Vrt2I+az0l>-3q2JfCXqKD<N
zVTFzFe|=-GrJJ!-E1fb@Et!+%yei)-Nu3id9EP~YUdqrTTj#vL=d<6^-B<o;f}Hie
z%lleAgxZxGw^hof+p|l`!kPTc(=X|wDd)rdxYNV;l{b1TL~Gs8<rfKcR^dV)%8N_M
zl{VLy@br_q4#$kwf={P37&&xQJlPrS`HyS5Z4t=q^cKj%MxDxAsPjh-HAl4|r*#S;
zu@;*>j)zSqJAvv{B9kQBud}>3MNtx=B~AIG{2LnG#tFXeE4(2=U+rd)!|5+UN<Ngo
zz+W*94qFJ#n9K&uq+wEg&t3g+k%D*SzavFL5W0sEL)vE+#8gFZfxn=bgF@u`qTF#m
z$L_zaNPcqP#TzcZ9gd<18~ClPV)^mv2j&{X(NJQ{_>lm@ZEEQtL7cFjd^|%TO?m0X
zf$|W#q>O-!NRZJR6MNMuwb26r+AZ$tQJ;0?2XOtK$iue;+{<VWYW>~(=Ee#WgYo!y
z&|KOCf6=D`Iw9bZlDFpLt*GA9U)z5t&sFRQWN!7%Bw%`%-?p?#DkxHd!PO%emO{Zh
zbt8Vu{*JBVhd%DKq61?0SLuATToKh{k3VVkl{gkjgr<u7&<Zsa@fWBgKUTTZha%x$
zhTa(I>34_QvOg0xx0Y_b(Kmr__T-1Im(n-)hBc6&mi0yYQu)-F=pU+kf5loF_Y}eU
zQO1&`fm1yJhA2!tzy?VvuMrsz)&3-n2P$fYVMa#}4Ch2WMRKGE;dp#hs}&N#b4@lt
z(9M1wX3ly64}U_w(-B-C(SVz*_$3mPqO`@$QlFE30m7E1v!cIt!27F`Wud4%b=p3D
zRgXZ-C@v?(s<(ZQjf0jPY9JX(aOM&y;a^(DRtCMT14uY`C0L_Mc*7%8<ATqPAuF%g
zwDr-g$F*y1uNEaf+oK)`v~>9uf6{B;SsL<Lz`Yf({AsGf=|#Q6WVN{CPY4zM)DI@n
z4xhuvT0_Scq*bz?7q5mg+TF~e+ymOv*lYx?Q$_{|TOmFL@AHae2k51j<c15(>)eNF
z%{=F7%M^1gK3^4Em-z9J0{|AcFv97gVw%O!(()fLnC>p|#(k_)*bLvC$Du%kw~7$v
zpw>ar{+{v|x=D7VAsnITaqsEX$Z%{3Ev<rzp(a0J+#!xTc5KllL0lrWKgF{J49ETB
z8g7QPq!a#e6hX395o?&b6n?AaJRGMBPx~4dv6r-##a9p>9dskeHIml!kw-_{Y$Cw)
zFKgh6p1Ag`T0RpIWbPMmRJbrj_w!VW1Z(s`^3D{kq)j#O8J6>6cfdn*X-w1%uk#rs
zI9#y+t|XPy;TALQ@G!GMc$3ZZ6X)kVYaF7Cn`^7XfEvy!GWnveZ}WFF6_;Ap=UD}a
zR+BWovlSLS4%I9hTqHclUHeY0Spxzb+`Ik?bh>ovb4zB|*XYjiim+vtUfCybJ#|#g
z<8|j>=9J=_r6qGZjFx~GS;R9;;WfQ9=x@xV-O@F}WZl*5BC2*&UgWuy5%35eV+5#X
zQ_@nc>#ekU5Uc>Psy`+Z99~LEp`k~MbR8Za)tpGBQPpvln5ag*Wur;-T~Be|b0H=-
zXm`70Lsw%-DC4<qnNe&Ht2G3BVTOAsxl<0TXR)^WJ^m85HM4j<c@|J}OaZO-MN}vf
z@8IZo3ZI*q9exo)5_Itz`<-REq*oV~!9BOc=4zu4q&TvG7k9~~N}18xoqS20JKOtN
z;q{6Li{V`qpO_EGJw-|`Ik-rYC>S~a6Y+U3M?&4$)ZzKQ1CxT1!ojz!e7+G~TLya<
z@hT|IyAxEEtz8NS-pT=`m*i5|3FimYb6hdUFx%uNXB`}|$JqjmE^=5JVx*I~H9pfu
zA-jwPcb*OGDxcFd-QDoT+t#{OA9yOJ5S8<_HXS|XPmmw`39UIVx*7zByBqJBo|@;F
zypMY2&@%-ZxZ&cBuk#QS?|kOF6k)e+h<-G5cjpvB6L4pB_>oi|BSzXMU4LX<nT;>=
zeP-MekBD3EKEPZ59$lE=z-Hdv79LV_OWD){K*HY$msX#&0Q;#3S~omFcVa%ONf{zE
zi5L{jD3iyuE$vjT-H)X?&VwqhU!&hmHwQ9ihMl9^WmHvbsyT9e`Zz6Y!7hzTc%0yk
zQ*)iVyxyP~#`a-VEk!9io4|N*!WF;CdK95jzZ;d3$u@tHsND9AZE-&=Jc6V9Auh&I
z;9-|s&nS+uc4bGJYFcHz^M09U#&<7*?46Kqpk^(vy&le;?bPaM-A}!!_7OxO&mH-@
z#{oo&qx)N7?8WpsFTF9R#PIh9SW*LK1tuMp+=tTp)UZ-vWKw!EvO0a2Hye~$y?@x8
zPIFU|7={TUzEhdfAPTqnm58C3vKY4)zZX2Z-;?g;sap~gpz@>XPXS;Hz2%gJ{P2@v
zwXyWomcHgIYO?{!wk&qkBm$AlSn}>@pqe3@&c~H0&jI6bb9eH?+NX}RI_v-Nc6DRM
zd+ER%N@SREZMJM)Oim-^#+AmlQKZrJa<L74iY-JEY1F`nsG2Lw<Pa_&9DZ$WuUPe3
z7=gEpoNU7KnM}p|flPneeDYR<u7soVu^m1k+Q~icw|yCRf;iTMTYUVV$A%=8AC&ty
zJ&z1?@R*q87kX3S-A$voIKn<Y2c`qEUqzm3-*(;xUw2O4KlM6kOkRT|aTDblqmuC2
zlF~AlKnLt8l%#mV;!OQXZ;c2|vuttvvV@?7X*Mj1t~7WUpzDXbeYo5PACpV0>&Q-%
z62VIdY<;obPn|malSx!(nVsv!glcslgvElkq4AFoF*%Rr8{1ZBjm)rH!QSxxg8p^Y
zL*q8zu-j>ANWFIbZRY91JbK8}?J~-jR~ANh)Cw@a=XRMWS{f5xG=AE<9{WcgFYw{$
z2jf0thj&H`F8ZK#u_pJXbX4kk6);I>1!_ff_!+1Ful?&0p^nkvHFjUyVxgwVefxM_
z1Jz<Ft_-~r_#5iy+rj4Vaq-@P!hq&GP*+WP&miktxRpnq6sT2x@~u^W2pL9~J)KiO
zK?s$SCg&8tSoXmo2}KLu=33s6*D&GUe3Om8X~Id7@NI63<_HC=a}cUfBt{nD9ZdoU
z)kPV~7LTuwJ_M0Z)NQ~FNdL2=(tJ^s>kJG&g<irT>nb1ACfVjZIRk6X*@4e2V{Jm8
zlqR|GTXsU|^ZE;6u)AYzLEfDOKh}?DEhfv+xl)LFLA%bc8xxvC##o|s+<$2^;)ha)
z$MXyAN3grKsYeO@jP8oap`zdT2l6foOoi}_RQ;cflGaoIveP{LG=(5`mw;XhJ3m+v
zG$4bBEbO$1*?R#e5ky__O6x;$%tVDj)vceQ5|^${C3K?Hs56!ZnWxOc;@vgVTC8xk
zyM<0#gH-ODCOpuu#`Y9fRxLSwS-%;(RI)7ASpHuhNQhV}ZXDDjK5bBoE{?UnB$xR8
z`+!p3x@pn1J|A(6igT;B`kW4?4P8>%-#W*rr3tbN%VdSw840o2Yfq>t@7jG?DuCU%
zLq4`gdTlEAvbBT;04fO{v0GzNw1QRZlk-(bZ6nS-rc!1PDO&oWDMw*8aP=bodGpPw
z3;NeiDw}mRb5fAnik|0hLR1gH<&h;0@oR$4XfWDaZc<DJ;IG1Z(H_t8MszO4d=Y0n
z<ERxdY=*D<%wDgx?~K=3<yk2sA#$p&HAaNQuc)L3Sz!!H(~PVmt1xCOEe5GQujC=_
z^RgS>{~qt?B1yihnU89@;>%d5OGYTuJ~LmuLg9B*TnR|?K9PGPo`?0r((J^WB4+6G
zmfPj;v$ccsN9yC-gN}OVP^Jz#gGMqRHe<3~7m(i{FAtA{>4Qzy`t^_#YX7BghgZs$
z<GJZ};C>1~-CBt}w$p*fsF@$#Wg<1se47_yeM!H7O}=fwG+c;_gO2(?ATTXjRZRV;
zbL2WrQzYW+j*#W$vQ^eK$XlN*SPS&%<@<Q0qj@YoHhS5i$G~vnHW4oKu&_eU>;Ab!
z_;1<wm%@PEhRyhvB-!=t_PlJ0v>>mk`xU06c&<?|Re6KACN!LdTfGRCw5R46j2$(}
z2euzXV(tRg&l0PeO=}QD_(BS6%!A{t<eht07e!GaO-_Zh?nd;gVhbK+>NMb&PH_Y9
zycM;9+K(eTbyTEoAI#0MeK&~B6|H27?{E8b>X?#;b}2!hEjVE)3FnPNRigD8;Fv$1
zgZEEVl(t|>PBU>l1Q#e!|7@u??Pc9NRO5AyjV&Zy;X+?J+y5A`GVv)@56wmv%^e?c
z^>|Ow41)(RQbGA>L%chlEDS`Yp&g0{WG(c!wzbpm$v=G$NzxdCu^_x2Jspm`q@6ON
z;zy_;<Z75mNU5lJffzl~y;MkA$vrv!U-Z#q#iNbBC29AGa2ug+@xFe^xf*g+;vn(R
zj}TT|<sQ7mlvW4CcyR|pg~?96DNN@Z&N}Hqb=*Gx>S%rn8TS6iQ_5EhSu6AH<mWOP
zp5I|88b@`C8M1&i;=@;OiZox)kOBm14S!_NBoNZxhDtv;0v4QlQcp`Oqp{%rm<|4s
z`=Wxy!s30H?b_QW4A5RLjDIA|FV$Es;&qI3Zlh5hJyqMuW!(faA*NGG;`CpX+yr1S
z{Qm!s81*(CJy4~I<g|nfkN)jek5`pZ=f6s>FQ6}mKU%po)J-2*WL35_;`Cn4+x#1k
z1_laWI;r@)3~-gM9>T4am|Ikmx9^Ps=lus|{!etluzL1+N%+Wrd4X28yIy|SUY4?Y
zM;oRUgdjme+6{wG!#2MTt0lG@Aa4W(DaIO7g(EzaW@4=hKA0pQ&f>4;B_|4xEqO?l
z2po!{@crYe7|`<{dhxSCp|q}8#!}{Z-;$H1`!R<|Vfympn-~$3YwWu3V$Y60{^26M
ze?eC0eJL87xh^kG?y{o-d$U#onWgXPGbm(x{#R}t<Uown*neNFYyv;+lHvJ7*o}kk
z%%r?}^RAjjBB>lsLb^j{wf}*%L)QN={lDGxJiqEXyZW2u_jTu=AOLA)scH$sp#KNI
C3nP^P

literal 21682
zcmYJaV{|1<&@LL=nTgGbZQHh!iEVpg+qP}(*tYHL*v@&sgL{8;SG8C5(_LMwS5<_f
zyaXZ~4jc#w2%?mvs4@r$=>2~@FAUUwc@6|;{(l72Sy@6Dq;>}H{J(;zsiu^foE!-C
ze>@BbXqY7k#Q${pFX8-`KtRCrK|#R(qoDs&mk;*;T0!sg!T%o*!uvlR2aI7kKtKdR
zq(p^OJwUH|pwsmvJZ}Y@XF5!~TI<xS=(SppLQP30)k<+4{=^0~G%%5qK}ag(2A_^&
zQttm8PYRIvz<S=3`vk=Bq@#d=;?@g|q#pm<G8s>8xv08&dUl%0xZyB=(cj+gIlh!`
z><5r;^VweTu-Iq0?<5?!5+tLHSZtO65m#kllsJ~TzXgw6caE$cDpAUX^Wg%iA$9~&
z>h*tYx6L%wJ11SXt67;5QJ&LEP_BW!+shd0#EKz;zroaCx>1R4JIRhvtk-E)AX!L;
zuEJruWW4ZHuv4QIu778FrNBG@`jh{9U&PFfFSGyu!~BSEJ4ufeEkqt|5L>7^`c<jP
z-$lY~6ZC2D=i}MH=3@%4?=-9CiNVg1*xGHOhqnB_-0WLS)nHWr&&qY~F!`o_UyyQB
z#xiZ+K~5=7dhX_ZjCCr?%`zGgdLjf#|MK<$s+)uzGLd{4tAr4hbd~={uu2q<BEdaZ
z@&uZOnCHigL%N!Re8tI<U!W>DDzV8qp^CO+7cD4vCDQE_y&_2@ikl4V-i&7$U5ues
zq0|un-~RZu{3m$g7$r}gW{s|Q2h}nL)v+1zFf;LzsSB)dC#Km()wjsnNShXGoa8DZ
z71j1e!6S0XT1rlYM$iA1;eUj=r2!3GO%dH;H9-*7QImue1#kYCmOPS^+$$39G?0KH
z{4Je1;lf|@OLRvSmr;+<9pO!c2lum1`>y?gX5P4WAVn2eixg3AJdBgr5+OM!8M2rm
z=*_&{Q&oxh_WOFpYPsq^MEBT21(k$jU#Z15OP<E-H~-*kvC3C?@x&%gm|Uq&4%JpD
zJ3e~%#PTh9+Q}7l6pK-B{=sy=ZgUw3H~FXDYHZ?7`yzKrDcVJ2A^_IP90Fv0s1%2D
zol3pu5*Y&>a-59+JEr!R{M<{DQMl8Lyva&3Tc>CUej{?5oS?4Cr~w7UL;E36ZJ>0+
zVh)zPDRtR!6>?#`VWYbKpPll`YIwDh{U(+BkTiJ~$LQZuYaX*0{Hfx_yNCkWxU<Q4
zsgw?F8%othwf~^+!-WFF*`I;0yjlotxAfPAJ#5N9bbTO6_AT%$ML6sa{oeOaEacFm
zzEB)ZovEkVp-=flQ+C#=@DSU@z0V_Fo@FQS{&f4oA25=w;Vc_>u$plRX_@+UAZuB*
zdm<C+fm~kxA%Ih)5JS~K|Lf}d)%U#8J>g85>=|5o3^QRaFU0JUed~77RgMk4@g*?v
ziC#PJVp0nQ%WhZQpsX>*POv8p{{wTrw<_6X7V6|GnzGYeU9o#r)`0NKBN&KOGQ=V-
z%&$Y}?Gp^DZCYs-SoQvYZ_?C%5LtRt)6h*aYXpc4HWht%Bo@N!+&PQ6CsDo2j3Uz%
zfffTGMF|f&>-WOtTay~TeMwkLOo=E&gi^aij<kZfx5ZKjNOrL0qbyW&G)5^#8jWPg
zS%oYQF_lt1M5&f#c)UZJpO-5vL?7+yYLoIns&07Xx`Ep+Nh(!-a-8cl_-Xvgb{t)h
zI7Z0>76MjU6NWe6m-!{`fMuGB6^Bi_<c;tZGLnlWhhj@$QA7M|t;(WDx8-cyh^wx0
zRuL|JO-7E)c^NxReyDg*rS;k9-9m%Dfk8kLvAXU`a<h^bOxcPCP|<jtiYoz;j5(#*
z5^!H7{=cuK1|pakY{x!DLgv3Kl&-#i5!K2veXWyXUK0!9Y2Ne?L6+e-s$13(ip@w5
zD!;l55XjC`|8WRIT-XezpbjRepadl|vYHJ%L@7_2taN)&vvJ`yPX&-J;Y{cX*Wle_
z4Q76|Ba|1(%bCe`Z{;s{sMXmwf#`e-p~qOfoM0r#WgkN<DetFiz^(S+84s$*B`l1a
zLj@8bI0yNO2{1tw5Bt)QhWeQv=EuV(g`iQ=A#d7M$66@BG_YmcIO>Qny?l1OC41#6
zkIM?0kS;w~-unlYUvOxxS8EpOnrE=8YEZ5H0+?fl*#<ApuBNYW-b~U*{VuKA(fFSu
zZH*jQD7plLn+a0~Q9zP_*$+6rxWc(ohGns1UtNi?wK>ncaS)5pi7Ee3OiG?HgRzAv
zHlQE%+*MpAxr!Lyf>!P-v@a7EJZy-i`$D-_FPTD_ozC3LlK$?p{v#n37G-#)D|ob=
zd@PARz^~|k6k+b<sa6LcEcjwJ67E{TdYnhBlSieyT)ZzsNXu9>aE4ZZN2M3hh8+v1
z8S52Mry%PJ)rnwfK!xwBV|3~CQpyO0P?2lY^X<jdNNKO4L_b~k-X>{m?Azz)AH)Pe
z41JpR+Zgnb<_^s4HL5y^8WK37lw*_spXcJ!Nf4yw<kOJTX3D9%#c`K<N|$~@5o4)w
z1r~Cbb>7zfbO%$P)Y`989bzd1<&HhvX`cJnNS=2b#Ok4Ri`TXHmo6qNi8|3OM0dYj
ze2@S~iELLZ52R2!WAXxY>00ueh|E}TaQJ8ls}6-mqpe&OX_b)>O8P~Ijf^PN&zM7u
zf2dn8tWakH0>(&63d6iu(>=aXMjOx~G(&%6VZ53=<$nB0gH0$THd62vvB;9i>LAs)
zJ=(G)L){>-z1AqQs8r2PXi7tUS@M5tZ)y=kf;;5{ZuAIBkcOohl@s4ORe=SInpPv~
zHoiSGVARO0iDDi%o#X*l5@w9jGr1%sLP70Y$QoV%$n1oXy}?jJP+&zd8kK34)T-J?
zcokwr{E`?U_Kk=xuV|$o8Ud((45TgThlZ(4wI6M8K&WT;)qP26(MrM9+7Nr7JfH|v
z>(zs5%6)}ThEOtMFxL9HOWr}zUuB|PWUz4g5&-U-oj4E^`AxL!XAChVnyz6XuBm;$
z`<E7nEDId*6wz2_kC1&i{eO@VF$7roPK)+r!7-rPrMjMpL2qSGPR9~MjTzl+>6&1`
zn^Dc?iUggC)4U-Vg$gOkurHZsiP<~^|8Y2Kl<LyuqlF^f*4dTA3sRf^p#opAqKhri
zRWR2xUrRJoO&`$|`6*KPcUA>hkrDR#hL#(G7Il{snd`xz39=@_x=AMl9_^etjxtzg
zUI>vU`4u=m&XaOWu+qxB_09f_kzM?PXBb_#d>u&`n=kJuZTQ#9kTHFddW}hRq20=x
zn{uLfuDQ(czd@OV3G@u+JsIjmjPH}m^vS@Y)(d#=Jlkk8g_seq<j2)GiwcF60xxX!
zyYiS@Cmk8)m2sAU$W@z|nMe>dsAutkY%Dy6Fe&89-KKK6YJ8fz<%qmnEbQlH*moFB
zjg2?09?rjdncr}+B+9)I%zZsaH8xxM^b!_Vxb$^cRtC`NNqQc!1fHCxqsZCA2m=Vq
zc*gHkRTPUi0+S4`LX5FTR7YZB=(yf>m*;GW!K-oF-~tW6V5U@Zs;ZYGqc<FxU4wXw
z9M!7uh<TFxvQ}mHdU#iwT0&dSj}4b0Yh6#A#`T!$&<c6tTY@?`LNq38fGpsMUou0^
z^EPvr?!lf*jM2t_|7xh}F6W?Bg(Vdm@KP#iuHl{mM$mvkp+3;j=@bXwt?bi%VXy2c
zZAuyDllKnF`^yr%Suh)68xk7|cx+W<;?bIe3`F^naqFpE|5i>A=U1;XENt`X7ln<V
zVv{@{x**QZklksMYsMEO>|sL7An+>ds!(22g8O(Q@Ql;Uj`#9IrnRCFiNJko!%Nab
zgIr>?ofbAbT|%9tS_8ihm8SpD!Vu3^!N-c}uAVgt@8^fh`<H-3-uZ=M`GBN!VXjH1
zWhzeei*L){kNkSstpgTXM%eYb8z2Ru3XzHy+K|+_T`wxTERvCyzYj4Py=Ymbl!Jp_
z&r2$Lhfb0XqFeTO-K}dljESsH!f)6Kg$E_`jHtnvyl1=ikk$LDcW0cjSeoq#=6F}s
zL4N5Tmkd8drg?y<ILOqH)y4cph6<p(&`np^=L>11Af6#Q(E$z9_b1PY14%KY660Bq
zNCaDBWUhDYTT`;<GA0d#F>33h%PI*UnpU!mq||v26))k`ZGQ~34Ve?z4a7Sv2;dX{
z=acs;uS-Gll#Pv^)zOHc@W(wdH#8@9fo3HG*v?gLOAlKmN~3e&cJ7z0)|>Il9l4ti
zdIp7GC6A4i(b?(u{SOWM5?Nf2^w4&;$fnMYn~8%L1KB4(db-&<(i&MQ1M`is&%EbN
z%v#v(+{g7x`Xog`{U9{h2@@L67DLEdR8+R9BzGF-Hh4jq&ZZF?OO6Yj#PoEeF;+qS
zv-Jcr0!=IL2pGQ+V%Z-8Iq4mOt&F@^bSGYP?QbA7JDaR|P>YFNELHcB;AV5!whbh-
z^Uy<7gUJpEpfG6?W<P$;kJW`N<Xbmv6y9d(u(|&vA8q5~?m>*Hk+w6z6>0iCbnR`3
zSrr}(gO%E|;?n3j`9A*8#uhQYgl42u1-CdB9rQ@A#!k9yGHcpI0UGMdbUPi){rpOt
z$qS!xa-Xj4H*R&`N0Z@Lz?w)?u-EQ~xXd*n$69ra>Ru5^VZ&A)9Tm4Bbf`$r;ESVE
ztXJI_RJk1=%Mkpxk(8c^sX<}*B0qyi<?nK<BANH2j|?QY?z%7im7SB?Mk#7s`0GlU
z=+LHHT2-a{vUos}jL7!UauA#kzIW@|1tqZ1u5~-#IjjCQ$w})-8Z$^hLtf09!CSv1
z(YMfFLy8XaI0N0fcFlsK3DfAyzrin8%_0N(fPg9aBgKRIwg!iT#WV|>QWe+2LAGT@
zaRkazhcL9UZaxzS%4A7x#Fz>d&?JvH<Gr@1gK>B-;ibTe6gKgT{R90oD?9oT*Y_+V
z>iO#O>^pbKbv477=cBXOlopv{v8s4EoIEGxb^YCTx5uh0%*K5A)?Bf9EmDS~Z>E(&
z<+%fO@XR8KF?B*x49`_HBkdYjh6Av`{T;A#QybyS2&g`!^=|>K%F@hfHxqxt29Izl
zgtrf^%FzFY?f69{Q#n{U&b%CHZAJPaF=!<PkA!NiQh4Jx{W$|4$%JuJ&9msXi0gno
zM+|;WU<rQ$S&g1!o6eWy@es8>!G))ub|nv0ZRF_T?KgSWjWF3g#~8tGW4En|-cDka
zZeNuk2P86;X-Lr<(3BhwiDY$y&a-y1auc1dax4GNyNYww+sPbn$M28-$TDr@e^a1l
zb4-O3s0wZU7LCklG8F5X9=fMtaKQWEm4$79y~oTn^5SZ~3)t}5UQLXPqji-nn^(#p
zFzqqT!<UVV^5roT#q@tuGw%5&W{itBwu=?PyqY>Z!i{@x3Gq=kvS=QhtkHs~w-89G
zZb|l227T7ATH$FjBdXKp2y4ozuFZ|WO|UjMy=Ed$))bxWD-$tOzuuu?#}_G_$&(}C
zdYG<Z?)Q6&?v`BhsAP$zP#xf#V9VN%10Q>^NJp$m6va!jG?je*GYPw>ZhTiO6DJ{d
z5_V|jG%+zjC#0bdF>psNC2d(Y<#5#-LyMYF-!<K+yxtawJu5V2Zx-i9Y5iq%ku4a@
z7ms9?H`}7(t!|8~snQpohsjutICoLfI(4ul(OQUK(N7Hm?_Z?fzZkTi5U&Qug<UB1
zg?=zm4ug-bmxe$t+rZ$)+uo&TQ>531Avu_ZNRz53(?Of&F{9%omewm>6T=kRcO@_>
z%LN`6o|3VP^1@STtH+#R+sGot6j-$bVfQ-ox4OD43aqyIWkQq}$8xuooqo~2q-^tW
zCP*^oFCF8|i~HNZvR-ES9o@xqKX!Wh6=4A#QcMf2y81rGV?|&87k`S>m$va}O;rEK
z*Ak=D7)~Goav&(H=ElkZwx7vI(Qd)g=Unbtr-zy%);mZ5o!tmulAkr%-?V+|Xg2b?
zhO53P{K^v0$!zXl_C051Nr>xTGKYbTJoNlmWxm|8!2B$<So|B-BF0}f=Z`*u5TB)C
zT)|YPABL*mMy%YaiSfph86Mr!kyawhBHV=2-QjsptKuRTHndtC6na-h#9iz}raXrQ
zJFbQpEikbb$k}&dhZNYx*z(xfE(l$_%{kwit1E}+(N9r=?0m&~6dILzqcAVUxQDfG
z^oFen;y2R^Evrp*q2w4hhGf&6CfGbRr9nEBpiMQ|u1QyEK9j@Rt1#TJ&5ZO_s`A%7
zuhP~?ES-G1zK|o&Fg(VW5hqime}$(=j)be5()Bg=iZ6U#ad)G!o$raolcjm*<Dg~Q
zaPbY+*e(MS8dh<nitH-Qfrg9Cy9frZ)#6@X{~4vkVS+6Smr2^Bvq6Zv8{xJ<C#w?8
zv1Q3uJU_n}hkLE*9wV?Ig)KXmSI;3N;R^`QY?-aBlM#leso*b2FFETXi_gGVaE#O<
zTilD9aBm7HV26zf0QT?&{`Kg*sRxTo6_K5|Q~u-}@rlDHv17quRIp}rz^-&Pr61l1
z#E{k`4zpo^Fx;-Yb>$s!W!5E2xh=NMALM58n>?h9im_x50owA&hz14D55Cr4=c6=p
z!{%>|DK?GGVmpS?jqOq;q$RFKOS0@=Jr%}kjm{U1RXq*g&UbEWdmaJ;070!Dm?v9n
zT;-kXEBEZ%Bq595a!a5GJPxi&U4+_F1a{bft?`Ph&=SelCUc{ES86M?ncu8Ji@jD{
z$YzERl{PV0*W%#>lDjFpAQr#e*KBbiQ)OM7>NH`KepTc*DCHzwu@Fh3(bBY++-`4i
zWmB?^hRYI5l1wZgw&Xa=`c-|3*C)kInqZ`L_g1qIzBOUnjO3T#3YyGJT^ww>AQd|!
zz5U;5L$;S{omr4<=xt=i)_1i~A92otSz##oHBcIuq$eu9?!5TT!3c;;v6uH%g@FuC
z3z76VE0*6Im&@{zWTEBQo8!@F$MI-7)(4vsnU{hXUmc!o#*chENMO;(M$z56F4l&b
zW+Uiqb18dePhgqG`vwBC8~dH{dWYI4*A=BT3>?o_OAa*JdUSUZxP@{HOtZ|%pPbQ`
za8Tb~SSRQA-BHjYp$I_jg-sR(-G+>k5aL0!4@67$O4_S??D8>AB}$8Nt6IPa?4fh8
zd^Vg3-&QI^M0a#WX{PpMiamK*%#cpTkLE?FBnUNp-*x}114&i(akQ^PCL`T;OY0(q
zqJbr5D(`uxy2x)Z0*Di0G1Yn*>|h$!dx3R9g2~q$$_>&|oQ`G562b!y8grUt$Qy$l
zSzQ-Y1kYk`;~3KIZY$sUjNcSCyQ-LtIJMB{pBON9d{3(z;61588W4eC=y|gYbv``t
z*Wi-Wx+BrVg+>;{^0YSMP2C_zOl_m&67qpAp4R4w`a5|H>hC3WW%PCN^oTv-{wUQ&
zNa-uXm**@^w@*RY(wEBElAq$xVFup6JL?t)<X3p{x=NG+<dtO^vD)9+aT@>pYh1JZ
z65XOfTQ)rO@i*LbF+9Gk@jUNAfHh%dt649cc9W^x%|tYM5;Ap{N*uxBYkpnC8u%WV
zB{7(fakW|&P7GN>rZ_#~H4kO=7VV*~v(PbCHIn=+V-fsX$T6`JDJGS`1A<LP`_KUY
zNGB%V#T|GVbf^&-6r_6G!tYaTqYzGOOv~TvUu<yE?ufPg=Qv5Zs@<%<A;iizNPiBu
zYe{dz82-U*17P%OVTV>n@N>euPO(Eh=3S0SX>q@5xVwELUmoh^TwFb3#yByZ-wzBn
z2d@61(r`iFn=&dG33kd_`skM|YcP$5*I&ke=-x?BVJ5TY3g+E@h(32g3&6x`Qd`lg
z{CY)<cC!ykP_JSVSQ7>|w+%*u5|M$>O!+@|rNf&eZ1#}h!Nqa4>X>g{d-3GE4OVI0
z4&aX4C=4T1q3$rEq>GI$o2~T3%J7|~{>spShmK4}Bnqw-wUrUEeR;0WK)p&IrZ?Ja
zVzJ#{pO!BmN^e}RmxH-l#*)eTj4+)q!OUYLk2y{S0tne2rBRwGNLZNrE*B>G=2?R|
zhZ74@l`vKm>x)v<PP_$m&EtQ~>Xt-sQtwXJ8nJ~(d()kJ8OF0N2DUcoUPbzoMqpgB
zI<;zkT?c{;AgmEaxwM#%#?%TW<X}laFO0eO!q98P*UIw^UGkcy;~7VSainxp@0dQ0
z4h;_yZ7OZT_M*X>j>0X6B*_mn$CM&*WBZL+&yi>!s~IuvjV<R?*@!4~qf(f$fh{t7
z{c^p&48ST`_2W}>{QE|Z38#}i%RIJe>5O}Wopn6u0_4Q)TT~sl{o{&utdjj)2dDN_
zt}3t7J*X)*%#VOKQ*b52X55MuupquID;Mo}L8{IIxU6t_7g7Ic{ZS?rz!m;`+7jj(
zEjhbFt}fl3Mb(^=*1<wZ9q8zloIgl``#g)A_5h~VmR2*<X)?!@eni_+B~sexzCO^*
zr`2l`iB4FaJYtG+l~2z>7;RGuz2Ju$9Yw(KI|Bu+&?X+Qsv1C<SOLpX%n4Gt5^b{X
zyg&A9SDz_c7V9_kRK?wfqvspO_x-ldr7@wkLh;qU?)0sK*ISSK)}7|{+mp{Ux)W3r
zo`A_RL=fCT)oR`+RB0<_q@4Y5v1`KpR%>)Zf`_ii?^x{~%_UvOqf(YfGuw;`9#VZa
zl(xVp3ps~}P^FG)45u6v>`Vd=77#AXp-(#j7(?PW1|oWE-%cNx(q|C^GGa+_<1cO!
zeW?!(lw%ykCKZfkzU<@}qPCRQM*aR)Lwhnh0uJkzHi4cMKz)7$A%1793(!THOffzc
z2TF-h)Vh5aacxs;a5pUP6Wn!>oqAADzM0-aSdtqX_N^o-B*m-pueFqNXvMwN1|z)I
zsWgbZaUUdEcL)1<xoz`{6I8=Z%epTAqK50Z@IDXEmlVHeh%s#9Fa&RSM9;pBqn;<<
z197prSHoR<I2zAb6|6DL6nvt$=wuiApU9%4L8f3J82$ubP)*g1Il{rS29w)oT4j;)
zG!ccn&QpzoCi5}phg>>zQ|VoIa}z9cKLQwu9+k&4b74x$$LCtUEGgACTRB^;VdXoT
zwq(+tdvZzm4=?xe2nYKTc7!%fpemstnnI|}VLTA)l<`L8b+EjB_2(Vej$iu0d>S9w
z8iox?H<qOQ(&%l!)w}mDrqaZqBF-NYfQhg)efG~fjm5u3HH|R&ctemkl?@SBO3XPM
z((_n_$!x9EgvWlO(LeooA=WaK>!)WeW+l{A$<|uUYIqMywC!T1why$55>-uBkqnG_
zPS9853_;yqV8pzK;9DE&>~X4}w8V;u?l%CO?SQ(_g5tylq9=sW0`Byon&wiPZ3O{W
zOPz>(VmS%HOHuI!sTrwe?|zyVU;uCIhM@NTy>>r$itoAZNRv^jsS3nH^RFx)C8>&0
z!qhHib_Nrv1O2mL(M<Y^gtd&UvMU!wD?|A}+LI&te4NDms>wBHGVU2Qs0@ZMl~R1$
za#-jy;|!oiExchEd0T3!$Q)<0@>%pf=!`*v(yyTge)}hTBT-@SwGtN+@ZSfC{DJNg
z>!DfX+eyd4j@GgDCjMux7#2AxnOv0Cz>Q`GlQy3Rr~3!+H_BD#LM__#5BU!4s2&2t
z3}`4vJ3)}AM{%qFDLev!gxIhs>w9dNmDgXwKC6aJ$1An!**{o28epR=3{#VaGw>Hk
z=(5{zgRDA>!ye*nH-O3MNP+h`L=FM6!4-*{kN4FN_#*Wi{}v)e#<71EO$Sv7rthNJ
z)%%i6)p%{lJ-@*9YyYgcg!{nE0x<=z4y*Nu&sm})A-*uS?Sf_Sq833pflcGi&w{jx
zGbXmH4!X9I&o&9O0DWR1w$k8tvaM^ci#Cg+{VGQPgo#7KOK?r-QD!}vPWa}5XAJ<R
zbthUSYH>Z2O;+CiW4qFOaNgWzpFDMZ+e+z4e2u=ju3RWS7UdVbI@B&x^qxwsi)WbV
z^M<k$-O*jI%N|jh6aq|RcK<i!<G6OA23}i<v$t(8BXSFs5KLD9Q0dfaT34w?u{PDg
zjdbcRsQ3-JcvfnG*614m8K5VXo%l?HQx4HH|7kS}WtN5W!}G41$Io|zfYlBE7J5?4
zyVZjy{YkZH^srcuzsM)9Los}|P~F7Z6m(a<sh1G1kXAJHp1;`Xxh<1a>Hc8C`nNlU
zyvVtnPezG_F2|ts1!|4>&t!S?avL2vA*n!|(g_^l*P$ry!%ChcM@as)Ltn62G4StN
z>ePdY7Rg7(s^qP*>^#M{wXvF7UwTDbgz9q!(Efex<GSmim2&b_<?DSCE)YG@-8?(T
z+>8`oUvNuCBa3T<xjs@vg7t4)TI@M?t(#!+W__jUbeqW>Ct1H@6cMp?l&nD_;nQBb
zjQv%s$%v@{(KC~!Rl2N~PBz8CqH~i?;p!`C$}-El3)<a33^3$YOju{qi`zfGNw-yX
zv|~jFbW_4G=cOT_p8UWAbEBd5>|Bcg&hAn)tKmp=A$v<>rIa9_BPc^PAmucJE#4W@
z&)wA7Rb!uesZV|{6w`!9h|v8nc4CG4KVR^M^<f>wSG+W{Mq8g~{vqiwOW4@PY^^ZB
zGxwM<{b|3^5joMjD}@{hqWnf=UR5PuJs4~W6KhJeh|Iy<MT(Bl7Sd07RkKDm0`ff6
zWIc($6FKC+!Bx}*K5rGb&tktj=k>syj?RU+8hiSRYwMv*uS?!P?00-eCqAw_jEA+%
zt1CFbM%EG5dnrOz1s;EIy5-#X9H8e}P$kJcEiy1c+z0zG+d?SX))uPBIL(J#5#`n(
z80%(SV4*AFe*8j2SVCbrL>pAZ6rP%_z|+D|=^A%OehQdeO>Ig6ze`gJQ%f<%h!Y}~
zSqqN3ad3r2heqnei4+X*ZLvx+o*cx&asssNSbJZ9->$yn^c3xD!@T~OY|;9rpuQL4
zi1o~-g*w8zZE<qnkHRoi=4((Uv=s|yvD(e)DbwdCr2fQX^#9B=wm&4K7UXnoLb=-r
zu(w}66ki@|pfMb=xQd~NVbjHMWymB0cm9>07roinEg;6Yln*NLR8a^DupfSyck|T8
zAIR~nVNWczvelhc^#6GTXB0Vom#)Kx+I;&6u<l*s{w`jT%w2H+*0gPS>3!~W_1>jf
zNY@oIdNA<asJio}d|?WNBuOaJpnVSgXOzfmWaPasm4O}Qlm$gqFr2si1dH__n*8S@
zPzTIT1ISU1RU}(+O=Kw!pYv>MXGw94yG5iqpcS?iC&PG+>$o-EuQ1n`Qe)2x6?$S1
zp>QMzkuf$=wTjkK>Q~XD@S{68f}R;i$ZSt&g<;NW^ZfG+XWQ~s?PfU2j6}?@itxfP
zE75p85RN?cp4bI*grL0&RpF0~M%j-bw|e2-sQuc;EMK3%uuT`bLXqeeCB!$3nz1MC
zu!z$A&O69=kRIAG^V<kOCH+$xv7-RwAv!+$YL}Kv2qQQ%!l_1ll9w>7(8vyqg%~CK
z2EUqj#VyEHV2)+I)BP*?BE4fBv7@2(BrBW}W0V?6q&+Ox4BEXosiEC;M5FkOb>2i9
zeQ2QO)XX@^F0Hnc5%BW6k`KYTRycJL>wLr+-w5G`eDcYuX>iA5)~efyjfljx`7mfn
z?*o2rla7WW)2=H#>Dh6x-p`I_-Q3}Mt<UPkYBIT31h@0gu830#bJ6bYZyN&W<Fguv
z@Zk#MClZ%mmpikqvOTu7fBpB0@?*ZX&kaW|i|zP6sh>f?hLrYv$0jm=^jI(mt5j!I
zzP<omcK(lp99y6M7Kelv-GS?_gx^P$KYKfMey$dFS{z$WlU^KEhaES*=PBTm{GSO~
zMTDJqC)?3q5~*&je)}>8?}?)*XD+L|xAOu-ZMctoUyCo(-q)W200sn<{L%`KdrI0O
zkNObQ@6R6h?eC-kPI#&&M!k{`T>I{0yztc<X7k<O5oMia&xEqRXCqmR?@0={Z2i6T
zE8jo?r^(~!8viBF#nPTtz)xnJ|7n-Nt8?zo%K{Db?AvV&2W4&VeyIUt*-iV)HP1D*
zMp#H|RlSY)!CVG#wfpCI2mD8%@cN_trxIxYd3JNcg_=q;Piy(_#Qt^>WTYUR$s^9X
zShew>IXVI@)S!Q0t0|n}cM7?ZC&V%xMv4bL>5noh{4NVZrY5C5y-!=dceP4?p*C6_
zr<U^@8tU(CZUn;KAosZXeQTc1j=Vz*=Pu%{ye9Q`T7DkN_&LT~9TyPY<bWW!+VU+2
zVC@h}FJx`pJmbt0RA!fB&fA~uI~bsQT%QfEbT8sUs?#LN+k^@-IPlmF<vZPSJ?`Mo
zDYn_SQM|y;ki26$1qBW)p(!t~%vYX{B5e7O6bC}l9hU0{SG_kv@Ez}sPm8OaR;RB8
znPITQY1A@9oUu#n3{6?4jahx`w4BDJCyx3Ce7;A>$0(8EX5c=l2Vihb3Lwe_zwQ<K
zPZZzWuBY$*yr}r5EQZ_ur$41<Zs!ymGmeSk@wp7LABO&9Dtge*zNB`kH$G7V1W4lm
zi9kF^zhTf<Dwr#_KHay5X*}LOEYeupb=Pc^9!I8jk17-L^ywW<;vGomyktPcklj=P
ztAj;w+4bRWc_N9v0_x{?r-+CKA06Kn=w?B3U37Kvd*j1rdW{Eq;_dupHF9{kacZNt
z=*F3I*hwV=czWV8h}f2WW3sKs_|uCxGxsd%!nPq(LSIsoM~H>v{XT*#5DL2O5?}g(
zaKo@9u+#k$ipvk6c%gI8i6q|zrSG!f&gCpCV1HG;&H~UkPYpC5UlV)f_1oUEOdTp*
zw1W7D_6)3sw1)$4%1z8>!|dA6J3BlD%{f=ROXZXShXUWgUjKg!ulA*zW3fmDeE5-V
zEV0+0b1{Tp3vGa>nnD?oC`%2a^`$pvtcs7mQ-48E>rx<t)qU_5%pnwn!79SV#8&&N
zbgPuixKh$}l%O!O2Xe(UWFJ_rtwgywb1hf}7P_|NT~cbO>vZ+$TZBF>lHBuB_%I;F
zi-Q*7VW-pPei!E>@73>Ne>ATO`195j^A+dk?qK*BB^$jPl{Eri%ZeGQ3NKy6(A-EN
zbes#O<BxfYxBD;1C*V(JJS{8lz{cV3<;|>5!S`z{!!qLK=P9?0UnYJ9vd|^c+Y|yO
z(CK#%ufF$X#SQ%At8pspwTbjg;<w3%pZ;&GVo99?fm>B~n(%k{|GZ|r3$WrQe0iC$
zJ}d_N4hhq-P;O4Ey9EkrpeM;`9%8Ny4O*6lG>lNl+y#A*=VrYoQ3eUAuzovcJci^w
zqSkz@BYi%FI{fDj^Th+u=D1zcK(jlVECqhDxL(pk>+bVU>b`-F-hbPQ2q>4U5{YnW
z5>HppuJLVwM?DW0^F3`!nss5hjhc)7dD^QnBCVl*nU#9DarTeidB_jcD@nuzK*!ox
zs-A+V@J_uUSu!548v0yUaXpU}>4`85J$X3=k?Qw_{k)u2q3&`iDIG(_R;k+hQGr-{
zAzddZu>ANi9WH?v>CeNS`f?q=YvsB)_W1M~pRsRUz^~Hf^8t!>JWqQOS^SVs(fU~J
z$G3q%L=K<7B{VsN3%wh+sLhv5952qk@qQ2K<nMOq*66zv73DV_he*LVHK`d$?Pom{
z?gkFNHxb@XeHwuKly1iMbY_JkwfF0HTzdeh*^xmw)1Zk|j7+ZrkDu(|<FiC&g|;UE
zx#H{ZmoBS?ZJe?OXbkI>Pja&Y3PVy{lt{tP=MJ*njKJ(xcBY#rPi8IMln(HLSGZP_
zbSzWriqD!ne4LV413Rt7CLuO@{tX&yOxsGER#+i3b<4bLNvQP>PiPv3<5Gd7O!iYR
zs<z*GSBayB?2paCc}JKhmU+^H!jK7Vo%}>fGeKJEV9+2#Grs?&;r3FxnFGeJfL?V(
zi;p1t_0o1?Q(Qt!swYf4=C8Jl=1&QLanc?G3Z@vSPEoOsnbn^s#p_^-dyPVSbGX$s
zWZ@9NAp-|3CK(R|!n~xHdAt2>$4K#4oa=et$61|wq1>A>E4RNy#4aT9jraoZ1<Nkl
ze0d9%R+O{4Susmo5krE-dkbrN{>Z-k{6Wm91MaA?>5|pnK6L-gjCKV6<1i-eXvf49
zg}+?o5uM--N0R!xHZjX8iSGgIRPQhN%LQ5~U(&0!IOlN5ofn~x@Uh~WJp#BFI#i&a
zq3=`qlnI6SZLXw2?Z1WvZMNNh_GKl!Lga~CG=!<6_0N?L`A-}%2v0Mt)g*a}ho*#r
zxo@pyM&oP{^M#)YOi&6si>YvEQ>S{*17hS1;3usNK|q3d(IEq&M5H#B-3%pKS`gvH
zf#Q91k<c6a=?U-r7N)nS`j<fxwCk&AgS5<+{_EB$|0qWPC3v&>`6KR|qKwKQcKL+=
zA)xD~TN^5xL+G*j<R4W5`_-oZErstaPa@Xt(u=->80b94-^{(qD(AewpPr77;nWNn
zgA1=oy0$ZLH$e7BZHr-PxsHU6-_?H;d6Xe&nJYUgJd~B_F7X*G16Mm<o$E3Kpr>Qi
z_Z%QYgLS~g_jGsg$A^t$f3#v7=5ORpy8;*xx?jO$EbZHhTgH>wUSwsCUTzw)6(vcz
zdMKUV^=ie*YbB9v*5hGE5sIWRP*vfy(KPYQ$KUY;3E&`dRR0)Sict4_Uve<i48XWh
zB(@MO7hXi8$!UICyDVA`+x29BJaKVZ{zXa@Q^C|mFdpO-rn~HvSSQ`xWbZVtk3gTn
zDeR&cSjY`Fx{u0d70H)_S|?yg+y-+s5}Mmpj2bx`mFx$?wKax{+8%DF)o4<Bu{ix*
zU3zvjCNf!i<eu0=(0Bqn^23C=g?)c;l-`vRuo@wqwbl4T^poKd5a4`StQ52zN{M(R
zpx&*7BI$f_8=Y^&eM=i^6+HJwKuCa2HpGZtidkynUJiJ+m|lDMLKI;@;6UKx-vZP&
z%p$_3{~iux0E|*^gPO=Xuf-RXuL`i(&Pz-ey3Rixw)Ex$&oc3RjQ1gPN%^#%4Xg6)
zv!LrxXlJ;Z$>YI{f!qImQff&Z9oMOs31DOr^VMDj)1X%kwW24Yh{f^X*;lTXeI0=H
z_#9V?k{n)mLcW%Yu=kDI*5dR-1>{sv?wkT<dzAlB!dJTO7;h?-B2ytlamNONB5CRR
zOy_ZyTiWH;tvt}up-f5EZp}xWEk{Q*InAafxBd6VeOv2KdfZ&K^-k&jbZxo!JyvY_
z3gWyRT?dY)aO}KxjBGu8e}(NLl(SX4gtIM$etW;GhbK|7q)9YbQy0bmEz8iAg9%D)
zzsvRhR@iBkz9||--;$67#(++zcX$8nc}E_X>|$4b`?~ME4f8JguId@=LgNW!MJc?q
z=<oQSRc<|0*kB%h95SN#JI?aC^SZojw_WuBYwHj^M0vQmc2Hcl<hkXX6a7%7QpN5a
zH!FkUt4Pzkflp(@DD*KK6bTo8x#JsDlw7c&qQ22cWYEEI8WveFWPfL<qh}_Z27ce)
z{a{0L8mX)hV%!zV#_`|o>nNhdBGSG0=n8=dz_)#)bdHQ}Al>+6obuwCXxiI85k7_=
zrG-*lv^>ALGKsD*ZfS+rt6u*?$eIr14s9nfiOecOG(QmWQE|XECtF4Me3V=qGe%xP
zzUnSB+G}9QpZQ)wh9>+8k6tG<vDtzy>*`Vkl<Wi%={B<rR<}89Wb#i>`sWv*m!9M0
z@B?wrC)nwR=YdB>8EU;kb-3R!!QTFZcca&7VQquDxq@d-AJ3}P6lL|eqBMuz)yy4p
zK~nB8%eMOOi@&v3wXCrNm$dCLl_fCkgGUi~c-Nsoi`*tFiVS}D+C^IzR|k%W{xK`<
zafW>Syc@oZSBFL#x<f!~F*BMMK(Y3s5MWr8_7BK!Wo|3O?W7c-d{k;HXx5or8Rkd`
zGdN)oBP2AIJ>+{A{aGPgV?vY0k(_iw5mt4K6&$MzII{<hTTY}fDD$+PXGe(TJ__&L
zw0;L-R5xU$?NWJw0>%%q8Yd576>mSB*IDddwtQbWn&sxI4XF<2|NUovytr?>Zn6}6
ziU|a9fVF1&m|x>^5;GJmzU+$B<YF?*mrm(^57#>Q-AwkB@e8yc#`2ud5nEdOd0i*y
z@`?|JynS$Sm}k#(S$|*5zHC3m5XJ-Y6}XiBD6%KqY&CmN0J?yVsy6k2qByhmp<~%n
zAIcMw<W6Be7HaFbR>&rKUJJZdJZlLGU}KKkz7VPY4Dj1?a7fjvxQB8sTkTMaG$>%7
zp)a3B@kl$q*WPm3V20e-)ron@zL~ulP+S<+@|ZI!^0l31jn4d<`l6+QCpb&Ql6}<P
z7a&3h6pOh$Ep{HXO=wti$eB@0JB8-m!)W+t*_lczv|65U1uf<BcfraS-PDG@{5zW@
zikI3oA;)os6_}+ld=X7p_1c<OdFFOi$chY}bHQPFq565AAi7xck<Pi1wPY&hMDqrh
zL35?~>?~xe3n{D__$4~t?ktd>oHwOCGGD)T+>)|*NVla^8z8e1mh*~;t$HEgpl7a7
z0U_BRYPrJB70c3eqE3BM{c`p;EKPOAzY}}GV719k<GN%woV6<95E|6dGTWLMk#nHR
zM42ELCSu#CCBygamg6w=$C{ipHX&LpL7WTFO^|91`d~m-aqJd5gJ0ZfQHFu78E3S^
z9-vTL6y<9P9&Qjs-8BdYy^~o1^!}xy2t#j`cPyYEBhy(Uq|uW#s&2q`K<k#iPFi~`
zb@WCS&Goy1gL2Bj0s0|KWpv^uvu}5wdQZvIL+Xu8MtnE+rI&Ys<XxZ6C&gZ49v7)?
zqBo5?&fQ}6;?sKuu}|9fG~)D}X9>GtiwB}HHp}k)u(P|^D%`uD-Jk105B=uji4Q60
zJ~*5CI_K?LPrh?%U<&T~Tmj3|X%$o_?L6zRKik8J-2-53A-G#pIvvgRD~99gep)AT
z&h+FUr`GNG{skrexb(j;ikqX7pNQzm<$#FM{6k~A;x4uYJjM@{Le{?vcwb<}aM(s5
z(Vd_#j3cFPAChrXZk(uQL$LouLXW{!22r-#-|<Wm^S%S%(2rars$2LIE!tlNMHlR1
zYX+=RNI7GU%c~hCBQG`LE5k6Auv62rVQCA^YI+xGOSH8YoH&bWhLpm*#gR>$R`UbU
zmnO+EvDHsfRUfkagHiSIMi2=pPH<3`{tH5>o{hO_%*c5SKScN8r17L`?$lZ?Z=$ef
z@Nv_HK-%}EUirmX)?CY<;s`FKQ+*=25Vfbwku7-*l*dhwB_er(WWID`?5+_7pj}AH
zYWi4f2JO)KlbxCsjx25d^Ff6}WTh|#OZf)vibxuBkrx9i#Iyn*<I}i*{(Y7da8+Jq
zgmOWGuj80loPD<A!eM@&3u&}H_PV^Tj+8rTjJh9?*X|(P-<)GRS|~WnXTSpT<Pti8
z+;BIw(pXg@iv*;il%A<YyOP7MeXXFuOC`XtUy`zIF|Uw6;|eSO6YKe;<bN<Xhcf!)
z7f+XmTd1dlWMw{o2Blu#?2M5)png&oDt6p=XVT|87vVT@l^t)I5w}grke}&ElgH{u
ziya`5e<Z<wn`2b{9(enpuE-Bid8A7pWJvpw@)d!Zh%t0<)K`WK%>;b`Ta`Z<=EXV!
zoKB3s8lW@DP1XNtx`sslE&-S;0(9!IZ+3TAZL1zV-|_87vn~b%G68wt-i@XhCv2wx
zx*u9o|8KwR7&8+y97uxm+>efX79DAGW}+<KAQzm?W3_S8Bl(r;Aev$A*-^5I7E$Ta
z*xbI<g-tf`4fg1j%$lHbxn^sz-C(?fS#<&?UH4Z@dBMNs;pP0d)H5Uy!CRQ}3l)rD
zsrV?0ND#Lf6sxh8<-pp9=^;f11f3yIieHFshhmGYoFAG{LbR8Z?CeY+?EiLq!7~jQ
ziOWdvfF~n#Oa{j>+^ey!`q9tAv7mSc)T(<0s|dTn`aU7J^)?uPM<35eXe;cB>gb^|
zK9Y3h``}@UqK#)6hU{7__ar4U1xBDBXaD=+GS>sPht%i?h2TvU(4ToTK<ihr1z@6Z
zMo33DQw}LECC5|?y6;&}X*ePKErfThpiQeX=V~6gD5u&&Zk8+b5f)Ku<!U(6q~O@$
zt_@=`{00eX6N}IO3Il1_jWpG!<7<Mr5=w=n`gEFv$Lggyr|~~jw9ZTBIoGDPmFBU*
zR@c$a6FYSNRFQ`wyc--?a>KK<syk2j9|k*wE$Zo8M3g_^vZX1=LPlY|V-@?L@JB#T
z@D5v8A1N)(ea{SNU7f>$^oPJ2kU9mR-yCKa)QS_w|M|^FrHk&kD+!XFW~6gmZd`hb
zdY^iiDcj9bQ{vkbG~i!4l!IFy55DLI;?qXy;c}|ast%9M;@rezI?J(jdv2yNqH%0B
znEr?WZ~^U0BA+=gOb0SJz6?C7bo8E7yBa^6H_55#3bNaNybx|oU<vS~QFi!1w{ZI`
zL^w2>=8joD<JSwwcMuqrGTZ~7nvCbohAq8W0zJ?>yn8jaXLNN#3(R54^At3?oJ>7g
zRuR^wi2{yk-9AJ}^rtlqVys}h!(iuVl#A%x<l4Hxqi|!K9{R?9t6ofWKBEu$Bjr2J
z8>QjH+2l^O3qdf)rE659Thgt)v&rra!dvvaIF=h(dLt0aIxGC1%#=U+5({UX5hvLM
zL7FPOSp4B6)w6^c)FO4GPMM;J$!v`F5_0>tOX$djQpKC6U450=N0h(%6HEuVcoEd4
zCALaXu@vsgPbxV{4TA{5P;oVsdIrUcs+vFK(KJ3qA>qVWZIk91nd4tRC-3b?nH5Up
zOj-}s%+Mn{)KoKwNbtI4J}Vz52j5-R#xGIdMq^L(l{<UWDM0b#AsrXw{71ZA?Yh{(
zrWpPPfsjguu&`A}p4VWhBJ=u=vEc%HJ8wcchOK46^%*BHf+emA<vOI&Vbt2>?hg5M
zE8r&;7yA>Bi|)pqJOMG3SY#t&EMqzDHTw<nLQyU2Jtcg|g1#_GuQM5X*~F!>Z`|RY
zQoFr<A%LAI#rjXAT;7lx^XNdmC|o@hYBbf0+>)Zt9=;o*SZ+Q{g1O%YmF?wOR`0~N
zS28$>@rXL`#IQj=<cvNA2Irnob8}Y?@+;;<x{n8P7a#kB#VRQa69zS~%XwXSwnz2x
zAmcQx;TpjIGJW$q%;<&WN;m%y*y0G{=tfTmRBl?jc>k*S!;<E|pVAS?l-X(Vo};bx
zT63FwuW`a1)=9wdd2&hsrNIN9iKL7_vzrU1d2&zf_C&!SGxT?vh59}Qro0;8Nw&Fs
zlkc}jTsUVqQy2Cx@?QzVk>;XZBT<rdZ*1^<V`bGiHGgCVAZHF%B2W8t;^9)x#0hbz
zvCEF2+dWse6$oBEUWO7AncxK!70QF%r~X{ah_QtGz&cce$L>_vX6vW#lNr%nWN++g
zGjO)vu{wl~-OVcG|NR_1Q_W*x5b|k6T+0PBxC$3)HzB!!^1E`#*~nUH%rIyRg?E6I
zdZlpg<U5Qm>ZwKGMXiE0@~ytez%vq<hQJFjh-v7}2_o;q4YqjJ)Ekj*C9Z7L8C0Mj
z5|TFF{mKVQRh2BZONCg5I%eCblo(I{2%B4sYk3b_pIE~S@cnc<vIw}{aTJ@r2_be$
zZ93Ae_i0OE-n`y0%xP$&;k!&lvka`XrB5I!g<%y2)wQCug#!G$j8?n3cHGuaL?=_D
zgg{mszTbd~tMJs{#oqjmEA0-NC}W32AK*(qD^7`Zsf-XkOi<`@K;OeUpB*?IP)g2p
zyoH%NGw6Wx$cIbL*Zn`4RfD{<Q7k-Sca#hGWr+%9F;hGBxDrqAlc@an32}NLP;a`m
z?0dn`Hyx+e68EznjFa0eOm**Ar@p7T@O9dz-#on!JdBqQK~&%`cPoP`(HYhm1@_Ag
zeK6p-E45p-H}K%b2gQ@LQw;92K9i@DSpEXJ$0u|~+b)atz(d#FRGFaEm;J4;Eo*;&
zfo*Oc3y+04wvM)`xS)=Y#pPPv@0~u08VSmPEngC_Z5kpliJ{b?rz;mT@ASBRUzir{
z9Nq`JcbSY{ZAzpv69Ve!!=Xm60W#1^0bzM4)?$`?@`His&#l9LSk*arjaaW4bI;%R
zPkTis>_byED6ai^Kz!h_whk}+XAznHufJLj1$Fvh>Xf2+`x9wMgz#5#B?xpKD<HGk
zLyD~wvg)Z4%YTx@<75~(?HUQHOlqz(Iqu8~r+W7qe;sx*rHol)o{a9x1wqP`IN&u3
z3hT2rg#d=gX|<!2R>$f|`$MRl{|mGD*;l}wpF`le?AjrFHc>HhPG-}+s#S}tiVS2A
zBX+hQjJ|cUG-DXlyrzEST~!XNlB!lqC-)yZ7hheGBA8%3Zt&9S2I~sj@I(#n{wp^r
z5l}I0sLsPop&d0t-jfZv>zZ!B@H%FUG<nMTL1PQq6G?h@?#BKc^D>^mXPRndR>r5N
zkhkZMjJ)fyNN7aRki^_=s%R+CUohOOrdhg^H`Sc6!yUPKWHQoWOW(gTVr#SbKJ#jF
zc}n=bRCaH5tjq7d`=y4IpAdIpo__hH>oi&WG6*sibo!q*&~V#l!(#<V^HDtUq(`hs
z(muKCT0Xnv)2pw@`9#z$4iF*zwGshMm52(f@VFp^>#bMdv*~*Nndl)sEU0Zg33Hk)
ztJ3TE<Xh%W4byhgmf8oPfLaft&XH73-cUMWC#)#hlFklE;NA_!cq^Yv;d%-l9~{?7
zCi`SNWxqav<DVCC5>7*7<`8=Gj8ci58YC}HN}Pl?(wgl{AK@L`v)X(78p(B@Eo6$)
zsOE|KnHK%xn^+36y$hTN^;rPrNJ7#Xmz^rRO1uG+Xhj~)nvsH@>SSo-111p_E&~?7
z(IiZ0i$S*2;h+RY{kFbN8~M2RO;$Up1KxMthxL~BC4{ivTIe{t%wju+FSd8rR>=EN
z$hfYq;$xIcY{oAe$LQht(3*$CCPsMh3GWd5?x*{0h>Ta;ErRhn&=`yWCv~;4cE+5>
z&+IXDAzC|SUhm=u3AxW7nr>Wi#|?36)y&SZmaT9xLpLm^AedUzHNJQ9=(JgQW;8*;
zUQ@2%{+dZry=y%D33is}Z+?vFE3$$L>qBMFq%_{u9oY%|3!Tmy<ABzX2l&ji;t=~X
zk8N=SA#_KVuOiK60b1ybZ?*8jGJTQLA`02O-R|$utX)X6C3U_k<MC*-MtKO|=t@?*
z_LtVp*c=b4;GI05FGRvGm6OF@;LFtPOSFQR!BE|6TYeyl#fu!adpbEu%fJVL%(s0l
z;rvSo=$02UyO_o=0L!pXOXs&=<peFQ%<it+rY$KWga2@Ph~^?j0e@8Q>x1Ut4{F?r
z%m;FJS{h5GyN^B0TVS2<mGvRF-F*JiY5jpfTsDE(X2?+cOVHy>2ju~d0qvuJf9FOD
z%`BE>S8@#@+Ecyz-am%q@lFe{r&AxcwOl?gxrCr!yauCv)i&XzO5MTWz@abi=c!Cl
zT4ylyxbTle3)hl2tv|4ugHFzP2I~U~K1(vmcGStg6`Jfm5s)cW87WEL0E@rFV5OS+
z)pv961$nj;D#(DYGj1!#gc6n974NzCaP*8Kh-4!&2x~Wgm!AN#yuJ?9S?OpV)XuV1
z=!_?;hQ20pZX<uFYr2;PQ;lN{U0bB*I1-BJIYAu6ZKCK#OhxMO*^f|}`4Jkq_1Uf7
z;#^AlEPOzPCZe$!#T)y*7Am<<l%YLucMSwvG8(37H=4><N3IH2VKqmRy8YpVy%9=V
zg*SVg7-8>H(;k^YyRac}Iiy#G+7zs1h`_oObGGcwE`2=;B@c9AIJqSxKhdUMX}+}`
zNLE|`xlqVI?+1(q)cd*TL)t{B;-Zg_k^GhaD=8G#>m>jH6c9;7K~#XaOKTBX!#cu%
z=p~9Te3Y*l!V1{sr;cIl84->?kYzz#oX_VZZ|KXF5U$H0xY{@REFuoxe-<X}!h7$!
z{lQ|z+<W)!|Cc_|Zl^t%>b$`JxI1?LiThh}M4a#c9W*;<N%Xn=V5Yy#_Y>MxDGuFz
z_w7&QzR$g$iZbWssh>BjU;8hxGGESpqyCrEBVXY6SNw8B9I`BLzVGgDJe-SH>`EN1
zy}ClD1*W(1%M)?t!Gn$UAsDyW;dHf2mtvUlR5MeyflB%IHbNsJAg?^K%vE=0pbkM?
zw3miTh#<zSem0m1r*54y@!B~V9R$HCT?<-!)JI-vHEKl(K3Ct|6(pPqj2+vJla5E2
zX^+vtQOd4V|6KC9SL)727>CU{rzvR9aSi=X?}SzO2`Fm^bsmRXM#W0aPfb9x%wcX?
zWlYAWCd(qZfao9^aR7DDRK`O=S#xL0_>%*A7sMocf7ss0_Ll|OJwP8^yr!KvI0V&q
zJ&0&QYG>Vlj&z37BaLOpfF9#@$98Z+7Uyp}a*qeA1wczjB@Z+as2`@)ehWwqAr4wY
z>Hab8Xt@DAs~zVsEh`5-PC&+KQCE*1Y?s%@tFU>gu^OMnSnx>*?Q`S=k;4w-R0U51
z=Xnx5i2u5uh_H2Uc=B<!tnSjxzf(8*=m6)3?m|2GG(%3GT;~rKG=_iFQy-@+4nb~?
za`iR$^il$h#iYFd{<8htQfq4_?Fe{J!^3aAKt&>k0r3ym&GF)DvE7&L0r{WiAV(nH
zyJ*YTImYw~&M3d&n|It%l6fMYy6>(#{sfzmOCeB?Q@OkV$G4PzhiSrJeDHnmeSd!c
z_?#Btd}WN@{7LRL+L&+V?u%VdMVZC&MSX7LPW5+9Q@jU){v73;U@k}iT%O`whYw=Z
zSGImSZ&L)%=kk4i1!D)_?b7&%55Di3_ZB+2(eZUSUG36&TQzmHt3g`&WEcJHFQAG>
zYS9yYULcnv*uFlF6|Pn{mXoF?4O{&*8p+HX-~&Se)wq=P45jjeW?n%>UZ7djhC_q}
zv}HO0e=VF&2k&gnBpz%Ene5IIzsAd@`OiLY7z{3lHY7o=PGJ}OOzt}x$PcHu(R-(w
z!jBoD@P2q7j8;@D6K0+fhwn^hA~HGI5~vRmz{p1$7xP*hn^EMc4Z!F)lH}gB>;8q~
zn#Vei|4ciU@g{~A$K9-0%?2-ha-Oe1ue*+eWSlX*wJ@Csqe<;!xd+(zB62zn<)v*E
zI@Ti+z6hD?25&b-`Z1PNE`fsRHGMRyl>^P<G)3_gMDs9{JPPglB&nv?=qe?L$u;BY
zBdfYwQ9sBfkghJ0_<|JmOn_CUY7ad;OoIGmk-ZP3_ltFVJG(po1V7+^4ID0FJg=@)
z6`$V^p`Ly|ZoB`>O~(5=;xA&$FnfkHL~6c~HIqNhgtc^|)=;s!N_jI@HU1dGG0o?>
zzW@ll4K9@1$^kpgW3+FeQp~AXQ=4ICI;pOoY`yHDfBi5;FWIT7AGAa^POmdpD(Dn`
z$A`GTapbeiyQd}SOCg5FO9v0GGi}*$#`@K}dG@pv_ucc2vN?V8o;%)CHbRk)3oTQt
z&&j4@AKi23oj)Yr52<^wxA*8-u(iQpP#&I1U!*4UU#(x?Gf4Vh(>~NECSse|1{%HR
z_S^UCnBTm+JS^^BAS~~_^LEWJlx>%lwX&-j_iR5~NO1N3!aTApOj%b~cQh7HXtR(6
z?>UG?FB8oUAT8F4)JUxxdZJeB<bHN=ggz@nO@c_UT%Y}|?341=<;zAX_i^LMc8sJp
zr_=4`7hO~C;CR%H%-wgfr|B%xX{MxNZ4k$i3XKtLiDz+p<;q>`H|?icO>H_h)*8I0
z#&Gwz($L=d-T}qBggjx+${*fPST3;EZgB_UmY-k~z;|(KI_ad{DO_)Cf;Z`A>&P~Y
z0@;twaea$t7D(#(wS5_@HV$ktp36%0N^0PEZ?9OFg%ahtTO-WgE@7;JHrEu^v%<a0
z7N29bvh!mTiAay_<%~DLQnCAV_8MEqC)1(hE#gsMguHR2=2)~LIw@;|zYhudB*kn1
zmf9kHUZDM&xkw`sKL^2is!m#Wr$zQc=F{8x0seVO=DpBFpCyOMx}k}Q$yIGjt+b-A
zCAOaa0;(HrkUEQq=Td4P`l3H{DArZ~SL{)I6Ao6eE_biyyJi$xbMY!&nYSEdh~`eo
zXW1+HQ#3DoXzzj4=<!26I76YX`M%EQ6>XUu7yDAR%Nsr;ZI?r7)VXL!w!q*p22NlC
zoi}jis9G((iyb(H`9&Zce96u_n}Nf6#;7l*4Uzd}V16)Pevun>-F0T-vE$eC=|U>3
zcc_#Fv+iHrHUy&`(sb_G9|=b<6y+uUBE|mFzJhpZZAVE7{&ZCQbd^cInhAOSWa|9o
zFMnCnuV)sM$Ej==J{eIgqb7$d8S+~hEJQfcamJc)PNKav&B+cYJr+*b1B_^VROmg#
zbAl&n!wEOlOyCD+-h{S=KCo-q1l+&~>3!D=Vx*Y|=D+_mO!{%8LI}7;a;7z^J`O<a
zO|QE==p>ya+65RLwm`962rWby#Da%SjVK@t(^Hz)Y)}E)5l0hmRK@BjgfKP9(Ne6}
zMv1K3;mb${gqO%FGlfLti->rKE{q}BuDcpn^~wHpCbJYZFVchCK^+?aq~4#bnJMZ^
zovHjZvOx)nk5S%Jf0;oY-A|t$MaBEP2!);+?P`fE-+6y>vh%VSgl8Gw+b~#Z1aWo(
z-zL4)54EKB8Ne9AcYwC>10b|r??=<6fK&COw@#?ljL>W}ED{4p<?agw0#7T$+}&{G
z=ZB~Rp>O(9@Ru6ui8et_^O(JYX!%>ZBbqT~#0k~p<1@M`&dq@Qan4X#DyQQ5c;1QB
zM00X_Jmj-4c_YOGX%*e<#+$@b=&Ub?c!fdaS}^3CVupY>Uhs6Ffr4vP+M^kbeSCjz
z)J*QK&05P%sofjnpapoAENJEf+e0umm7|!V;48l#zXd@KO<^Cl&p<z;(k?VFJ&|y_
z%`k|A;-y&27J<h_5Vx@wm%(Xz6#}Y)dJYhe|C%S^i%!l5{?N}nvfG3Q#ywW>hS<xY
zEKivMYhP{OPs`d7NC+P35<|`Jc&2uAYCZ7Ka|VxMvWcrVhJmMMl;e!O2#nrd99caR
zaIB{h%j*GL7<D<zYXwwa*R4b_Tt};!$4h+H^Te2Xa-b2d&<4iOnY^gjHy-@hQ9?ud
zQenAo^UTsksWPhXs}ML95Rj?mm#lT9u_SBTMJ0%0h16KifNO=KH3uI%TI@R$z)W^s
zz8RH$81EzV)aynHx02GFXdK)5a*6ats`;`W*UYwOgVJ}sOyy|Ak4R<CE3;TR`W=e!
zDXarVn~pqngh}Y(q`7g&)@|!Cl6Gq_liduNT92es#~~a|#Mcu$3W1t}5$XeDA57Q*
zePY>uotF~ZtZ19P23fv?!<w{ux?<qaCMOV>e5o!Ij!4#uD<&usVUM^j*xhxk8@2cf
z%eGNd8lCKkT*6*s50>Cwy2g#5D>+KtC$fh7oSSm?H&0x{iCiAXT_jh~G>1}*xBPUO
zG}9}?rg1(-Ks{Ky_V8sj=$n(b*t+3@bPY5v7>t41$3gT*z`R4875TDZn-3cyF;REq
z(TeI!CAQW?y5w81Gzdffd`VbvVp%p+KP*1`_PCtc+7fTO_yPm#+O%b{G*&ri=OmD*
z!TSCue^NR2{1`}Z!Q?YToo*!c7M%9JiBW(%U)2IRpM<<%#p&+N$j}2VM(3#PyWd+n
zN^+VUwr(rZ66iqc=jS^6O`R<hz;h}%xMS~B(`8HCaB7)hT3TZE6=d3&5=L;MX=Hn^
zuLMMjoUyIV$R?JFlyxrJGA;GuJ3uahYYW2(>P2@n{4nR7+YWU<;0%VJY!EF8h_mnI
zG4O`hcK&ed{h{Bl2~VvYIn&6hS~H7BF4G*5hBa6d<OpSsfz@%9SQm;e?f489_wOc$
zxB6`ptn~-7(tV}%=#zVkrBN+g8Y4Bv#|_8ZYrUpeoFeb^0Wf#di}yDT?0m4u_v))(
zK?r>KrdzII-R^t2s-Jbn+5i%@FJUW}=5$`IkQqEa8p{p`vUmmc88}ZflQin)Nz%FG
zOfF|ElX*Gfrj2IA!`%DaHEY&7=}=oqAdtXS6AefhN5`j{3}2G0&b!_SdW3k&P5DCn
zI!%V{JF)Q6?2-~hT*u*XgArlZPQ*oM2;x<f5z-20Fxd$rhGbpG!ULGH)0y#1I%P!b
zv?Mpf5NvlEMz<cDXwD3A$e6!6A>7tYYRy9F?J&Ad<-$gBfA;X;s==n_)(OK5_Zqen
zM7FV9+%^TFtoY1RU_d9H!KoK@&pMHK+r&PQ?(`uerSjH9e*gHo;nwD+NWu*svMh#=
zv_m1=2qn#I08N4sba1B1elL8XvOFTP7Mclcz%#LsO12IjU|U#o$$p<*E=w+ntvj{9
z4pgY~#?b7zGf&!cY;+eyd`F%ktCeBYfbo7et8sqipbv^phb)gFtQ@;YjQj7;)`(3*
z@s9cj9Xq`v%LzCf5y~M^IFI3n-Y4ENI))VZ7PL3_dl`gl8S7)iQz_;OuGcHpGs-y6
z1Y2z=H!P$T6;tZqR8zdHv|CuyM#j7dwfO9Z>68r((W$*hQ>m4*elRZ8V__6AP;e{j
zu<4C}T#gQjP3?>)212q?JgjYK^8GNKOX<I8ltS_3#AhJk9T8#P)?m0tW#3K?X8C@q
zDY5Mp;nZMt5;a9&#1>0n*n4|DuY0OzYYT@5tbj4S0mgMDH7Q-li7#0+1u&V${+5Q&
z(G#yv+>JNCttle2XP9p0M&9Oqj-QB8<W6g!3^B;?|0Z8gN@ZIl_v))E1WH1{(#JFM
zRsZ~lsmf7X$Db@}3|BejbPTPo<SxDNldS!gP!Ml)U%|utTiM$?T^A_A{I8|ofRVu}
zJCnFt@GX^;&dvXq>2eRJ#00-ZoCRL4ByBNIdo(<JjDli0^%r|N?;UM$1?RBO`>?<l
za%8*ST`_Nm#R9YO9eo=1oH0G@sjkbYyKl|ssg2Bd(7y!-DYk2ZY||Ty(%$$jQ0`*M
zNgrE!8epk4SE+cqi&cm><0Et>Ea1WMjQ!$p`<9VN+8Apb+3qm~-k8u8W>Mi*)J&0v
zZEbcYeFi7SoyUImHO#g~{kd{bz)HSiy6&Xd*q#)7=BKdGDdPV2JeJ$nGL38I$0+(H
z&Mt|UI7+Vfc-ztmG5loFNY$6WdJsS}$T=e7ySbWg+_=#f$C!(My06TQYN$e>3V|vF
zUONbAUlyUD_z+U{pQ0LHPffHW|0slcH#R0eL{0xxp_=|yi1;UZwuV}=#@o^9|2k>j
zjVil^G(Pc}dPUgoKi13m-Nihu=_RB@=L5H3U-DZRl5i-Czg-B__a$onm+_JK54*$*
z3u5}Ido@%cuxJSQ9QcdQznZWLfhq*55GV-&Z52Mg<8XIC1@1u-Kc9%xejwOZ#^N{o
z$<b!veGLQ36oi!nYB0>5wjOU}T^|1c+7Q({{KwzYm5>L>^C|q~f3`8QlLM1xtN)eQ
z9Ef)Zf1PcCAH*o|8g>`>@~=VMXR-2oIyDgaqjs?eV?0W!hAISJB?$Ol7k`!NQ!S<n
zfhq*vKoE%T9$yj`VF<FVi84m2kU$;qAHZFhN9}nM4{5k`R-y%BnZT$NPjVdeBvl>P
znFQ0xO8zBtzF|x*_mJY{{gJcT7PfQN8a@$B(LBKs#a(B^R4miRoBlHQOceK_DCn&c
z@sd4I{csu~P$lH25xCW?s}QI{pgaVONbCZ(&TV9i$8v~x(cLBxSdFLH_R027ZjjWW
z%9<|wB(u|1&|4s<0*3wf>^wPip_qLRwvIBfW^=vB1Xlzd^-)yy?bFFB{?*lSvZj5z
zDV5%>qAOMnRS3MQ5U3LJR~6jV!m1FcLLdhLD4vW7^BTnBEenu-bIE;QQF~(^CpZV(
z{rgzI^?aM?E@~JUhy~ti8tOxAf^SFCXM=~2A~?1g7p30|joZ)H#p`rA)lh}Ns}2F5
z>q@VBy{ZLPAy9?D>lgwMaYHn2ZRVskoELdVn))G|3xf!ja3mOGE&WBV&*Js>K${4#
zJ#@CGHO){&yDo2s;IF{R%v$!r<HfdeQN+Q~kR0a-<lV`dAnW4Z4uZ-Ft1+q&IK>dC
zO5~>)pw;ZE5U4_+G6ed>)=+cU-HbDebx0FSp}2SeKDnTE+WJR6c;~|_pp-Er>xbQt
z__Ey`e5v`l?b@T>ys%en3aob0+t|f_Ikh;O2-92o=Ea=z!c{{!_<14SQS*)VJ=(o<
zHB=$++CZR6$X^?{S4*uz;0+Cdh=@4N+15cB%sdDUKY-`K%Wz`b#@e)R2T*eX2m#kl
zsuC~-`edtbV-$A)7t2pK92uSxM|$-h_@W^w($Y2>mPi-xgRXy9w|ESE7Q(+@6Y=WW
zcu~++U%pBZ@S#9@m1<HgrV4>71l}+Z(5m%V*X6BvggX->u@)@G*5c@OHH5qocfYv)
z)dwKSTGZm&<!{LI<uCE2I8CgzUwS;dDNbk7KHX)6W8_9~7dylm00XY;90*w9XANPE
zSMu+!0Zty~)Y41egm+vV*H`wZp6evG!}a@hIh;#Vy;dP`Iv`Lb<fj9w)jX>Zs6t>t
z5YYR{V^17Ei(TCvM#jCEZDM#-6KqM7JvjZ<ho)#EUWe4J-REkLg-M*X=%Y}Nb56_g
xtS$E#hOyVJX@7ai;qOjWC1fB}4R06-{6DGsxc5`{gOLCL002ovPDHLkV1ni~xu*aC

diff --git a/static/img/favicon.ico b/static/img/favicon.ico
index 3d1388db2d0fdb2e7db387165624999a91b44650..f6002706ce67517c66bb63ea5bef45d6a5cd1674 100644
GIT binary patch
literal 15406
zcmeHOd5{#<8SkE%-JRLFx@UK}m4yHS0XYmuOhAf7Fn~s52uDyCcDHAjln{(Dv68Yh
zK~qulmj)ypl`^L$8c8DNsF<>1tfZnQ<q;u=Lc%42k;C2X>6Mq?_j-D!yXW;W?5_U9
zRK4x)_rCA@{oeQPV<kzJqLQLWcs5I&F-e*&Nm6sO`8`pUq}_;{KE0SeL6V+plB9`{
zfeJLtcsxS=l+MBoHDB1KX!<`Ct)LgfejbN3FC(Kivjk+m1Nn0Z%p;s58IrZzDe69B
z>7<rD#pJpy%dFnVBB_xqG54Ded$940-3Gq5mvoo^n#D%7FxY1`W3FX#q=v<Y&u7W2
z_PA|qCk{$SVLEh6oa;aS0M{jbcZg5>g5AbB(p9y>RtuY+cKzhS@3Q3LM_DvCh1-%N
zwM=O{U9v&C;J(jGKeOsJE?akrW^$1uOj-ZGvc9R?>!lxUn8u>YhfDb&J9b&T_ku%@
zJ<iTw0-oiA__SNxx=huK9_YX3rBD3R*Z+l)9XT3j*>xuzHb^&{FMQiiKeOU*T%UMk
zR_$}>bKQJlnvyTPXW6jxm!owh{^SRxqo=G-I?#n(N$o6`VQT4<EH><8T(9P$B}|IM
z7(KIV50-UN&T77Q8|l)oxs}C%|Fp#+wd_|cl4wNz-OnQFW|sKqeGXlcB^^`S{7c_d
zACOkci)GLDe2-+@x^_FN#->94LDZ{P5xR@vRUX%_Uuu^fh<EB|nh_QtQ2*55ANXfg
zO<$wrdv}8K3n-%#c=qvNzCVw+og_oD{l&BN8#{U@C|chx@)xk&<t6+s%I+pz%TBdV
z>c@b0KSCiau0W1-?;oKZsjmh<vw@9+FJBhe6XrKi4z|c<7!FMvsNXe?i)_X(`zqSa
z#XO|0{w?Pc8}bqU9aSa-a5IiK`HWM<Ez{OJ4!A;W;!`)}bESSGwe%MpFOnS2<K$R<
z06wof$1@vxg?=#0+jvQo@AP%gG0HEETcF89V$MB0E)s7j;-epJb@rnoTU4(0G14j%
zHE-N2lt;d;amvE>e4;;(HeJT*7wm*DbWeY%dHp^Mm!3^j-+bzMXnfn)Ts!7E^y}ST
z914VKaRBxXue?+I`QXDgOU(Yd7e3<qb`XB<W|l$U{cg4Rwc}T__{^`cx=S~)no)}|
z7Dh{TgRm(?5<}sGULgm<B<x(iZ>1l$SN>B=f9bHBT>O&?eBzK<^KXZo9gDD4t?waw
zoakNTe>c9;epZaX>hGTT=%=@%J^WdOX^#topKN)!0-xqK_IaJ%CVw}v->istjWZ(r
zn&wZkx~Vs_x=HOUHgqn^U#`Hfoz&);_aZ)FJLZWZE+TxZj(I(6E?SIv-P`{7e4c4I
z=9&G)r#Ts|6GV0dag_ICf_R6%F#nkU$q4TJ%QY$V%fEBzd)qgTp&kCoJKdabi14lY
zpIv)^)lO`6@Q9>G`}KV#ZiJ0Cu&qD%T(|8E=JDk@HTfic-5*OhUiJw)tLZDe(ye&E
z{Bs$!eK{6)_#nCD@j(2n*0%!VKnga_T3Di|AAa_xH(A}}E(bQ{KXuLTgYeH1He@A~
zgKr-w!k253Os>re+r3<y!Fuo=UwpzOZ2D!pddDhx!?Pa{;X|z=&sJRG@^ATK6Bc0-
zw)MlD;2x3hDK0F2Bsr4R&wt1t8}<mx!nK~`(3N5=cu~ZG)_%!FKjiB@$n$*1XMBmr
z$#p9KmSYLevDRr*|7&yW8;&)e#X;$0%~-!2b;_659Q~btBHu>|!@?6i)lPj1*6&9|
z91^qcVo`M>52<UO=6;S1pJ&E3PV@CU<%?{KFx_!VXHT<|*M(&v;uRQ2wqVnZ<M&PV
z0i3tMwr9Ht#5KpaEo93N%P)=BiF_aSLX6WP@QP(%oJRZJ8dTPPxbC!}x3XlmL%$w<
z_Je3A&%!r{fpOLh`eC%`XDN+jNY<@?;alth+9$ylt<;Jz5c?!BQ~A4-MY3H?&1$_L
zQnlV?)c>K4??rvukMItHxsPJL@251i)3}>tNr!YL*r+r-$T4@aSXL{{1fSc`AN(A3
zPS`K`wF|C8x}C;tWDEJguK3{pRIU4B@Y;oT`(Hf!vxj5#tFXas?N-`)Mh{L7n4DU7
zrU`BN7I3bjzbTJVeq~WkLth3A!oqMW4^&=Yb3V%ZsR8o0<#(@V0edD-5oZ7SGZ}l<
zZQxC7k<yt%*<aQAH?%xq9V6`XEr;T~X%p(^89%<+*0->Kbq)51W|Ttxf*mE_){gyD
zDW3N9>KE)PrTN)4(}0~XY^r{oWirmSHbR&7l6~>AHyuSMI?gfYP0ZO+(uw9SDW_pC
zhW6)zY&z2O#tF(pHRXVFru9L7w=f2sKldNXp|h|)xIHjgZ8zqDoB!Gy>&onnM_BfT
z!z{D%6&A^iDf<|XiqE{Ar%^iX{{q(x<o{V;!+hL!t`ktcmY;}|+GWi1D~Ghk8jItn
zZ(F5(fSQXx!D1t>z}eB|SfeJ&903qXk1^AbPW#7Y{xXXVna$!ezRc<ueh+(S|3qHA
z_fu`$sm`4vZp6{693b;~gupQ=dF7AIHKyg)s-H5GYtm>p<5_(6-PM!_aoa57pIg^`
z5$Zh6SpwTv|M@%DxU{#F`Rwa~xJ7QKh^r$Hn0p}2cdyx=uYu-Id&ITl*WjGst+096
zVV^JYGx2=kKX#6O?*q=C8YT9bl2<+&jz4k5Sv)TT%wKaI#;vG3bax??eh_~-F$8Ph
zNoK$~GM(wlbRJ_n9|v~1T^HYDLoWw@nD%Vw#F^&aN-I;q{bymhlUxx0#2mCq4d(+m
zBgkUED6{5YEVXnmtHqwOyRUNO1N)xY8xDo?A?FP4+4a3+(J#?lIHX<}{^Bu~#*CWL
z%PahD&qMm!KZN2zoQZo*GZt6FJ)Hl={HZ)>f630*{hnHGo_~hnl-oeujXT50+GT?4
zj|YF;WubEkH)s2I<})va@;~R3*YCnS`w2U@Fz@HfKXvtQSft)O*R^xD-sMCSQ`$Yx
z76th-_F!+M>hts<{&f@AqrE=KLvqPuxKDB~>itsTS)j$8#sE4u4C6mb275fO;NA0F
z+>&!YgZP&?3HnH38qT<4Bj#5#1{d>b97j9$J!5rqr|*I0Uo*0W@p>PAF30)9|J@%H
ze>zKujk*%P_z}2-8M7+;cjAxs8+gv?E`x#af3#sL<9(&aIk+3s;~Vv-AiSI5A<xS#
zkU#Dq(l|?Z5ry@g+6C%7%`wtg|M+3~rGfj)@c-j}GNQB~{`NI4-GfWa`38$5M+oym
z=ha?!5k%OIxIE@P9r_)PxDfM*YWSPBb>8NMWq~<QRb!T&U*5Q*A>Y#i4Bz#lJAc*l
zN87`=B*z<tWl%qF>v`3ohP=^|ZSNU__J7dL(eL}b_+!mZ^J-BU(ETqzJdd=4#GUR0
zVh;3E4;i7|^WmSo>Iort%1<2UXVu`Fvif8EJ|n|k71qQE1Gau~wBL0nadx^DYnaiV
z{F4hGu9iP>-7JAS@{e<Fo$jC>KnP_g$p17p(fzwfVwnG&2fpX`jB!^YEVe19A0*Di
zo&Q##D|X#W_OlnnA2vOG?M|clv>%oz4gLOB37k#x=HEu`-Qj2lCq?q^xPjsy9WsmG
zd3M|P|29rGYHYZjyY-HIbwM|<9rTYs_O58|gY)h5_0L!9dtKGu>$3Q|pXnP<H=qpm
zU~j^AJV-6u%l84J>LuoVef*yQY?VTU?>`_7>5~2a4dx7VCotLagKGAA%sg^V#vbD6
z=3V|~a)VZwgFGDeE5q#iQ<$qC;PdtLr(fjzBX<7r>0jh&w5JwT#+UL%YZQCm<cCq2
zW*pA7ch99JU*;=*Q#<-rVP15q(ne+f^uFw$gNxd(uNJcv$Kp&gA7*Yn==?FiCoW=^
zKCvrUE%daYa-jbashzNv#YQeH1-f%-m0ca~z?IUd?l1a&Db14ce8TUXJGl5T^-ap<
z^_9rOAz=9ZpGJ62;l@b(uZnR<?a){Gk_(yGpmoo|IXmsM1oo|-z6{5k{GbySVTPm^
zLX63oHkQNqkca)iGrfM~;e^^z=p?K#{Y(hr6(U30*-+%;0h|fG0iON2gJjh?*w7E)
zzV!o58_o`^033`6zUQt_2LFv1D;~x3bp+or59t<PdXg-3xbDVWhd$XopBW6=6*e({
zrMvR{URsB71<w6%#~qqS!0iRh4-cUYzD<F@Q(V6A2+1grB^}bW=D-!UFGO7M!295V
F{{!S91MUC-

literal 977
zcmaJ=&ui0A9M4ol3e)LHJv}l|2PQ8sX}TpeZf(-KvSo~}u<jyDlh-zE$&1OG&304|
z4i)qd5YK}62k5|q2N5>V>#iOJ1^)tHy0-IR4ZOS`d_JG=kN0`|t1EXWbJuem$4%B2
ztvZ{hvT@-I`@eYEEwJettu*NxY15t)W3J?p76!Gz>EJqcyxsd>aFOHA-tZeu+O(H-
zmjt4dVZ=0u7@OmY^J(O`TbP0t?)ag>|N8Ke2fk<U>#8l;k%_zh;$Do`_EsA1-j=I*
z{QMnIOm!v@VCsN0*bWmtHTb@+&eqv6<Ut=ow+#LysiwUOOcG<DiUq+%2!UBmMCzO(
ztG9tHAr(p*M3NvO9Z9+@fx*YKXtCGU>sECTi|q`)OKGG-*z5Jgo+6UC1Cgd_P?Di6
z3k)G7yCHQ_Axx%+3KmY>*pH}BLXassEwV!mo@IJcLJ*B)!(`AV)-ael5k#Vtl{5s}
z_Wz+lFhVD^j!*Obr*P8PjWDd^gzUsFySVmr7An%s7(0~24MMhuU0m%FN|G*#fNA!-
z25znUp+|bjOrK-hdM!+-6S}x&89Y-Fec#hdvx+I3no=oitn(GMY|W`vRLECKs-~el
z8geb-?gTibL#}tq&5z|~b_gOC*}}2^0DIM#1fXBG?vKv}jnx})z45uoW4Vwe1GCHh
z>#~PO%t6_5WL>rynIDJD@iDXZz2~ogvS(4MS*1pL+&Xyk_VYq+vjr}H-FS5T>gmGc
z!>K11r;pBmd!G}Rlq-2jR+j7^H;*nY9~8}*=KjR9Pe7PBca{5|Oyb|-VJCZJwaSY1
IuDtp15BHNTdjJ3c


From 23b51603b7f16dd9a8a2c05c2fb04dcf3982e136 Mon Sep 17 00:00:00 2001
From: zhe_mstr <zhe@microstrategy.com>
Date: Tue, 11 Feb 2025 13:24:56 +0800
Subject: [PATCH 2/5] fix comments

---
 .../add-and-remove-datasource-from-project.md  |  6 +++---
 ...ing-from-dsn-to-dsnless-for-a-datasource.md |  8 ++++----
 .../create-and-get-a-subscription.md           |  6 +++---
 .../create-subscription-for-multi-content.md   |  2 +-
 ...reate-subscription-with-prompted-content.md |  8 ++++----
 .../manage-drivers/retrieve-drivers.md         |  2 +-
 .../get-history-list/get-history-list.md       | 12 ++++++------
 .../create-a-migration-package.md              |  2 +-
 .../import-a-migration-package.md              |  2 +-
 .../view-newly-created-package.md              |  2 +-
 .../view-uploaded-package.md                   |  2 +-
 .../edit-migrations-and-migration-groups.md    | 12 ++++++------
 .../object-migration-between-environments.md   | 12 ++++++------
 .../project-merge-between-environments.md      | 18 +++++++++---------
 .../upload-and-download-migration-packages.md  |  4 ++--
 .../validate-migrations.md                     |  8 ++++----
 .../manage-an-intelligence-server-cluster.md   |  2 +-
 .../administration/monitors/manage-caches.md   |  6 +++---
 .../monitors/monitor-and-manage-cube-caches.md |  6 +++---
 .../monitors/project-administration.md         | 12 ++++++------
 .../manage-fences/create-fence.md              |  6 +++---
 .../manage-fences/retrieve-specific-fence.md   |  2 +-
 .../manage-fences/update-specific-fence.md     |  2 +-
 .../manage-quick-search-indices.md             |  2 +-
 .../user-management/create-security-roles.md   |  4 ++--
 .../analytics/export-to-pdf.md                 |  8 ++++----
 .../apply-filters-to-a-dossier.md              | 10 +++++-----
 .../create-a-cube-object.md                    |  4 ++--
 .../retrieve-a-cube-definition.md              |  8 ++++----
 .../update-a-cube-definition.md                |  4 ++--
 .../retrieve-the-hierarchy-of-a-document.md    |  2 +-
 ...-irr-definition-with-advanced-properties.md |  2 +-
 .../retrieve-an-irr-definition.md              |  2 +-
 ...perties-of-an-incremental-refresh-report.md |  2 +-
 .../manage-page-by-information.md              |  2 +-
 .../create-a-new-report.md                     |  2 +-
 ...-a-derived-elements-definition-in-report.md |  2 +-
 .../retrieve-a-reports-definition.md           |  2 +-
 ...trieve-applicable-properties-of-a-report.md |  2 +-
 ...ate-the-definition-of-an-existing-report.md |  2 +-
 .../retrieve-transaction-report-definition.md  |  2 +-
 .../object-discovery/folder-browsing.md        | 10 +++++-----
 .../object-discovery/search-for-objects.md     |  8 ++++----
 ...-project-load-settings-on-server-startup.md |  4 ++--
 ...t-project-applicable-advanced-properties.md |  2 +-
 .../get-project-with-advanced-properties.md    |  6 +++---
 .../update-project-advanced-property.md        | 10 +++++-----
 ...trieve-data-from-the-intelligence-server.md | 18 +++++++++---------
 .../retrieve-dataset-sql.md                    |  2 +-
 .../retrieve-grid-or-graph-query-details.md    |  2 +-
 .../retrieve-report-or-card-sql.md             |  2 +-
 .../retrieve-visualization-query-details.md    |  2 +-
 .../change-ownership.md                        |  2 +-
 .../manage-object-acl.md                       |  8 ++++----
 .../remove-add-object-translations.md          |  2 +-
 .../retrieve-object-translations.md            |  2 +-
 .../update-object-translations.md              |  2 +-
 .../manage-the-schema/lock-the-schema.md       |  2 +-
 .../reload-the-schema-asynchronously.md        |  2 +-
 .../reload-the-schema-synchronously.md         |  2 +-
 .../retrieve-the-schema-lock.md                |  2 +-
 .../manage-the-schema/unlock-the-schema.md     |  2 +-
 .../create-an-attribute-object.md              |  2 +-
 ...attributes-definition-within-a-changeset.md |  2 +-
 .../retrieve-an-attributes-definition.md       |  4 ++--
 .../update-an-attributes-definition.md         |  4 ++--
 ...ributes-relationships-within-a-changeset.md |  4 ++--
 .../retrieve-an-attributes-relationships.md    |  2 +-
 .../update-an-attributes-relationships.md      |  4 ++--
 ...e-formulas-definition-within-a-changeset.md |  2 +-
 ...e-formulas-definition-within-a-changeset.md |  2 +-
 .../retrieve-a-base-formulas-definition.md     |  2 +-
 .../create-a-consolidation-object.md           |  2 +-
 .../retrieve-a-consolidations-definition.md    |  4 ++--
 .../update-a-consolidation-object.md           |  2 +-
 ...filter-elements-using-custom-expressions.md |  2 +-
 .../create-a-custom-group-object.md            |  2 +-
 ...tom-groups-definition-within-a-changeset.md |  2 +-
 .../retrieve-a-custom-groups-definition.md     |  4 ++--
 .../update-a-custom-groups-definition.md       |  2 +-
 .../retrieve-a-datamart-definition.md          |  2 +-
 ...ieve-applicable-properties-of-a-datamart.md |  2 +-
 .../create-a-derived-element.md                |  2 +-
 .../replace-an-existing-element.md             |  2 +-
 .../retrieve-a-derived-elements-definition.md  |  4 ++--
 .../manage-drill-maps/create-a-drill-map.md    |  2 +-
 .../retrieve-a-drill-map-definition.md         |  4 ++--
 .../retrieve-a-list-of-objects.md              |  2 +-
 .../manage-drill-maps/update-a-drill-map.md    |  2 +-
 .../create-a-fact-object.md                    |  2 +-
 ...ve-a-facts-definition-within-a-changeset.md |  2 +-
 .../retrieve-a-facts-definition.md             |  4 ++--
 .../update-a-fact-object.md                    |  2 +-
 ...a-filter-object-with-a-custom-expression.md |  2 +-
 .../create-a-filter-object.md                  |  2 +-
 ...-a-filters-definition-within-a-changeset.md |  2 +-
 .../retrieve-a-filters-definition.md           |  2 +-
 .../update-a-filters-definition.md             |  2 +-
 ...retrieve-a-metrics-applicable-properties.md |  2 +-
 ...-a-metrics-definition-within-a-changeset.md |  2 +-
 .../retrieve-a-metrics-definition.md           |  2 +-
 .../create-a-prompt-within-a-changeset.md      |  4 ++--
 .../retrieve-a-prompts-definition.md           |  2 +-
 ...-filter-object-using-a-custom-expression.md |  2 +-
 .../create-a-security-filter-object.md         |  2 +-
 .../retrieve-a-security-filter-definition.md   |  6 +++---
 ...-subtotals-definition-within-a-changeset.md |  2 +-
 .../retrieve-a-subtotals-definition.md         |  2 +-
 .../create-a-new-table-object.md               |  2 +-
 ...-list-of-all-available-table-definitions.md |  4 ++--
 ...ve-a-partition-mapping-tables-definition.md |  4 ++--
 .../retrieve-a-prompt-of-an-sap-hana-table.md  |  4 ++--
 .../retrieve-a-tables-definition.md            |  4 ++--
 .../update-a-prompt-of-an-sap-hana-table.md    |  2 +-
 .../update-a-tables-definition.md              |  2 +-
 ...update-a-tables-physical-table-structure.md |  2 +-
 .../update-sap-hana-parameters.md              |  2 +-
 .../create-a-transformation-object.md          |  2 +-
 .../retrieve-a-transformations-definition.md   |  6 +++---
 .../update-a-transformations-definition.md     |  2 +-
 .../create-a-user-hierarchy.md                 |  2 +-
 ...eve-a-list-of-available-user-hierarchies.md |  2 +-
 .../retrieve-a-user-hierarchys-definition.md   |  2 +-
 ...rmance-by-working-with-partial-resources.md |  8 ++++----
 124 files changed, 231 insertions(+), 231 deletions(-)

diff --git a/docs/common-workflows/administration/datasource-management/add-and-remove-datasource-from-project.md b/docs/common-workflows/administration/datasource-management/add-and-remove-datasource-from-project.md
index 72857332a..5c4de973f 100644
--- a/docs/common-workflows/administration/datasource-management/add-and-remove-datasource-from-project.md
+++ b/docs/common-workflows/administration/datasource-management/add-and-remove-datasource-from-project.md
@@ -8,7 +8,7 @@ This workflow sample demonstrates how to add a datasource to a project. To see h
 1. [Get list of datasources based on project.](#get-list-of-datasources-based-on-project) `GET /api/projects/{projectId}/datasources`
 1. [Add a datasource to a project.](#add-datasource-to-project) `PATCH /api/projects/{projectId}/datasources`
 
-A detailed description of each step of this request is listed down below. For this sample we are using the Strategy Tutorial project with project ID B7CA92F04B9FAE8D941C3E9B7E0CD754. You can obtain the project ID from `GET /api/projects`.
+A detailed description of each step of this request is listed down below. For this sample we are using the MicroStrategy Tutorial project with project ID B7CA92F04B9FAE8D941C3E9B7E0CD754. You can obtain the project ID from `GET /api/projects`.
 
 ## Get list of datasources based on project
 
@@ -120,7 +120,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 Endpoint: [PATCH /api/projects/\{projectId}/datasources](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/updateProjectDatasources)
 
-This endpoint allows the caller to add and remove a datasource to a specific project with the Strategy REST Server. In this request we will add a datasource. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. For this sample we will be adding the Act! Essentials datasource to the Strategy Tutorial project. You can find the datasourceId using the endpoint `GET /api/datasources` and the projectId using `GET /api/projects`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the project's datasources.
+This endpoint allows the caller to add and remove a datasource to a specific project with the Strategy REST Server. In this request we will add a datasource. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. For this sample we will be adding the Act! Essentials datasource to the MicroStrategy Tutorial project. You can find the datasourceId using the endpoint `GET /api/datasources` and the projectId using `GET /api/projects`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the project's datasources.
 
 Sample Request
 
@@ -248,7 +248,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 Endpoint: [PATCH /api/projects/\{projectId}/datasources](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Datasource%20Management/updateProjectDatasources)
 
-This endpoint allows the caller to add and remove a datasource to a specific project with the Strategy REST Server. In this request we will remove a datasource. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. For this sample we will be removing the Act! Essentials datasource from the Strategy Tutorial project. You can find the datasourceId using the endpoint `GET /api/datasources` and the projectId using `GET /api/projects`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the project's datasources.
+This endpoint allows the caller to add and remove a datasource to a specific project with the Strategy REST Server. In this request we will remove a datasource. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. For this sample we will be removing the Act! Essentials datasource from the MicroStrategy Tutorial project. You can find the datasourceId using the endpoint `GET /api/datasources` and the projectId using `GET /api/projects`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the project's datasources.
 
 Sample Request
 
diff --git a/docs/common-workflows/administration/datasource-management/convert-connection-string-from-dsn-to-dsnless-for-a-datasource.md b/docs/common-workflows/administration/datasource-management/convert-connection-string-from-dsn-to-dsnless-for-a-datasource.md
index d76880e3c..4737913b4 100644
--- a/docs/common-workflows/administration/datasource-management/convert-connection-string-from-dsn-to-dsnless-for-a-datasource.md
+++ b/docs/common-workflows/administration/datasource-management/convert-connection-string-from-dsn-to-dsnless-for-a-datasource.md
@@ -141,7 +141,7 @@ Sample Response
 After conversion, you should be able to see the DSN-less format connection string in the response by calling the API to get the datasource definition.
 
 ```json
-"connectionString": "DRIVER={Strategy ODBC Driver for PostgreSQL Wire Protocol};APPLICATIONUSINGTHREADS=1;DATABASE=test;DEFAULTLONGDATABUFFLEN=1024;DESCRIPTION=Strategy ODBC Driver for PostgreSQL Wire Protocol;ENABLEDESCRIBEPARAM=1;ENCRYPTIONMETHOD=1;FETCHTSWTZASTIMESTAMP=1;FETCHTWFSASTIME=1;HOSTNAME=xx.xx.xx.xx;HOSTNAMEINCERTIFICATE=xx.xx.xx.xx;PORTNUMBER=5432;TRANSACTIONERRORBEHAVIOR=0;UID=uid;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;"
+"connectionString": "DRIVER={MicroStrategy ODBC Driver for PostgreSQL Wire Protocol};APPLICATIONUSINGTHREADS=1;DATABASE=test;DEFAULTLONGDATABUFFLEN=1024;DESCRIPTION=MicroStrategy ODBC Driver for PostgreSQL Wire Protocol;ENABLEDESCRIBEPARAM=1;ENCRYPTIONMETHOD=1;FETCHTSWTZASTIMESTAMP=1;FETCHTWFSASTIME=1;HOSTNAME=xx.xx.xx.xx;HOSTNAMEINCERTIFICATE=xx.xx.xx.xx;PORTNUMBER=5432;TRANSACTIONERRORBEHAVIOR=0;UID=uid;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;"
 ```
 
 Sample Request
@@ -188,7 +188,7 @@ Sample Response
         "charEncodingWindows": "multibyte",
         "charEncodingUnix": "utf8",
         "tablePrefix": "",
-        "connectionString": "DRIVER={Strategy ODBC Driver for PostgreSQL Wire Protocol};APPLICATIONUSINGTHREADS=1;DATABASE=test;DEFAULTLONGDATABUFFLEN=1024;DESCRIPTION=Strategy ODBC Driver for PostgreSQL Wire Protocol;ENABLEDESCRIBEPARAM=1;ENCRYPTIONMETHOD=1;FETCHTSWTZASTIMESTAMP=1;FETCHTWFSASTIME=1;HOSTNAME=xx.xx.xx.xx;HOSTNAMEINCERTIFICATE=xx.xx.xx.xx;PORTNUMBER=5432;TRANSACTIONERRORBEHAVIOR=0;UID=uid;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;",
+        "connectionString": "DRIVER={MicroStrategy ODBC Driver for PostgreSQL Wire Protocol};APPLICATIONUSINGTHREADS=1;DATABASE=test;DEFAULTLONGDATABUFFLEN=1024;DESCRIPTION=MicroStrategy ODBC Driver for PostgreSQL Wire Protocol;ENABLEDESCRIBEPARAM=1;ENCRYPTIONMETHOD=1;FETCHTSWTZASTIMESTAMP=1;FETCHTWFSASTIME=1;HOSTNAME=xx.xx.xx.xx;HOSTNAMEINCERTIFICATE=xx.xx.xx.xx;PORTNUMBER=5432;TRANSACTIONERRORBEHAVIOR=0;UID=uid;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;",
         "parameterizedQueries": false,
         "extendedFetch": false,
         "login": {
@@ -315,7 +315,7 @@ Sample Response
 After conversion, you should be able to see the DSN-less format connection string in the response by calling the API to get the datasource connection definition.
 
 ```json
-"connectionString": "DRIVER={Strategy ODBC Driver for SQL Server Wire Protocol};DATABASE=tpch;HOSTNAME=10.27.69.102;KEEPALIVE=0;KEEPCONNECTIONACTIVE=0;LOADBALANCETIMEOUT=0;LOADBALANCING=0;LOGINTIMEOUT=15;MAXPOOLSIZE=100;MINPOOLSIZE=0;MULTISUBNETFAILOVER=0 - FALSE;PORTNUMBER=1433;PROXYMODE=0;QUERYTIMEOUT=0;REPORTCODEPAGECONVERSIONERRORS=0;SNAPSHOTSERIALIZABLE=0;SOCKETIDLETIMECHECKINTERVAL=1500;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;"
+"connectionString": "DRIVER={MicroStrategy ODBC Driver for SQL Server Wire Protocol};DATABASE=tpch;HOSTNAME=10.27.69.102;KEEPALIVE=0;KEEPCONNECTIONACTIVE=0;LOADBALANCETIMEOUT=0;LOADBALANCING=0;LOGINTIMEOUT=15;MAXPOOLSIZE=100;MINPOOLSIZE=0;MULTISUBNETFAILOVER=0 - FALSE;PORTNUMBER=1433;PROXYMODE=0;QUERYTIMEOUT=0;REPORTCODEPAGECONVERSIONERRORS=0;SNAPSHOTSERIALIZABLE=0;SOCKETIDLETIMECHECKINTERVAL=1500;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;"
 ```
 
 Sample Request
@@ -346,7 +346,7 @@ Sample Response
     "charEncodingWindows": "multibyte",
     "charEncodingUnix": "utf8",
     "tablePrefix": "",
-    "connectionString": "DRIVER={Strategy ODBC Driver for SQL Server Wire Protocol};DATABASE=tpch;HOSTNAME=10.27.69.102;KEEPALIVE=0;KEEPCONNECTIONACTIVE=0;LOADBALANCETIMEOUT=0;LOADBALANCING=0;LOGINTIMEOUT=15;MAXPOOLSIZE=100;MINPOOLSIZE=0;MULTISUBNETFAILOVER=0 - FALSE;PORTNUMBER=1433;PROXYMODE=0;QUERYTIMEOUT=0;REPORTCODEPAGECONVERSIONERRORS=0;SNAPSHOTSERIALIZABLE=0;SOCKETIDLETIMECHECKINTERVAL=1500;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;",
+    "connectionString": "DRIVER={MicroStrategy ODBC Driver for SQL Server Wire Protocol};DATABASE=tpch;HOSTNAME=10.27.69.102;KEEPALIVE=0;KEEPCONNECTIONACTIVE=0;LOADBALANCETIMEOUT=0;LOADBALANCING=0;LOGINTIMEOUT=15;MAXPOOLSIZE=100;MINPOOLSIZE=0;MULTISUBNETFAILOVER=0 - FALSE;PORTNUMBER=1433;PROXYMODE=0;QUERYTIMEOUT=0;REPORTCODEPAGECONVERSIONERRORS=0;SNAPSHOTSERIALIZABLE=0;SOCKETIDLETIMECHECKINTERVAL=1500;VALIDATESERVERCERTIFICATE=1;XMLDESCRIBETYPE=-10;",
     "parameterizedQueries": true,
     "extendedFetch": false,
     "database": {
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
index 7a7735ba4..92ddfcab3 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
@@ -88,7 +88,7 @@ The authorization token "`x-mstr-authtoken`" is returned in the response header.
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 Sample Request
 
@@ -115,9 +115,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "alias": "",
-      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
index 7c6382a69..3622c00bf 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
@@ -147,7 +147,7 @@ Sample Response
         "name": "Shared Drive",
         "deliveryMode": "EMAIL",
         "deviceId": "18F9613B681E4E4FA671D1AED6B7B375",
-        "value": "C:\\Program Files\\Strategy\\Analytics Modules",
+        "value": "C:\\Program Files\\MicroStrategy\\Analytics Modules",
         "isDefault": true
       }
     ]
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
index 1b2868828..beda96180 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
@@ -86,7 +86,7 @@ The authorization token "`x-mstr-authtoken`" is returned in the response header.
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 Sample Request
 
@@ -113,9 +113,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "alias": "",
-      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -236,7 +236,7 @@ Sample Response
         "name": "Shared Drive",
         "deliveryMode": "EMAIL",
         "deviceId": "18F9613B681E4E4FA671D1AED6B7B375",
-        "value": "C:\\Program Files\\Strategy\\Analytics Modules",
+        "value": "C:\\Program Files\\MicroStrategy\\Analytics Modules",
         "isDefault": true
       }
     ]
diff --git a/docs/common-workflows/administration/manage-drivers/retrieve-drivers.md b/docs/common-workflows/administration/manage-drivers/retrieve-drivers.md
index 69f7e687a..d8cf83088 100644
--- a/docs/common-workflows/administration/manage-drivers/retrieve-drivers.md
+++ b/docs/common-workflows/administration/manage-drivers/retrieve-drivers.md
@@ -57,7 +57,7 @@ You can get all the driver objects in the body of the response.
       "enabled": true,
       "id": "43A6758EF9CE9BBB12AD13C2636B162D",
       "isODBC": true,
-      "name": "Strategy ODBC Driver for SQL Server Wire Protocol"
+      "name": "MicroStrategy ODBC Driver for SQL Server Wire Protocol"
     }
   }
 }
diff --git a/docs/common-workflows/administration/manage-history-lists/get-history-list/get-history-list.md b/docs/common-workflows/administration/manage-history-lists/get-history-list/get-history-list.md
index 2590bb542..1d5ca4789 100644
--- a/docs/common-workflows/administration/manage-history-lists/get-history-list/get-history-list.md
+++ b/docs/common-workflows/administration/manage-history-lists/get-history-list/get-history-list.md
@@ -72,7 +72,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
       "status": "reserved",
       "sequenceNumber": 10,
       "parentId": "00000000000000000000000000000000",
-      "clientType": "StrategyWeb",
+      "clientType": "MicroStrategyWeb",
       "requestType": "document",
       "requestStatus": "job_running",
       "startTime": "2022-06-30T06:10:50Z",
@@ -88,7 +88,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
         "folderName": "HLCodeCoverage"
       },
       "projectId": "9DE876B611E7C33BF65B0080EF45D3E8",
-      "projectName": "Strategy Tutorial",
+      "projectName": "MicroStrategy Tutorial",
       "resultFlags": 0,
       "cacheId": null,
       "messageText": "User request is completed.",
@@ -108,7 +108,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
           "status": "new_message",
           "sequenceNumber": 11,
           "parentId": "0A6B683C4AF5FECC365F4CA18C11710A",
-          "clientType": "StrategyWeb",
+          "clientType": "MicroStrategyWeb",
           "requestType": "report",
           "requestStatus": 1,
           "startTime": "2022-06-30T06:10:51Z",
@@ -123,7 +123,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
             "folderId": "D6253070472AA691A4E9C88E72B7AC64",
             "folderName": "HLCodeCoverage"
           },
-          "projectName": "Strategy Tutorial",
+          "projectName": "MicroStrategy Tutorial",
           "resultFlags": "dtls_expr_nothing",
           "messageText": "User request is completed.",
           "displayName": "1.NormalReport",
@@ -143,7 +143,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
       "status": "new_message",
       "sequenceNumber": 9,
       "parentId": "00000000000000000000000000000000",
-      "clientType": "StrategyWeb",
+      "clientType": "MicroStrategyWeb",
       "requestType": "report",
       "requestStatus": "loading_prompt",
       "startTime": "2022-07-30T06:10:51Z",
@@ -159,7 +159,7 @@ If successful, this API call returns a `200 OK` status code and the list of docu
         "folderName": "_Chun"
       },
       "projectId": "9DE876B611E7C33BF65B0080EF45D3E8",
-      "projectName": "Strategy Tutorial",
+      "projectName": "MicroStrategy Tutorial",
       "resultFlags": "dtls_expr_nothing",
       "messageText": "User request is completed.",
       "displayName": "3Ms",
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-a-migration-package.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-a-migration-package.md
index a06b3e165..92ef8a050 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-a-migration-package.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/create-a-migration-package.md
@@ -24,7 +24,7 @@ This workflow sample demonstrates how to create a migration package using REST A
 
 ## Creating a project package
 
-In this workflow sample, you want to create a project package that contains a `"Year"` object with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4` and all its dependents in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. Use `"replace"` as a conflict rule for all these objects.
+In this workflow sample, you want to create a project package that contains a `"Year"` object with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4` and all its dependents in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. Use `"replace"` as a conflict rule for all these objects.
 
 :::info
 
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/import-a-migration-package.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/import-a-migration-package.md
index a24d96bd0..d2a50e706 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/import-a-migration-package.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/import-a-migration-package.md
@@ -27,7 +27,7 @@ This workflow sample demonstrates how to import a migration package using REST A
 
 ## Import a project package
 
-You want to import a project package that contains a `"Year"` object, with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4`, and all its dependents in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You are using the `"Demo Project"`, which has a project ID of `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to import a project package that contains a `"Year"` object, with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4`, and all its dependents in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You are using the `"Demo Project"`, which has a project ID of `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-newly-created-package.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-newly-created-package.md
index 0858c7e2a..760a600c7 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-newly-created-package.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-newly-created-package.md
@@ -15,7 +15,7 @@ This workflow sample demonstrates how to view a newly created migration package
 1. [Download the package and save it as a binary file](#download-the-package-and-save-it-as-a-binary-file)
 1. [Delete the package](#delete-the-package)
 
-In this workflow sample, you want to create a project package that contains a `"Year"` object with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4` and all its dependents in the Strategy Tutorial project. You also want to view the detailed definition of the `"Year"` object. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. Use `"replace"` as a conflict rule for all these objects.
+In this workflow sample, you want to create a project package that contains a `"Year"` object with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4` and all its dependents in the MicroStrategy Tutorial project. You also want to view the detailed definition of the `"Year"` object. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. Use `"replace"` as a conflict rule for all these objects.
 
 :::info
 
diff --git a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-uploaded-package.md b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-uploaded-package.md
index d8b00a751..b4486c566 100644
--- a/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-uploaded-package.md
+++ b/docs/common-workflows/administration/migrations/create-and-import-migration-packages/view-uploaded-package.md
@@ -14,7 +14,7 @@ This workflow sample demonstrates how to view an uploaded migration package usin
 1. [Get the package detailed definition](#get-the-package-detailed-definition)
 1. [Delete the package](#delete-the-package)
 
-You have a project package that contains a `Year` object, with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4`, and all its dependents in the Strategy Tutorial project. You want to view the readable definitions of objects from this package for this project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You are also using the `"Demo Project"`, which has a project ID of `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You have a project package that contains a `Year` object, with an attribute object ID of `8D679D5111D3E4981000E787EC6DE8A4`, and all its dependents in the MicroStrategy Tutorial project. You want to view the readable definitions of objects from this package for this project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You are also using the `"Demo Project"`, which has a project ID of `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/edit-migrations-and-migration-groups.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/edit-migrations-and-migration-groups.md
index 9fa24c62c..74d22e754 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/edit-migrations-and-migration-groups.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/edit-migrations-and-migration-groups.md
@@ -67,7 +67,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -380,7 +380,7 @@ Sample Response Body:
     "storage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "creating",
     "message": "",
@@ -748,7 +748,7 @@ Use the response body you saved in step 1 and change `name`, `treeView`, and `mi
         "purpose": "migration_group",
         "project": {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "Strategy Tutorial"
+          "name": "MicroStrategy Tutorial"
         },
         "tocView": {
           "settings": {
@@ -770,7 +770,7 @@ Use the response body you saved in step 1 and change `name`, `treeView`, and `mi
       "importInfo": {
         "project": {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "Strategy Tutorial"
+          "name": "MicroStrategy Tutorial"
         }
       }
     },
@@ -780,7 +780,7 @@ Use the response body you saved in step 1 and change `name`, `treeView`, and `mi
         "purpose": "migration_group",
         "project": {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "Strategy Tutorial"
+          "name": "MicroStrategy Tutorial"
         },
         "tocView": {
           "settings": {
@@ -802,7 +802,7 @@ Use the response body you saved in step 1 and change `name`, `treeView`, and `mi
       "importInfo": {
         "project": {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "Strategy Tutorial"
+          "name": "MicroStrategy Tutorial"
         }
       }
     },
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-between-environments.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-between-environments.md
index 90ca2c3d7..7be862179 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-between-environments.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/object-migration-between-environments.md
@@ -87,7 +87,7 @@ Sample Request Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     }
   }
 }
@@ -152,7 +152,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -177,7 +177,7 @@ Sample Response Body:
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   },
@@ -298,7 +298,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "locked",
     "message": "",
@@ -356,7 +356,7 @@ Copy the response body from step 4 and change `"replicated": false`, to `true`.
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "locked",
     "message": "",
@@ -417,7 +417,7 @@ Since the package import is asynchronously processing, this call checks the impo
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   }
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/project-merge-between-environments.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/project-merge-between-environments.md
index 6d943ec53..40a092582 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/project-merge-between-environments.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/project-merge-between-environments.md
@@ -108,7 +108,7 @@ Provide the correct `environment` and `project` in `packageInfo` of the request
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     }
   }
 }
@@ -182,7 +182,7 @@ The value of `packageInfo.status` could be `creating`, and you should keep pulli
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -207,7 +207,7 @@ The value of `packageInfo.status` could be `creating`, and you should keep pulli
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   },
@@ -323,7 +323,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "locked",
     "message": "",
@@ -382,7 +382,7 @@ Sample Response Body:
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   },
@@ -431,7 +431,7 @@ Copy the response body from step 4 and change `"replicated": false"`, to `true`.
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "locked",
     "message": "",
@@ -490,7 +490,7 @@ Copy the response body from step 4 and change `"replicated": false"`, to `true`.
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   },
@@ -553,7 +553,7 @@ The value of `packageInfo.status` could be `creating`, and you should keep pulli
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -618,7 +618,7 @@ The value of `packageInfo.status` could be `creating`, and you should keep pulli
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   },
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/upload-and-download-migration-packages.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/upload-and-download-migration-packages.md
index 8d38d0adb..f94be93d6 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/upload-and-download-migration-packages.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/upload-and-download-migration-packages.md
@@ -212,7 +212,7 @@ Sample Request Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     }
   }
 }
@@ -300,7 +300,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   },
diff --git a/docs/common-workflows/administration/migrations/migrations-in-workstation/validate-migrations.md b/docs/common-workflows/administration/migrations/migrations-in-workstation/validate-migrations.md
index 9bd4dfb45..e75b7e732 100644
--- a/docs/common-workflows/administration/migrations/migrations-in-workstation/validate-migrations.md
+++ b/docs/common-workflows/administration/migrations/migrations-in-workstation/validate-migrations.md
@@ -132,7 +132,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -157,7 +157,7 @@ Sample Response Body:
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   },
@@ -310,7 +310,7 @@ Sample Response Body:
     },
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "status": "created",
     "message": "",
@@ -335,7 +335,7 @@ Sample Response Body:
     "undoStorage": {},
     "project": {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     },
     "deleted": false
   },
diff --git a/docs/common-workflows/administration/monitors/manage-an-intelligence-server-cluster.md b/docs/common-workflows/administration/monitors/manage-an-intelligence-server-cluster.md
index dfaa012ec..7a084f5b4 100644
--- a/docs/common-workflows/administration/monitors/manage-an-intelligence-server-cluster.md
+++ b/docs/common-workflows/administration/monitors/manage-an-intelligence-server-cluster.md
@@ -69,7 +69,7 @@ This operation requires the "Monitor cluster" privilege.
       "projects": [
         {
           "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-          "name": "Strategy Tutorial",
+          "name": "MicroStrategy Tutorial",
           "status": "loaded"
         }
       ],
diff --git a/docs/common-workflows/administration/monitors/manage-caches.md b/docs/common-workflows/administration/monitors/manage-caches.md
index 4e842eeea..a158703f9 100644
--- a/docs/common-workflows/administration/monitors/manage-caches.md
+++ b/docs/common-workflows/administration/monitors/manage-caches.md
@@ -73,10 +73,10 @@ The X-MSTR-AuthToken is an authentication token which you receive during authent
   {
     "acg": 255,
     "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-    "name": "Strategy Tutorial",
+    "name": "MicroStrategy Tutorial",
     "status": 0,
     "alias": "",
-    "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+    "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
     "dateCreated": "2015-06-30T21:55:35.000+0000",
     "dateModified": "2022-06-25T12:48:15.000+0000",
     "owner": {
@@ -102,7 +102,7 @@ The X-MSTR-AuthToken is an authentication token which you receive during authent
 ]
 ```
 
-Please find the `id` for the desired project. For example, `id` of the project: “Strategy Tutorial” is `B7CA92F04B9FAE8D941C3E9B7E0CD75`. We will use it in the next step.
+Please find the `id` for the desired project. For example, `id` of the project: “MicroStrategy Tutorial” is `B7CA92F04B9FAE8D941C3E9B7E0CD75`. We will use it in the next step.
 
 ### Step 2 – Deleting the cache
 
diff --git a/docs/common-workflows/administration/monitors/monitor-and-manage-cube-caches.md b/docs/common-workflows/administration/monitors/monitor-and-manage-cube-caches.md
index ddbec4302..96a64d0b6 100644
--- a/docs/common-workflows/administration/monitors/monitor-and-manage-cube-caches.md
+++ b/docs/common-workflows/administration/monitors/monitor-and-manage-cube-caches.md
@@ -162,7 +162,7 @@ Fill in the sample below to design your own output.
       "openViewCount": 0,
       "creationTime": "2018-02-12 07:15:17",
       "historicHitCount": 121,
-      "fileName": "C:\\Program Files (x86)\\Strategy\\Intelligence Server\\Cube\\serverdefinition\\Server_tec-w-004832_PB19DEDCC11D4E0EFC000EB9495D0F44F\\363249D447A5EF245AD51AB916CA4904.cube",
+      "fileName": "C:\\Program Files (x86)\\MicroStrategy\\Intelligence Server\\Cube\\serverdefinition\\Server_tec-w-004832_PB19DEDCC11D4E0EFC000EB9495D0F44F\\363249D447A5EF245AD51AB916CA4904.cube",
       "rowCount": 39,
       "columnCount": 8
     }
@@ -290,7 +290,7 @@ Fill in the sample below to design your own output.
   "openViewCount": 0,
   "creationTime": "2018-02-12 07:15:17",
   "historicHitCount": 121,
-  "fileName": "C:\\Program Files (x86)\\Strategy\\Intelligence Server\\Cube\\serverdefinition\\Server_tec-w-004832_PB19DEDCC11D4E0EFC000EB9495D0F44F\\363249D447A5EF245AD51AB916CA4904.cube",
+  "fileName": "C:\\Program Files (x86)\\MicroStrategy\\Intelligence Server\\Cube\\serverdefinition\\Server_tec-w-004832_PB19DEDCC11D4E0EFC000EB9495D0F44F\\363249D447A5EF245AD51AB916CA4904.cube",
   "rowCount": 39,
   "columnCount": 8,
   "jobExecutionStatistics": {
@@ -385,7 +385,7 @@ Fill in the sample below to design your own output. We recommend you specify all
   "aggregatedCacheUsages": [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "currentUsage": 178000,
       "capacity": 280000 // Capacity just for project level, not for user level
     },
diff --git a/docs/common-workflows/administration/monitors/project-administration.md b/docs/common-workflows/administration/monitors/project-administration.md
index f606eb1cd..deb4bb882 100644
--- a/docs/common-workflows/administration/monitors/project-administration.md
+++ b/docs/common-workflows/administration/monitors/project-administration.md
@@ -96,7 +96,7 @@ This operation requires the "Monitor cluster" privilege.
         "projects": [
           {
             "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-            "name": "Strategy Tutorial",
+            "name": "MicroStrategy Tutorial",
             "status": "unloaded"
           },
           {
@@ -115,7 +115,7 @@ This operation requires the "Monitor cluster" privilege.
         "projects": [
           {
             "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-            "name": "Strategy Tutorial",
+            "name": "MicroStrategy Tutorial",
             "status": "loaded"
           },
           {
@@ -152,7 +152,7 @@ To apply a filter on project id and node name, you can use the filter option of
         "projects": [
           {
             "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-            "name": "Strategy Tutorial",
+            "name": "MicroStrategy Tutorial",
             "status": "unloaded"
           }
         ],
@@ -209,7 +209,7 @@ This operation requires the "Load and Unload project" and "Idle and Resume proje
   ```json
   {
     "project": {
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
       "status": "pending"
     }
@@ -278,7 +278,7 @@ This operation requires the "Load and Unload project" and "Idle and Resume proje
 
 Endpoint: [GET /api/monitors/iServer/nodes](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Monitors/getClusterNodes)
 
-In the example above, the project status of `"Strategy Tutorial"` was changed from unloaded to loaded on the cluster node named env-160560laio1use1. You can view the updated status through this API. Here, you can use the filter option on project id "B7CA92F04B9FAE8D941C3E9B7E0CD754" and/or on node name `"env-160560laio1use1"` to get information about the node.
+In the example above, the project status of `"MicroStrategy Tutorial"` was changed from unloaded to loaded on the cluster node named env-160560laio1use1. You can view the updated status through this API. Here, you can use the filter option on project id "B7CA92F04B9FAE8D941C3E9B7E0CD754" and/or on node name `"env-160560laio1use1"` to get information about the node.
 
 - Curl:
 
@@ -299,7 +299,7 @@ In the example above, the project status of `"Strategy Tutorial"` was changed fr
         "projects": [
           {
             "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-            "name": "Strategy Tutorial",
+            "name": "MicroStrategy Tutorial",
             "status": "loaded"
           }
         ],
diff --git a/docs/common-workflows/administration/server-management/manage-fences/create-fence.md b/docs/common-workflows/administration/server-management/manage-fences/create-fence.md
index bf2abe7ed..a08838256 100644
--- a/docs/common-workflows/administration/server-management/manage-fences/create-fence.md
+++ b/docs/common-workflows/administration/server-management/manage-fences/create-fence.md
@@ -65,7 +65,7 @@ The `name`, `rank` and `nodes` are mandatory fields for both types of fences. Th
   "projects": [
     {
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     }
   ]
 }
@@ -99,7 +99,7 @@ curl -X POST \
   "projects": [
     {
      "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-     "name": "Strategy Tutorial"
+     "name": "MicroStrategy Tutorial"
     }
   ]
 }'
@@ -136,7 +136,7 @@ You can view the detailed information of new created `administrator_user_fence`
   "projects": [
     {
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     }
   ],
   "id": "YWRtaW5pc3RyYXRvcl91c2VyX2ZlbmNl"
diff --git a/docs/common-workflows/administration/server-management/manage-fences/retrieve-specific-fence.md b/docs/common-workflows/administration/server-management/manage-fences/retrieve-specific-fence.md
index 9225584b1..04cab6bfe 100644
--- a/docs/common-workflows/administration/server-management/manage-fences/retrieve-specific-fence.md
+++ b/docs/common-workflows/administration/server-management/manage-fences/retrieve-specific-fence.md
@@ -70,7 +70,7 @@ You can view the detailed information of `administrator_user_fence` user fence i
   "projects": [
     {
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-      "name": "Strategy Tutorial"
+      "name": "MicroStrategy Tutorial"
     }
   ],
   "id": "YWRtaW5pc3RyYXRvcl91c2VyX2ZlbmNl"
diff --git a/docs/common-workflows/administration/server-management/manage-fences/update-specific-fence.md b/docs/common-workflows/administration/server-management/manage-fences/update-specific-fence.md
index 1809e6182..ae29304d9 100644
--- a/docs/common-workflows/administration/server-management/manage-fences/update-specific-fence.md
+++ b/docs/common-workflows/administration/server-management/manage-fences/update-specific-fence.md
@@ -118,7 +118,7 @@ You can view the detailed information of updated `administrator_user_fence` user
   "projects": [
     {
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
-      "name": "Strategy Tutorials"
+      "name": "MicroStrategy Tutorials"
     }
   ],
   "id": "YWRtaW5pc3RyYXRvcl91c2VyX2ZlbmNl"
diff --git a/docs/common-workflows/administration/server-management/manage-quick-search-indices.md b/docs/common-workflows/administration/server-management/manage-quick-search-indices.md
index c45d028a4..4274a0bc9 100644
--- a/docs/common-workflows/administration/server-management/manage-quick-search-indices.md
+++ b/docs/common-workflows/administration/server-management/manage-quick-search-indices.md
@@ -71,7 +71,7 @@ Sample Response Body:
       "machineName": "aws-amazonlinux-base-template"
     },
     {
-      "projectName": "Strategy Tutorial",
+      "projectName": "MicroStrategy Tutorial",
       "projectId": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
       "status": "completed_on",
       "percentComplete": 1.0,
diff --git a/docs/common-workflows/administration/user-management/create-security-roles.md b/docs/common-workflows/administration/user-management/create-security-roles.md
index aced91565..b65a922e7 100644
--- a/docs/common-workflows/administration/user-management/create-security-roles.md
+++ b/docs/common-workflows/administration/user-management/create-security-roles.md
@@ -500,7 +500,7 @@ Two examples are provided below. In the first example to make security role assi
         "members": []
       },
       {
-        "name": "Strategy Tutorial",
+        "name": "MicroStrategy Tutorial",
         "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
         "members": []
       }
@@ -629,7 +629,7 @@ Get information for a specific security role using the security role id. You obt
         "members": []
       },
       {
-        "name": "Strategy Tutorial",
+        "name": "MicroStrategy Tutorial",
         "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
         "members": []
       }
diff --git a/docs/common-workflows/analytics/export-to-pdf.md b/docs/common-workflows/analytics/export-to-pdf.md
index 4baae6bab..79c98beec 100644
--- a/docs/common-workflows/analytics/export-to-pdf.md
+++ b/docs/common-workflows/analytics/export-to-pdf.md
@@ -85,7 +85,7 @@ Sample Response
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 ![swagger_GET_projects](../../images/swagger_GET_projects.png)
 
@@ -116,9 +116,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "alias": "",
-      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -137,7 +137,7 @@ Sample Response
 
 Endpoint: [POST /api/documents/\{id}/instances](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Dossiers%20and%20Documents/createDocumentInstance)
 
-This endpoint allows the caller to execute a specific document in a specific project and create an instance of that document. In this example, you execute a document called "Casino Analysis" (located in Strategy Tutorial>Shared Reports>Strategy Platform Capabilities>Strategy Report Services>Visual Insight). You use the authorization token returned in step 1 as the value for `X-MSTR-AuthToken` and provide the project ID and the document ID. In this example, you leave the request body empty. The resulting HTTP response returns an HTTP status 201 and a JSON object containing the instance ID ("mid") of the document.
+This endpoint allows the caller to execute a specific document in a specific project and create an instance of that document. In this example, you execute a document called "Casino Analysis" (located in MicroStrategy Tutorial>Shared Reports>Strategy Platform Capabilities>Strategy Report Services>Visual Insight). You use the authorization token returned in step 1 as the value for `X-MSTR-AuthToken` and provide the project ID and the document ID. In this example, you leave the request body empty. The resulting HTTP response returns an HTTP status 201 and a JSON object containing the instance ID ("mid") of the document.
 
 ![swagger_POST_documents](../../images/swagger_POST_documents.png)
 
diff --git a/docs/common-workflows/analytics/filter-data/filter-dossier-instances/apply-filters-to-a-dossier.md b/docs/common-workflows/analytics/filter-data/filter-dossier-instances/apply-filters-to-a-dossier.md
index 7c61f5a3f..d13ac0701 100644
--- a/docs/common-workflows/analytics/filter-data/filter-dossier-instances/apply-filters-to-a-dossier.md
+++ b/docs/common-workflows/analytics/filter-data/filter-dossier-instances/apply-filters-to-a-dossier.md
@@ -86,7 +86,7 @@ Call `GET /api/projects` to obtain the list of available projects.
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects that the user session has access to. You use the authorization token returned during login as the value for **X-MSTR-AuthToken**. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to. The information returned for each project includes the project ID, which will be used by a later endpoint. In this example, you get the list of projects in the Strategy Tutorial metadata.
+This endpoint allows the caller to get the list of projects that the user session has access to. You use the authorization token returned during login as the value for **X-MSTR-AuthToken**. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to. The information returned for each project includes the project ID, which will be used by a later endpoint. In this example, you get the list of projects in the MicroStrategy Tutorial metadata.
 
 To execute this API, you need to provide the value for the following parameter in the request header:
 
@@ -121,9 +121,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "alias": "",
-      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -303,7 +303,7 @@ This endpoint allows the caller to execute a specific dashboard in a specific pr
 - **id** Dashboard ID generated by `GET /api/dossiers dossiers/{dossierId}/definition` or other endpoints
 - **body** Filter definition for the filter key/name generated by `GET /api/dossiers dossiers/{dossierId}/definition`
 
-In this example, you execute a dashboard called "Filters" (located in Strategy Tutorial>Shared Reports. You use the authorization token returned by `POST /api/auth/login` as the value for X-MSTR-AuthToken, a project ID returned by `GET /api/projects`, a dashboard ID returned by `GET /api/dossiers`, and a filter definition. The request body contains the definition of the existing filter that was created for the dashboard; it is applied when the dashboard is executed. The resulting HTTP response returns an HTTP status 201, indicating that the dashboard instance has been created, and a JSON object containing the instance ID ("mid") of the dashboard.
+In this example, you execute a dashboard called "Filters" (located in MicroStrategy Tutorial>Shared Reports. You use the authorization token returned by `POST /api/auth/login` as the value for X-MSTR-AuthToken, a project ID returned by `GET /api/projects`, a dashboard ID returned by `GET /api/dossiers`, and a filter definition. The request body contains the definition of the existing filter that was created for the dashboard; it is applied when the dashboard is executed. The resulting HTTP response returns an HTTP status 201, indicating that the dashboard instance has been created, and a JSON object containing the instance ID ("mid") of the dashboard.
 
 Sample Request
 
@@ -431,7 +431,7 @@ This has to be the same filter that was originally applied, but with different v
 
 :::
 
-In this example, you execute a dashboard called "Filters" (located in Strategy Tutorial>Shared Reports. You use the authorization token returned during login as the value for `X-MSTR-AuthToken` and provide the project ID, dashboard ID, dashboard instance ID, and filter definition. In the request body, you modify the values for the filter to be applied to the dashboard when it is executed. The resulting HTTP response returns an HTTP status 204.
+In this example, you execute a dashboard called "Filters" (located in MicroStrategy Tutorial>Shared Reports. You use the authorization token returned during login as the value for `X-MSTR-AuthToken` and provide the project ID, dashboard ID, dashboard instance ID, and filter definition. In the request body, you modify the values for the filter to be applied to the dashboard when it is executed. The resulting HTTP response returns an HTTP status 204.
 
 Sample Request
 
diff --git a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/create-a-cube-object.md b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/create-a-cube-object.md
index e98b5598a..b50470b44 100644
--- a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/create-a-cube-object.md
+++ b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/create-a-cube-object.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to create a new cube object through the Modeling service and publish it through Library server.
 
-You want to create a new `Year, Category Analysis` cube object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new `Year, Category Analysis` cube object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -301,7 +301,7 @@ Sample Response Code: 201 (A cube is created successfully.)
 
 <Available since="2021 Update 6" />
 
-You want to create a new `Actual vs Forecast Performance Cube` cube object under the `Public Objects` folder in the `Strategy Tutorial` project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new `Actual vs Forecast Performance Cube` cube object under the `Public Objects` folder in the `MicroStrategy Tutorial` project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 Sample Curl:
 
diff --git a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/retrieve-a-cube-definition.md b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/retrieve-a-cube-definition.md
index 5ce99778b..413a8d86d 100644
--- a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/retrieve-a-cube-definition.md
+++ b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/retrieve-a-cube-definition.md
@@ -22,7 +22,7 @@ This topic cover several workflows for retrieving a cube's definition.
 
 This workflow sample demonstrates how to retrieve the definition of a cube through the Modeling service.
 
-You want to get the definition of the `Year, Category Analysis` cube object. The object ID of the cube is `A7D792D54B58C6CB68F192A4A73E317F` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `Year, Category Analysis` cube object. The object ID of the cube is `A7D792D54B58C6CB68F192A4A73E317F` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -186,7 +186,7 @@ Response Code: 200 (The cube’s definition was returned successfully.)
 
 This workflow sample demonstrates how to retrieve the definition of a FFSQL cube through the Modeling service.
 
-You want to get the definition of the `Year, Category Analysis` cube object. The object ID of the cube is `A7D792D54B58C6CB68F192A4A73E317F` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `Year, Category Analysis` cube object. The object ID of the cube is `A7D792D54B58C6CB68F192A4A73E317F` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -1001,7 +1001,7 @@ Sample Response Code: 200 (Cube’s definition is returned successfully.)
 
 This workflow sample demonstrates how to retrieve the definition of a cube with advanced properties through the Modeling service.
 
-You want to get the definition of the Actual vs Forecast Performance Cube cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the Actual vs Forecast Performance Cube cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 This workflow is similar to [Retrieve a cube definition](#retrieve-a-cubes-definition), except with `showAdvancedProperties=true`.
 
@@ -1142,7 +1142,7 @@ Response Code: 200 (The cube definition is returned successfully.)
 
 This workflow sample demonstrates how to retrieve all the applicable properties of a cube through the Modeling service.
 
-You want to get the applicable properties of the Actual vs Forecast Performance Cube cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD75`4.
+You want to get the applicable properties of the Actual vs Forecast Performance Cube cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD75`4.
 
 Retrieve the applicable properties of a cube using [GET /api/model/cubes/\{cubeId}/applicableVldbProperties](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Cubes/ms-getCubeApplicableVldbProperties).
 
diff --git a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/update-a-cube-definition.md b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/update-a-cube-definition.md
index 6c3c39466..3d4f139a6 100644
--- a/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/update-a-cube-definition.md
+++ b/docs/common-workflows/analytics/manage-datasets/manage-cube-objects/update-a-cube-definition.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to update a cube’s definition through the Modeling service and Publish it through Library Server.
 
-You want to update the `Year, Category Analysis` cube object definition in the Strategy Tutorial project. The cube ID is `2F15C95D934175CBC9B915915D485B0E`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the `Year, Category Analysis` cube object definition in the MicroStrategy Tutorial project. The cube ID is `2F15C95D934175CBC9B915915D485B0E`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -302,7 +302,7 @@ Sample Response Code: 200 (The cube's definition is updated successfully.)
 
 <Available since="2021 Update 6" />
 
-You want to update the value of advanced properties of the `Actual vs Forecast Performance Cube` cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the `Strategy Tutorial` project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the value of advanced properties of the `Actual vs Forecast Performance Cube` cube object. The object ID of the cube is `CC02C5C24AE2803ABF14EDA5038159D4` in the `MicroStrategy Tutorial` project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 Sample Curl:
 
diff --git a/docs/common-workflows/analytics/manage-documents/retrieve-document/retrieve-the-hierarchy-of-a-document.md b/docs/common-workflows/analytics/manage-documents/retrieve-document/retrieve-the-hierarchy-of-a-document.md
index 932d9a487..120e7f21d 100644
--- a/docs/common-workflows/analytics/manage-documents/retrieve-document/retrieve-the-hierarchy-of-a-document.md
+++ b/docs/common-workflows/analytics/manage-documents/retrieve-document/retrieve-the-hierarchy-of-a-document.md
@@ -13,7 +13,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve the document definition directly using the Strategy REST API.
 
-You want to retrieve the document's definition from “Strategy Tutorial“ project. The document ID is `643209B54CC84199C48A238ACB6CB621`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to retrieve the document's definition from “MicroStrategy Tutorial“ project. The document ID is `643209B54CC84199C48A238ACB6CB621`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition-with-advanced-properties.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition-with-advanced-properties.md
index 6a1b63326..0d0b7bc03 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition-with-advanced-properties.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition-with-advanced-properties.md
@@ -8,7 +8,7 @@ description: This topic covers several workflows to retrieve the definition for
 
 This topic covers several workflows to retrieve the definition for an Incremental Refresh Report with an advanced property value.
 
-The object ID of the Incremental Refresh Report is  `B17F066940FA684A00C1D9AC5FC95754` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+The object ID of the Incremental Refresh Report is  `B17F066940FA684A00C1D9AC5FC95754` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition.md
index 640f9bc7b..eb4d47780 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-an-irr-definition.md
@@ -8,7 +8,7 @@ description: This topic covers several workflows to retrieve an Incremental Refr
 
 This topic covers several workflows to retrieve an Incremental Refresh Report definition.
 
-You want to get the definition of the `YearInList_Insert` Incremental Refresh Report object as shown in the below screenshot. The object ID of the Incremental Refresh Report is  `B5905F5C4565159A5AEAF78E71DC8BF6` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `YearInList_Insert` Incremental Refresh Report object as shown in the below screenshot. The object ID of the Incremental Refresh Report is  `B5905F5C4565159A5AEAF78E71DC8BF6` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 ![IRR Report Editor](../../../../images/IRR_report_editor.png)
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-applicable-properties-of-an-incremental-refresh-report.md b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-applicable-properties-of-an-incremental-refresh-report.md
index 30ab62f69..f29560833 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-applicable-properties-of-an-incremental-refresh-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-incremental-refresh-report/retrieve-applicable-properties-of-an-incremental-refresh-report.md
@@ -8,7 +8,7 @@ description: This workflow sample demonstrates how to retrieve applicable proper
 
 You can use REST APIs to retrieve all the applicable properties of an incremental refresh report through the Modeling service. The workflow includes the following REST APIs requests.
 
-The incremental refresh report object ID is 01234567890123456789012345678912. The incremental refresh report is in the project "Strategy Tutorial", and the project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+The incremental refresh report object ID is 01234567890123456789012345678912. The incremental refresh report is in the project "MicroStrategy Tutorial", and the project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-page-by-information.md b/docs/common-workflows/analytics/manage-reports/manage-page-by-information.md
index 8530939ab..95fd8c3dc 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-page-by-information.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-page-by-information.md
@@ -17,7 +17,7 @@ You can use REST API requests to manage page-by information for reports.
 - [Execute the report and fetch data to apply to the page-by information](#execute-the-report-and-fetch-data-to-apply-to-the-page-by-information)
 - [Update a report instance to modify the current page of page-by(s)](#update-a-report-instance-to-modify-the-current-page-of-page-bys)
 
-The workflows on this page use the Unit Sales Paged report located in the Strategy Tutorial project at **Shared Reports** > **Strategy Platform Capabilities** > **Strategy Office** > **Excel - Self-Service Report Book** > **Paged Report**.
+The workflows on this page use the Unit Sales Paged report located in the MicroStrategy Tutorial project at **Shared Reports** > **Strategy Platform Capabilities** > **Strategy Office** > **Excel - Self-Service Report Book** > **Paged Report**.
 
 ![page_by_report](../../../images/page_by_report.png)
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/create-a-new-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/create-a-new-report.md
index a1706ae6f..a385f6c8e 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/create-a-new-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/create-a-new-report.md
@@ -9,7 +9,7 @@ You can use REST APIs to create a new report through Modeling service. There are
 
 ## Create a new normal report within an instance
 
-In this sample workflow, we want to create a new normal report under the Public Objects/Report folder in the Strategy Tutorial" project. The folder object ID is `D3C7D461F69C4610AA6BAA5EF51F4125`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this sample workflow, we want to create a new normal report under the Public Objects/Report folder in the MicroStrategy Tutorial" project. The folder object ID is `D3C7D461F69C4610AA6BAA5EF51F4125`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-derived-elements-definition-in-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-derived-elements-definition-in-report.md
index d74eb0894..c3cf02b44 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-derived-elements-definition-in-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-derived-elements-definition-in-report.md
@@ -9,7 +9,7 @@ You can use REST APIs to retrieve a derived element’s definition in report thr
 
 ## Retrieve a derived element’s definition within a report instance
 
-In this sample workflow, we want to get the definition of a derived element in report. The report ID is `9B9ADA7F464E63CE0D0B709B03BD9370`. The derived element ID is `EA18C4C1484F06FF47B603A7A0DCA8D6`. The report is in the project "Strategy Tutorial", and the project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this sample workflow, we want to get the definition of a derived element in report. The report ID is `9B9ADA7F464E63CE0D0B709B03BD9370`. The derived element ID is `EA18C4C1484F06FF47B603A7A0DCA8D6`. The report is in the project "MicroStrategy Tutorial", and the project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-reports-definition.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-reports-definition.md
index 18b041ac5..14efa606b 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-reports-definition.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-a-reports-definition.md
@@ -13,7 +13,7 @@ You can use REST APIs to retrieve the definition of a report through Modeling se
   - [2. Get a report's definition within the instance](#2-get-a-reports-definition-within-the-instance)
   - [3. Delete report instance](#3-delete-report-instance)
 
-In both sample workflows, we want to retrieve a report’s definition from “Strategy Tutorial“ project. The report ID is `FFDAB82F4CA397073ABD4196FCBCD918`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In both sample workflows, we want to retrieve a report’s definition from “MicroStrategy Tutorial“ project. The report ID is `FFDAB82F4CA397073ABD4196FCBCD918`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-applicable-properties-of-a-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-applicable-properties-of-a-report.md
index aea0d12e6..763eacb17 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-applicable-properties-of-a-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/retrieve-applicable-properties-of-a-report.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to retrieve applicable proper
 
 You can use REST APIs to retrieve all the applicable properties of a report through the Modeling service. The workflow includes the following REST APIs requests.
 
-The report object ID is `E472644E4239AD7EFDBD869600C93E4D`. The report is in the project "Strategy Tutorial", and the project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+The report object ID is `E472644E4239AD7EFDBD869600C93E4D`. The report is in the project "MicroStrategy Tutorial", and the project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 ## Retrieve applicable properties of a report directly
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-report-objects/update-the-definition-of-an-existing-report.md b/docs/common-workflows/analytics/manage-reports/manage-report-objects/update-the-definition-of-an-existing-report.md
index 4b5c51a91..ec3791d58 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-report-objects/update-the-definition-of-an-existing-report.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-report-objects/update-the-definition-of-an-existing-report.md
@@ -9,7 +9,7 @@ You can use REST APIs to update an existing report object through Modeling servi
 
 ## Update the definition of an existing report
 
-In this sample workflow, we want to update an existing report object "New Normal Report" (report ID: `FB7816D149C8AC0573CC55829E56F217`) in project "Strategy Tutorial" (project ID: `B19DEDCC11D4E0EFC000EB9495D0F44F`), we have just created it in Workflow Sample: Create a New Report.
+In this sample workflow, we want to update an existing report object "New Normal Report" (report ID: `FB7816D149C8AC0573CC55829E56F217`) in project "MicroStrategy Tutorial" (project ID: `B19DEDCC11D4E0EFC000EB9495D0F44F`), we have just created it in Workflow Sample: Create a New Report.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/retrieve-transaction-report-definition.md b/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/retrieve-transaction-report-definition.md
index 52d319668..a357d6034 100644
--- a/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/retrieve-transaction-report-definition.md
+++ b/docs/common-workflows/analytics/manage-reports/manage-transaction-report-objects/retrieve-transaction-report-definition.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to retrieve a transaction rep
 
 This workflow sample demonstrates how to retrieve an existing transaction report's definition.
 
-You want to get the definition of the "Insert Sales Opportunity Action" transaction report. The object ID of the transaction report is `34D6AC79420AF8365B176480D411C3A9` in the "Strategy Tutorial" project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You also need to fetch authorization token to send correct request.
+You want to get the definition of the "Insert Sales Opportunity Action" transaction report. The object ID of the transaction report is `34D6AC79420AF8365B176480D411C3A9` in the "MicroStrategy Tutorial" project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`. You also need to fetch authorization token to send correct request.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/object-discovery/folder-browsing.md b/docs/common-workflows/analytics/object-discovery/folder-browsing.md
index 677558b8a..94a0a62fc 100644
--- a/docs/common-workflows/analytics/object-discovery/folder-browsing.md
+++ b/docs/common-workflows/analytics/object-discovery/folder-browsing.md
@@ -86,7 +86,7 @@ Sample Response
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the Strategy REST server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for the header parameter, `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for the header parameter, `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 ![swagger_GET_projects](../../../images/swagger_GET_projects.png)
 
@@ -117,9 +117,9 @@ Sample Response
   [
     {
       "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "alias": "",
-      "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+      "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
       "status": 0
     },
     {
@@ -140,7 +140,7 @@ The response body contains information for each project that is returned, includ
 
 Endpoint: [GET /api/folders/preDefined/\{folderType}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Browsing/getPreDefinedFolder)
 
-This endpoint allows the caller to get the objects under a predefined folder with the Strategy REST server. In this example, you get the objects under "Shared Reports" in the "Strategy Tutorial" project. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for `folderType` from the [EnumDSSXMLFolderNames](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLFolderNames.html) enumeration. In this example, you use the value "7" , which specifies the predefined "Shared Reports" folder under the "Public Objects" folder. If the call is successful, the resulting HTTP response returns an HTTP status 200 and a list of metadata objects under the "Shared Reports" folder.
+This endpoint allows the caller to get the objects under a predefined folder with the Strategy REST server. In this example, you get the objects under "Shared Reports" in the "MicroStrategy Tutorial" project. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for `folderType` from the [EnumDSSXMLFolderNames](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLFolderNames.html) enumeration. In this example, you use the value "7" , which specifies the predefined "Shared Reports" folder under the "Public Objects" folder. If the call is successful, the resulting HTTP response returns an HTTP status 200 and a list of metadata objects under the "Shared Reports" folder.
 
 ![swagger_GET_folders_preDefined](../../../images/swagger_GET_folders_preDefined.png)
 
@@ -273,7 +273,7 @@ Sample Response
 
 Endpoint: [GET /api/folders/preDefined?folderType=\{folderType}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Browsing/getPreDefinedFolders)
 
-This endpoint allows the caller to get the folder object of one or more predefined folders with the Strategy REST server. In this example, you get the "Shared Reports" and "My Reports" folder objects in the "Strategy Tutorial" project. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for `folderType` from the [EnumDSSXMLFolderNames](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLFolderNames.html) enumeration. You may specify multiple folder types as a comma separated list. In this example, you use the value "7,20", where "7" specifies the predefined "Shared Reports" folder under the "Public Objects" folder, and "20" specifies the "My Reports" folder under the profile folder of the active user. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the folder objects requested.
+This endpoint allows the caller to get the folder object of one or more predefined folders with the Strategy REST server. In this example, you get the "Shared Reports" and "My Reports" folder objects in the "MicroStrategy Tutorial" project. You use the authorization token returned by `POST /api/auth/login` as the value for `X-MSTR-AuthToken` and a project ID returned by `GET /api/projects` as the value for `X-MSTR-ProjectID`. You provide a value for `folderType` from the [EnumDSSXMLFolderNames](https://www2.microstrategy.com/producthelp/2021/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLFolderNames.html) enumeration. You may specify multiple folder types as a comma separated list. In this example, you use the value "7,20", where "7" specifies the predefined "Shared Reports" folder under the "Public Objects" folder, and "20" specifies the "My Reports" folder under the profile folder of the active user. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a list of the folder objects requested.
 
 Sample Request
 
diff --git a/docs/common-workflows/analytics/object-discovery/search-for-objects.md b/docs/common-workflows/analytics/object-discovery/search-for-objects.md
index 0d6c3b01c..e566c775d 100644
--- a/docs/common-workflows/analytics/object-discovery/search-for-objects.md
+++ b/docs/common-workflows/analytics/object-discovery/search-for-objects.md
@@ -87,7 +87,7 @@ The authorization token "`x-mstr-authtoken`" is returned in the response header.
 
 Endpoint: [GET /api/projects](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Projects/getProjects_1)
 
-This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the Strategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
+This endpoint allows the caller to get the list of projects with the Strategy REST Server. In this example, you get the list of projects in the MicroStrategy Tutorial metadata. You use the authorization token returned during login as the value for `X-MSTR-AuthToken`. If the call is successful, the resulting HTTP response returns an HTTP status code 200 and a response body containing a list of the active projects that the user session has access to.
 
 ![swagger_GET_projects](../../../images/swagger_GET_projects.png)
 
@@ -118,9 +118,9 @@ Sample Response
        [
          {
            "id": "nllmm5lpmkjdsj4d4etgdikc6c",
-           "name": "Strategy Tutorial",
+           "name": "MicroStrategy Tutorial",
            "alias": "",
-           "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+           "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
            "status": 0
          },
          {
@@ -141,7 +141,7 @@ The response body contains information for each project that is returned, includ
 
 Endpoint: [GET /api/searches/results](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Browsing/doQuickSearch)
 
-This endpoint allows the caller to perform a quick search for specific objects. In this example, you search in the "Strategy Tutorial" project for reports that include "Customer" in the title and then return all results without pagination. You use two different types of parameters—header and query.
+This endpoint allows the caller to perform a quick search for specific objects. In this example, you search in the "MicroStrategy Tutorial" project for reports that include "Customer" in the title and then return all results without pagination. You use two different types of parameters—header and query.
 
 - You identify the project by passing the project ID in the request header.
 - You set the following values using query parameters in the request:
diff --git a/docs/common-workflows/analytics/project-management/manage-project-load-settings-on-server-startup.md b/docs/common-workflows/analytics/project-management/manage-project-load-settings-on-server-startup.md
index 1c4771830..581fa28d9 100644
--- a/docs/common-workflows/analytics/project-management/manage-project-load-settings-on-server-startup.md
+++ b/docs/common-workflows/analytics/project-management/manage-project-load-settings-on-server-startup.md
@@ -114,7 +114,7 @@ This is the response of a clustered Intelligence Server, and thus, contains many
 {
   "projects": {
     "B7CA92F04B9FAE8D941C3E9B7E0CD754": {
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
       "nodes": ["env-220285laio2use1"]
     },
@@ -207,7 +207,7 @@ Response Body:
 {
   "projects": {
     "B7CA92F04B9FAE8D941C3E9B7E0CD754": {
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "id": "B7CA92F04B9FAE8D941C3E9B7E0CD754",
       "nodes": ["env-220285laio2use1", "env-220285laio1use1"]
     },
diff --git a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-applicable-advanced-properties.md b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-applicable-advanced-properties.md
index eabb2c40f..a80b6ee0b 100644
--- a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-applicable-advanced-properties.md
+++ b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-applicable-advanced-properties.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve the applicable properties of a project through Modeling Service.
 
-You want to get the applicable properties of the `Strategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
+You want to get the applicable properties of the `MicroStrategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
 
 :::info
 
diff --git a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-with-advanced-properties.md b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-with-advanced-properties.md
index d8e1b8b02..ab356ae50 100644
--- a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-with-advanced-properties.md
+++ b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/get-project-with-advanced-properties.md
@@ -15,7 +15,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve project's definition and its advanced properties.
 
-You want to get the advanced properties of the `Strategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
+You want to get the advanced properties of the `MicroStrategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
 
 :::info
 
@@ -60,8 +60,8 @@ You can view project's definition and its advanced properties in the response.
     "primaryLocale": "en-US",
     "objectId": "6851110C470AF40EB46B559D5098F309",
     "subType": "project",
-    "name": "Strategy Tutorial",
-    "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
+    "name": "MicroStrategy Tutorial",
+    "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
   },
   "advancedProperties": {
     "vldbProperties": {
diff --git a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/update-project-advanced-property.md b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/update-project-advanced-property.md
index a02ced495..d7c834252 100644
--- a/docs/common-workflows/analytics/project-management/project-advanced-properties-management/update-project-advanced-property.md
+++ b/docs/common-workflows/analytics/project-management/project-advanced-properties-management/update-project-advanced-property.md
@@ -17,7 +17,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to update project's advanced property value
 
-You want to get update an advanced property of the `Strategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
+You want to get update an advanced property of the `MicroStrategy Tutorial` Project object. The object ID is `6851110C470AF40EB46B559D5098F309`.
 
 :::info
 
@@ -74,8 +74,8 @@ You can view list of advanced properties including updated property in the respo
     "primaryLocale": "en-US",
     "objectId": "6851110C470AF40EB46B559D5098F309",
     "subType": "project",
-    "name": "Strategy Tutorial",
-    "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
+    "name": "MicroStrategy Tutorial",
+    "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
   },
   "advancedProperties": {
     "vldbProperties": {
@@ -155,8 +155,8 @@ You can view list of advanced properties including updated property in the respo
     "primaryLocale": "en-US",
     "objectId": "6851110C470AF40EB46B559D5098F309",
     "subType": "project",
-    "name": "Strategy Tutorial",
-    "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
+    "name": "MicroStrategy Tutorial",
+    "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed."
   },
   "advancedProperties": {
     "vldbProperties": {
diff --git a/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/workflow-retrieve-data-from-the-intelligence-server.md b/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/workflow-retrieve-data-from-the-intelligence-server.md
index 90f4aa0b6..02c144d9a 100644
--- a/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/workflow-retrieve-data-from-the-intelligence-server.md
+++ b/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/workflow-retrieve-data-from-the-intelligence-server.md
@@ -111,7 +111,7 @@ This endpoint returns the definition for a specific report in a specific project
 - Identify the project by passing the project ID in the request header.
 - Identify the report by passing the report ID in the path of the request.
 
-In the sample provided, you get the definition for the report “01 Basic Report” in the “Strategy Tutorial” project. This report has two attributes and three metrics.
+In the sample provided, you get the definition for the report “01 Basic Report” in the “MicroStrategy Tutorial” project. This report has two attributes and three metrics.
 
 ![GET_report_definition](../../../images/GET_report_definition.png)
 
@@ -222,7 +222,7 @@ This endpoint returns the definition for a specific cube in a specific project f
 - Identify the project by passing the project ID in the request header.
 - Identify the cube by passing the cube ID in the path of the request.
 
-In the sample provided, you get the definition for the cube “Advanced sort" in the “Strategy Tutorial” project. This cube has two attributes and two metrics.
+In the sample provided, you get the definition for the cube “Advanced sort" in the “MicroStrategy Tutorial” project. This cube has two attributes and two metrics.
 
 ![GET_cube_definition](../../../images/GET_cube_definition.png)
 
@@ -316,7 +316,7 @@ This endpoint returns the hierarchy for a specific dashboard in a specific proje
 - Identify the project by passing the project ID in the request header.
 - Identify the dashboard by passing the dashboard ID in the path of the request.
 
-In the sample provided, you get the hierarchy for the dashboard “Dossier of Advanced sort" in the “Strategy Tutorial” project. This dashboard has one chapter, one page, and one visualization.
+In the sample provided, you get the hierarchy for the dashboard “Dossier of Advanced sort" in the “MicroStrategy Tutorial” project. This dashboard has one chapter, one page, and one visualization.
 
 ![GET_dossier_hierarchy](../../../images/GET_dossier_hierarchy.png)
 
@@ -401,7 +401,7 @@ This endpoint creates a new instance of a specific report in a specific project
 
 :::tip
 
-In the sample that was provided, you create an instance of the report “01 Basic Report” in the “Strategy Tutorial” project. This report has two attributes and three metrics.
+In the sample that was provided, you create an instance of the report “01 Basic Report” in the “MicroStrategy Tutorial” project. This report has two attributes and three metrics.
 
 :::
 
@@ -666,7 +666,7 @@ This endpoint creates a new instance of a specific cube in a specific project on
 - Identify the project by passing the project ID in the request header.
 - Identify the cube by passing the cube ID in the path of the request.
 
-  In sample that was provided, you create an instance of the cube “Advanced Sort” in the “Strategy Tutorial” project. This cube has two attributes and two metrics.
+  In sample that was provided, you create an instance of the cube “Advanced Sort” in the “MicroStrategy Tutorial” project. This cube has two attributes and two metrics.
 
 - Identity the start and end position as offset and limit request parameters
 
@@ -861,7 +861,7 @@ Endpoint: [POST /api/dossiers/\{dossierId}/instances](https://demo.microstrategy
 
 This endpoint allows the caller to create a new instance of a specific dashboard in a specific project from the Strategy Intelligence Server. The request body contains linking and bookmark information for the dashboard. The body of the response contains the instance ID for the dashboard and the status.
 
-In the sample that was provided, you create an instance of the dashboard “Dossier for Advanced sort” in the “Strategy Tutorial” project. This dashboard has two attributes and two metrics.
+In the sample that was provided, you create an instance of the dashboard “Dossier for Advanced sort” in the “MicroStrategy Tutorial” project. This dashboard has two attributes and two metrics.
 
 ![POST_dossier_instance](../../../images/POST_dossier_instance.png)
 
@@ -911,7 +911,7 @@ This endpoint gets the data for a specific report instance in a specific project
 - Identify the project by passing the project ID in the request header.
 - Identify the report instance by passing the report ID and the report instance ID in the path of the request.
 
-  In the downloadable sample that was provided, you get the data for an instance of the report “01 Basic Report” in the “Strategy Tutorial” project. This report has two attributes and three metrics.
+  In the downloadable sample that was provided, you get the data for an instance of the report “01 Basic Report” in the “MicroStrategy Tutorial” project. This report has two attributes and three metrics.
 
 - Identity the start and end position as offset and limit request parameters
   - offset is the start point of your response. For example, if offset=2, it will return the report data beginning with the second record. The default value is 0.
@@ -1048,7 +1048,7 @@ Endpoint: [GET /api/cubes/\{cubeId}/instances/\{instanceId}](https://demo.micros
 This endpoint gets the data for a specific cube instance in a specific project from the Strategy Intelligence Server. The response body contains the cube data; the results are determined by the conditions you applied when you created the instance. You can refine the amount of data that is returned using offset and limit parameters in the request.
 
 - Identify the project by passing the project ID in the request header.
-- Identify the cube instance by passing the cube ID and the cube instance ID in the path of the request. In the sample that was provided, you get the data for an instance of the cube “Advanced sort” in the “Strategy Tutorial” project. This cube has two attributes and two metrics.
+- Identify the cube instance by passing the cube ID and the cube instance ID in the path of the request. In the sample that was provided, you get the data for an instance of the cube “Advanced sort” in the “MicroStrategy Tutorial” project. This cube has two attributes and two metrics.
 
 - Identity the start and end position as offset and limit request parameters
   - offset is the start point of your response. For example, if offset=2, it will return the cube data beginning with the second record. The default value is 0.
@@ -1239,7 +1239,7 @@ This endpoint gets dashboard data by visualization for a specific dashboard inst
 - Identify the dashboard instance by passing the dashboard ID and the dashboard instance ID in the path of the request.
 - Identify the chapter and visualization by passing the chapter key and visualization key in the path of the request.
 
-  In the sample that was provided, you get the data for a visualization in an instance of the dashboard “Year Cost” in the “Strategy Tutorial” project.
+  In the sample that was provided, you get the data for a visualization in an instance of the dashboard “Year Cost” in the “MicroStrategy Tutorial” project.
 
 - Identity the start and end position as offset and limit request parameters
   - offset is the start point of your response. For example, if offset=2, it will return the report data beginning with the second record. The default value is 0.
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-dataset-sql.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-dataset-sql.md
index 3ba3645e6..eb09b8e2a 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-dataset-sql.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-dataset-sql.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 You can retrieve the SQL statements of all datasets in a document or dashboard instance. In this workflow sample, a dashboard instance is used. However, the same workflow applies to a document instance.
 
-You want to view the SQL statement of every dataset in the Cost Analysis Dashboard in the Strategy Tutorial project. The object ID of the dashboard is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to view the SQL statement of every dataset in the Cost Analysis Dashboard in the MicroStrategy Tutorial project. The object ID of the dashboard is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-grid-or-graph-query-details.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-grid-or-graph-query-details.md
index 450a45eed..ca263b190 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-grid-or-graph-query-details.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-grid-or-graph-query-details.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve the query details of grids and graphs in a document instance.
 
-You want to view query details of grids and graphs in the Cost Analysis Document in the Strategy Tutorial project. The object ID of the document is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to view query details of grids and graphs in the Cost Analysis Document in the MicroStrategy Tutorial project. The object ID of the document is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-report-or-card-sql.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-report-or-card-sql.md
index 2288ba81d..ba6764ba7 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-report-or-card-sql.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-report-or-card-sql.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 You can retrieve a report or card instance’s SQL statement. In this workflow sample, a document with a report object is used. However, the same workflow applies to card objects.
 
-You want to get the definition of the SQL statement from the Cost Analysis Report in the Strategy Tutorial project. The object ID of the report is `CA8E4E2C6F4AC30B0DDE2195998B82DC`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the SQL statement from the Cost Analysis Report in the MicroStrategy Tutorial project. The object ID of the report is `CA8E4E2C6F4AC30B0DDE2195998B82DC`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-visualization-query-details.md b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-visualization-query-details.md
index 0b1d70854..dc9a37c54 100644
--- a/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-visualization-query-details.md
+++ b/docs/common-workflows/analytics/retrieve-sql-statements-and-query-details/retrieve-visualization-query-details.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve the query details of visualizations in a dashboard instance.
 
-You want to view the query details of visualizations in the Cost Analysis Dashboard in the Strategy Tutorial project. The object ID of the dashboard is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to view the query details of visualizations in the Cost Analysis Dashboard in the MicroStrategy Tutorial project. The object ID of the dashboard is `D14F30994A4B97AD8EF6AEA5F589E30B`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/common-object-management/change-ownership.md b/docs/common-workflows/modeling/common-object-management/change-ownership.md
index c3d61b6d4..85bb19c45 100644
--- a/docs/common-workflows/modeling/common-object-management/change-ownership.md
+++ b/docs/common-workflows/modeling/common-object-management/change-ownership.md
@@ -233,7 +233,7 @@ You can view the updated owner and access rights information in the body of the
   "viewMedia": 1879072805,
   "ancestors": [
     {
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 3
     },
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-acl.md b/docs/common-workflows/modeling/common-object-management/manage-object-acl.md
index 5a7a97d7a..a3e7a60b3 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-acl.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-acl.md
@@ -166,7 +166,7 @@ Response Body:
   "extType": 0,
   "ancestors": [
     {
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 2
     },
@@ -266,7 +266,7 @@ Response Body:
   "extType": 0,
   "ancestors": [
     {
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 3
     },
@@ -465,7 +465,7 @@ Response Body:
   "extType": 0,
   "ancestors": [
     {
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 2
     },
@@ -564,7 +564,7 @@ Response Body:
   "extType": 0,
   "ancestors": [
     {
-      "name": "Strategy Tutorial",
+      "name": "MicroStrategy Tutorial",
       "id": "D43364C684E34A5F9B2F9AD7108F7828",
       "level": 3
     },
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-translations/remove-add-object-translations.md b/docs/common-workflows/modeling/common-object-management/manage-object-translations/remove-add-object-translations.md
index a887954c0..82435061d 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-translations/remove-add-object-translations.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-translations/remove-add-object-translations.md
@@ -42,7 +42,7 @@ All params, but the request body are common for both 'add' and 'replace' operati
 
 In this demo following parameter values will be used:
 
-- Project: Strategy Tutorial
+- Project: MicroStrategy Tutorial
 - Project ID: `B7CA92F04B9FAE8D941C3E9B7E0CD754`
 - Object ID: `BEC722A6406320A3E67DBFBAB2F033CB`
 - Object type: `report_definition`
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-translations/retrieve-object-translations.md b/docs/common-workflows/modeling/common-object-management/manage-object-translations/retrieve-object-translations.md
index b35389236..b1c41afaa 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-translations/retrieve-object-translations.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-translations/retrieve-object-translations.md
@@ -25,7 +25,7 @@ Prepare necessary info in order to perform GET operation
 
 In this demo following parameter values will be used:
 
-- Project: Strategy Tutorial
+- Project: MicroStrategy Tutorial
 - Project ID: `B7CA92F04B9FAE8D941C3E9B7E0CD754`
 - Object ID: `BEC722A6406320A3E67DBFBAB2F033CB`
 - Object type: `report_definition`
diff --git a/docs/common-workflows/modeling/common-object-management/manage-object-translations/update-object-translations.md b/docs/common-workflows/modeling/common-object-management/manage-object-translations/update-object-translations.md
index 6e98418b1..65ce6618d 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-object-translations/update-object-translations.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-object-translations/update-object-translations.md
@@ -36,7 +36,7 @@ Prepare necessary info in order to perform PATCH operation
 
 In this demo, the following parameter values will be used:
 
-- Project: Strategy Tutorial
+- Project: MicroStrategy Tutorial
 - Project ID: `B7CA92F04B9FAE8D941C3E9B7E0CD754`
 - Object ID: `BEC722A6406320A3E67DBFBAB2F033CB`
 - Object type: `report_definition`
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/lock-the-schema.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/lock-the-schema.md
index 40af2ad53..e0f18467d 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/lock-the-schema.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/lock-the-schema.md
@@ -15,7 +15,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to lock the schema.
 
-You want to lock the schema in the Strategy Tutorial project with an `“absolute_individual“` lock. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to lock the schema in the MicroStrategy Tutorial project with an `“absolute_individual“` lock. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-asynchronously.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-asynchronously.md
index 7cb7e733d..af1c02090 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-asynchronously.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-asynchronously.md
@@ -18,7 +18,7 @@ This workflow sample demonstrates how to reload (update) the schema asynchronous
 1. [Reload (update) the schema asynchronously.](#reload-update-the-schema-asynchronously)
 1. [Check the status of the schema reload (update).](#check-the-status-of-the-schema-reload-update)
 
-You want to reload (update) the schema asynchronously in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to reload (update) the schema asynchronously in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 Get the authorization token needed to execute the request with [POST /api/auth/login](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin).
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-synchronously.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-synchronously.md
index 5d571226c..40fe355c1 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-synchronously.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/reload-the-schema-synchronously.md
@@ -15,7 +15,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to reload (update) the schema synchronously.
 
-You want to reload (update) the schema synchronously in the Strategy Tutorial project . The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to reload (update) the schema synchronously in the MicroStrategy Tutorial project . The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/retrieve-the-schema-lock.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/retrieve-the-schema-lock.md
index 2f7e32712..aaca10fda 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/retrieve-the-schema-lock.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/retrieve-the-schema-lock.md
@@ -7,7 +7,7 @@ description: This workflow sample demonstrates how to retrieve the schema lock.
 
 This workflow sample demonstrates how to retrieve the schema lock.
 
-You want to get the schema lock status of the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the schema lock status of the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/common-object-management/manage-the-schema/unlock-the-schema.md b/docs/common-workflows/modeling/common-object-management/manage-the-schema/unlock-the-schema.md
index bfd8d13ea..671cfda9d 100644
--- a/docs/common-workflows/modeling/common-object-management/manage-the-schema/unlock-the-schema.md
+++ b/docs/common-workflows/modeling/common-object-management/manage-the-schema/unlock-the-schema.md
@@ -15,7 +15,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to unlock the schema.
 
-You want to unlock the schema in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to unlock the schema in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/create-an-attribute-object.md b/docs/common-workflows/modeling/manage-attribute-objects/create-an-attribute-object.md
index eb859af4e..9ea36b710 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/create-an-attribute-object.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/create-an-attribute-object.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to create an attribute object through the Modeling service.
 
-You want to create a "Subcategory" attribute object under the Public Objects folder in the Strategy Tutorial project. The folder object ID of the attribute is `98FE182C2A10427EACE0CD30B6768258` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a "Subcategory" attribute object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID of the attribute is `98FE182C2A10427EACE0CD30B6768258` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition-within-a-changeset.md
index 0a1a7cb82..94f6cad4a 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition-within-a-changeset.md
@@ -22,7 +22,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 :::
 
-You want to get the definition of the "Subcategory" attribute object. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Subcategory" attribute object. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition.md b/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition.md
index 46eb26d31..7e8c28adc 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/retrieve-an-attributes-definition.md
@@ -18,7 +18,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve the definition of an attribute through the Modeling service.
 
-You want to get the definition of the `"Subcategory"` attribute object. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Subcategory"` attribute object. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -211,7 +211,7 @@ Response Code: 200 (The attribute's definition was returned successfully.)
 
 ## Retrieve an attribute's definition with expressions in tree and tokens formats
 
-In this workflow sample, you want to get the definition of the "`Subcategory`“ attribute object, with the expression returned in tree and tokens formats. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to get the definition of the "`Subcategory`“ attribute object, with the expression returned in tree and tokens formats. The object ID of the attribute is `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-attribute-objects/update-an-attributes-definition.md b/docs/common-workflows/modeling/manage-attribute-objects/update-an-attributes-definition.md
index ce66dd71e..6a7e204ab 100644
--- a/docs/common-workflows/modeling/manage-attribute-objects/update-an-attributes-definition.md
+++ b/docs/common-workflows/modeling/manage-attribute-objects/update-an-attributes-definition.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to update an attribute's definition through the Modeling service.
 
-You want to update the definition of the "Customer" attribute object under the Public Objects folder in the Strategy Tutorial project. The attribute object ID is `5D6C76C3A3F548A0B9ADE5F9D2AA65C6` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the definition of the "Customer" attribute object under the Public Objects folder in the MicroStrategy Tutorial project. The attribute object ID is `5D6C76C3A3F548A0B9ADE5F9D2AA65C6` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -36,7 +36,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 Use [PATCH /api/model/attributes/\{attributeId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Attributes/ms-updateAttribute).
 
-You want to update the definition of the "Customer" attribute object under the Public Objects folder in the Strategy Tutorial project by ungrouping the "Name" form group and adding a new form group "Email". The attribute object ID is `5D6C76C3A3F548A0B9ADE5F9D2AA65C6` in the Strategy Tutorial project.
+You want to update the definition of the "Customer" attribute object under the Public Objects folder in the MicroStrategy Tutorial project by ungrouping the "Name" form group and adding a new form group "Email". The attribute object ID is `5D6C76C3A3F548A0B9ADE5F9D2AA65C6` in the MicroStrategy Tutorial project.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships-within-a-changeset.md b/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships-within-a-changeset.md
index 36c3d0905..d9a353e38 100644
--- a/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships-within-a-changeset.md
@@ -26,7 +26,7 @@ Changesets are used in this workflow. For information on how to create and use c
 1. [Get an attribute's relationships within a changeset.](#get-an-attributes-relationships-within-a-changeset)
 1. Delete the changeset.
 
-You want to get the relationships of the `"Month"` attribute object. The object ID of the attribute is `8D679D4411D3E4981000E787EC6DE8A4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the relationships of the `"Month"` attribute object. The object ID of the attribute is `8D679D4411D3E4981000E787EC6DE8A4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -40,7 +40,7 @@ Get the project ID from [GET /api/projects](https://demo.microstrategy.com/Micro
 
 Use [GET /api/model/systemHierarchy/attributes/\{attributeId}/relationships]([https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System) Hierarchy/ms-getAttributeRelationships).
 
-You want to get the relationship of the `"Month"` attribute object. The object ID of the attribute is `8D679D4411D3E4981000E787EC6DE8A4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the relationship of the `"Month"` attribute object. The object ID of the attribute is `8D679D4411D3E4981000E787EC6DE8A4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 Sample Request Header:
 
diff --git a/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships.md b/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships.md
index bc061526b..4bded4146 100644
--- a/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships.md
+++ b/docs/common-workflows/modeling/manage-attribute-relationships/retrieve-an-attributes-relationships.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve the relationships related to an attribute through the Modeling service.
 
-You want to get the relationships of the "Month" attribute object. The object ID of the attribute is 8D679D4411D3E4981000E787EC6DE8A4 in the Strategy Tutorial project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+You want to get the relationships of the "Month" attribute object. The object ID of the attribute is 8D679D4411D3E4981000E787EC6DE8A4 in the MicroStrategy Tutorial project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-attribute-relationships/update-an-attributes-relationships.md b/docs/common-workflows/modeling/manage-attribute-relationships/update-an-attributes-relationships.md
index c471a3b95..c2c14d961 100644
--- a/docs/common-workflows/modeling/manage-attribute-relationships/update-an-attributes-relationships.md
+++ b/docs/common-workflows/modeling/manage-attribute-relationships/update-an-attributes-relationships.md
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to update an attribute's relationship thro
 1. Commit the changeset.
 1. Delete the changeset.
 
-You want to update the relationship for the `“Subcategory“` attribute object with ID `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the relationship for the `“Subcategory“` attribute object with ID `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -41,7 +41,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 Use [PUT /api/model/systemHierarchy/attributes/\{attributeId}/relationships](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/System%20Hierarchy/ms-putAttributeRelationships).
 
-You want to update the relationship of the "Subcategory" attribute object by adding relationships between "Category" and "Subcategory", and "Subcategory" and "Item". The object ID of the "Subcategory" attribute is `E8C034036E4EE6404513A6B12FAE9481` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the relationship of the "Subcategory" attribute object by adding relationships between "Category" and "Subcategory", and "Subcategory" and "Item". The object ID of the "Subcategory" attribute is `E8C034036E4EE6404513A6B12FAE9481` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 The following screenshot shows how these relationships are shown in the editor.
 
diff --git a/docs/common-workflows/modeling/manage-base-formula-objects/create-a-base-formulas-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-base-formula-objects/create-a-base-formulas-definition-within-a-changeset.md
index c4c2c847f..7cf661fa8 100644
--- a/docs/common-workflows/modeling/manage-base-formula-objects/create-a-base-formulas-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-base-formula-objects/create-a-base-formulas-definition-within-a-changeset.md
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 :::
 
-You want to create a new base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The destination folder ID is `31727EF14E35DAA437B716BA56466585`  in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The destination folder ID is `31727EF14E35DAA437B716BA56466585`  in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition-within-a-changeset.md
index 276c1beaf..86cb9f514 100644
--- a/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition-within-a-changeset.md
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 ::::
 
-You want to get the definition of the `"Cost"` related base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The object ID of the base formula is `594A680CB5894B25BD3AE8BB47AAF424`  in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Cost"` related base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The object ID of the base formula is `594A680CB5894B25BD3AE8BB47AAF424`  in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 For different formats of base formula expressions, please refer to [Retrieve a base formula's definition](retrieve-a-base-formulas-definition.md).
 
diff --git a/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition.md b/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition.md
index bd480d314..92d8daf66 100644
--- a/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition.md
+++ b/docs/common-workflows/modeling/manage-base-formula-objects/retrieve-a-base-formulas-definition.md
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 :::
 
-You want to get the definition of the `"Cost"` related base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The object ID of the base formula is `594A680CB5894B25BD3AE8BB47AAF424`  in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Cost"` related base formula object, which is defined as `”Sum(Cost)”` and named as `“base_sum(Cost)“`. The object ID of the base formula is `594A680CB5894B25BD3AE8BB47AAF424`  in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-consolidation-objects/create-a-consolidation-object.md b/docs/common-workflows/modeling/manage-consolidation-objects/create-a-consolidation-object.md
index 967e5a981..5aa8589d3 100644
--- a/docs/common-workflows/modeling/manage-consolidation-objects/create-a-consolidation-object.md
+++ b/docs/common-workflows/modeling/manage-consolidation-objects/create-a-consolidation-object.md
@@ -23,7 +23,7 @@ This workflow sample demonstrates how to create a new consolidation object throu
 
 [More Example: Create a consolidation with two elements.](#example-create-a-consolidation-with-two-elements)
 
-You want to create a new consolidation with the expression "(\{Customer Age=20 AND Customer=Aaby:Alen} + \{Customer City=Addison})" under the Public Objects folder in the Strategy Tutorial project. The folder object ID is 98FE182C2A10427EACE0CD30B6768258. The project ID is 091B51154B22036C53CFBB9958B2E8FC.
+You want to create a new consolidation with the expression "(\{Customer Age=20 AND Customer=Aaby:Alen} + \{Customer City=Addison})" under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is 98FE182C2A10427EACE0CD30B6768258. The project ID is 091B51154B22036C53CFBB9958B2E8FC.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-consolidation-objects/retrieve-a-consolidations-definition.md b/docs/common-workflows/modeling/manage-consolidation-objects/retrieve-a-consolidations-definition.md
index 48627a95d..a45cdf3b9 100644
--- a/docs/common-workflows/modeling/manage-consolidation-objects/retrieve-a-consolidations-definition.md
+++ b/docs/common-workflows/modeling/manage-consolidation-objects/retrieve-a-consolidations-definition.md
@@ -21,7 +21,7 @@ You can use REST APIs to retrieve the definition for a consolidation through the
 
 ## Retrieve a consolidation's definition
 
-You want to get the definition of a consolidation object. The object ID of the consolidation is B9E7FD5911D3E936C000B3B2D86C964F in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of a consolidation object. The object ID of the consolidation is B9E7FD5911D3E936C000B3B2D86C964F in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -461,7 +461,7 @@ Response Code: 200 (The consolidation's definition is returned successfully.)
 
 ## Retrieve a consolidation's definition within a changeset
 
-You want the definition of the consolidation object "Customer Geography". The object ID of the consolidation is B9E7FD5911D3E936C000B3B2D86C964F in the Strategy Tutorial project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+You want the definition of the consolidation object "Customer Geography". The object ID of the consolidation is B9E7FD5911D3E936C000B3B2D86C964F in the MicroStrategy Tutorial project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-consolidation-objects/update-a-consolidation-object.md b/docs/common-workflows/modeling/manage-consolidation-objects/update-a-consolidation-object.md
index bc5143295..163bfb36a 100644
--- a/docs/common-workflows/modeling/manage-consolidation-objects/update-a-consolidation-object.md
+++ b/docs/common-workflows/modeling/manage-consolidation-objects/update-a-consolidation-object.md
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to replace an existing consolidation objec
 1. Commit the changeset.
 1. Delete the changeset.
 
-You want to replace the existing consolidation object Customer Geography in the Strategy Tutorial project. The consolidation object ID is `B9E7FD5911D3E936C000B3B2D86C964F`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to replace the existing consolidation object Customer Geography in the MicroStrategy Tutorial project. The consolidation object ID is `B9E7FD5911D3E936C000B3B2D86C964F`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object-with-filter-elements-using-custom-expressions.md b/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object-with-filter-elements-using-custom-expressions.md
index 3958d587a..1e30818a7 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object-with-filter-elements-using-custom-expressions.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object-with-filter-elements-using-custom-expressions.md
@@ -21,7 +21,7 @@ You want to create a new `"Last 10 year"` custom group object with 2 filter elem
 - last 5 year: "(Year(CurrentDate()) - 5)\<= Year@ID"
 - last 10-5 years: "((Year(CurrentDate()) - 10)\<= Year@ID)AND((Year(CurrentDate()) - 5)>Year@ID)"
 
-You want to save the object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to save the object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object.md b/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object.md
index 5db443c11..47e04a616 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/create-a-custom-group-object.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to create a new custom group object through the Modeling service.
 
-You want to create a new `“Age Group“` custom group object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new `“Age Group“` custom group object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition-within-a-changeset.md
index df3da9d0a..464dacf47 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition-within-a-changeset.md
@@ -18,7 +18,7 @@ This workflow sample demonstrates how to retrieve a custom group’s definition
 
 Changesets are used in this workflow. For information on how to create and use changesets, see [Changesets](/docs/common-workflows/modeling/changesets.md). If you plan to use the response of `GET /api/model/customGroups/{customGroupsId}` to create a new custom group or update the custom group's definition, it is recommended to associate all requests to one changeset.
 
-You want to get the definition of the `"Age Group"` custom group object. The object ID of the custom group is `085CBF314703A71E926EA187C2002969` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Age Group"` custom group object. The object ID of the custom group is `085CBF314703A71E926EA187C2002969` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition.md b/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition.md
index baa2dbab3..46c215685 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/retrieve-a-custom-groups-definition.md
@@ -20,7 +20,7 @@ This topic covers three workflows for retrieving a custom group’s definition.
 
 This workflow sample demonstrates how to retrieve the definition of a custom group with filter elements through the Modeling service.
 
-You want to get the definition of the `"Age Group"` custom group object. The object ID of the custom group is `085CBF314703A71E926EA187C2002969` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Age Group"` custom group object. The object ID of the custom group is `085CBF314703A71E926EA187C2002969` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -276,7 +276,7 @@ Response Code: 200 (The custom group's definition was returned successfully.)
 
 This workflow sample demonstrates how to retrieve the definition of a custom group with a banding element through the Modeling service.
 
-You want to get the definition of the `"Customers Value Banding"` custom group object. The object ID of the custom group is `F519146F4B0A6EC81ED3CFA30F1C90B4` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Customers Value Banding"` custom group object. The object ID of the custom group is `F519146F4B0A6EC81ED3CFA30F1C90B4` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-custom-group-objects/update-a-custom-groups-definition.md b/docs/common-workflows/modeling/manage-custom-group-objects/update-a-custom-groups-definition.md
index 3a33f7560..bb544cf27 100644
--- a/docs/common-workflows/modeling/manage-custom-group-objects/update-a-custom-groups-definition.md
+++ b/docs/common-workflows/modeling/manage-custom-group-objects/update-a-custom-groups-definition.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to update a custom group’s definition through the Modeling service.
 
-You want to update the definition of the "Customers Value Metric Value Banding" custom group and rename it to "Customers Value Points Banding". The custom group is in the Strategy Tutorial project. The object ID of the custom group is C4E98C9B4BACB6D57CCF58BD95672BF4. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+You want to update the definition of the "Customers Value Metric Value Banding" custom group and rename it to "Customers Value Points Banding". The custom group is in the MicroStrategy Tutorial project. The object ID of the custom group is C4E98C9B4BACB6D57CCF58BD95672BF4. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-datamart-objects/retrieve-a-datamart-definition.md b/docs/common-workflows/modeling/manage-datamart-objects/retrieve-a-datamart-definition.md
index 6adba4dc1..f77f0d698 100644
--- a/docs/common-workflows/modeling/manage-datamart-objects/retrieve-a-datamart-definition.md
+++ b/docs/common-workflows/modeling/manage-datamart-objects/retrieve-a-datamart-definition.md
@@ -12,7 +12,7 @@ This topic covers several workflows to retrieve a datamart definition:
 - [Retrieve a datamart definition with a filter custom expression in tree and tokens formats](#retrieve-a-datamart-definition-with-a-filter-custom-expression-in-tree-and-tokens-formats)
 - [Retrieve a datamart definition with advanced properties](#retrieve-a-datamart-definition-with-advanced-properties)
 
-You want to get the definition of the “Customer" datamart object as below screenshot with datamart options. The object ID of the datamart is  CEA3C6FC4E6749C8F8B19580D16D2443 in the "Strategy Tutorial" project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+You want to get the definition of the “Customer" datamart object as below screenshot with datamart options. The object ID of the datamart is  CEA3C6FC4E6749C8F8B19580D16D2443 in the "MicroStrategy Tutorial" project. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-datamart-objects/retrieve-applicable-properties-of-a-datamart.md b/docs/common-workflows/modeling/manage-datamart-objects/retrieve-applicable-properties-of-a-datamart.md
index 203430c45..bb1f90e45 100644
--- a/docs/common-workflows/modeling/manage-datamart-objects/retrieve-applicable-properties-of-a-datamart.md
+++ b/docs/common-workflows/modeling/manage-datamart-objects/retrieve-applicable-properties-of-a-datamart.md
@@ -5,7 +5,7 @@ description: This workflow sample demonstrates how to retrieve applicable proper
 
 You can use REST APIs to retrieve all the applicable properties of a datamart through the Modeling service. The workflow includes the following REST APIs requests.
 
-The datamart object ID is 0DC7208C43B65E0DA10B26A6273F5067. The datamart is in the project "Strategy Tutorial", and the project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
+The datamart object ID is 0DC7208C43B65E0DA10B26A6273F5067. The datamart is in the project "MicroStrategy Tutorial", and the project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-derived-element-objects/create-a-derived-element.md b/docs/common-workflows/modeling/manage-derived-element-objects/create-a-derived-element.md
index 2232aa0df..76874cd05 100644
--- a/docs/common-workflows/modeling/manage-derived-element-objects/create-a-derived-element.md
+++ b/docs/common-workflows/modeling/manage-derived-element-objects/create-a-derived-element.md
@@ -27,7 +27,7 @@ This workflow sample demonstrates how to create a new derived element object thr
 
 ## Create a derived element using a list element
 
-You want to create a new `"{Age Range} = 25 to 34, Under 24"` derived element object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `091B51154B22036C53CFBB9958B2E8FC`.
+You want to create a new `"{Age Range} = 25 to 34, Under 24"` derived element object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `091B51154B22036C53CFBB9958B2E8FC`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-derived-element-objects/replace-an-existing-element.md b/docs/common-workflows/modeling/manage-derived-element-objects/replace-an-existing-element.md
index debe3b0b4..145cbf63a 100644
--- a/docs/common-workflows/modeling/manage-derived-element-objects/replace-an-existing-element.md
+++ b/docs/common-workflows/modeling/manage-derived-element-objects/replace-an-existing-element.md
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to replace an existing derived element obj
 1. Commit the changeset.
 1. Delete the changeset.
 
-You want to replace the existing `"Region DE"` derived element object in the Strategy Tutorial project. The derived element object ID is `610B9CC14AD9DCB69F094C89D3B5480B`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to replace the existing `"Region DE"` derived element object in the MicroStrategy Tutorial project. The derived element object ID is `610B9CC14AD9DCB69F094C89D3B5480B`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-derived-element-objects/retrieve-a-derived-elements-definition.md b/docs/common-workflows/modeling/manage-derived-element-objects/retrieve-a-derived-elements-definition.md
index d4bc13b90..ac07bd8cb 100644
--- a/docs/common-workflows/modeling/manage-derived-element-objects/retrieve-a-derived-elements-definition.md
+++ b/docs/common-workflows/modeling/manage-derived-element-objects/retrieve-a-derived-elements-definition.md
@@ -21,7 +21,7 @@ You can use REST APIs to retrieve the definition for a derived element through t
 
 ## Retrieve a derived element's definition
 
-You want to get the definition of a derived element that is defined by a list. The object ID of the derived element is `610B9CC14AD9DCB69F094C89D3B5480B` in the Strategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to get the definition of a derived element that is defined by a list. The object ID of the derived element is `610B9CC14AD9DCB69F094C89D3B5480B` in the MicroStrategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -170,7 +170,7 @@ Response Code: 200 (The derived element's definition is returned successfully.)
 
 ## Retrieve the definition of a derived element within a changeset
 
-You want to get the definition of the derived element object, `"groupDerivedElement"`. The object ID of the derived element is `610B9CC14AD9DCB69F094C89D3B5480B` in the Strategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+You want to get the definition of the derived element object, `"groupDerivedElement"`. The object ID of the derived element is `610B9CC14AD9DCB69F094C89D3B5480B` in the MicroStrategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-drill-maps/create-a-drill-map.md b/docs/common-workflows/modeling/manage-drill-maps/create-a-drill-map.md
index de7ac518a..7ed01824b 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/create-a-drill-map.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/create-a-drill-map.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to create a new drill map object through the Modeling service.
 
-The drill map is under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `091B51154B22036C53CFBB9958B2E8FC`.
+The drill map is under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `091B51154B22036C53CFBB9958B2E8FC`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-drill-map-definition.md b/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-drill-map-definition.md
index 0c093aa7f..ce2349b8e 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-drill-map-definition.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-drill-map-definition.md
@@ -18,7 +18,7 @@ You can use REST APIs to retrieve the definition of a drill map through the Mode
 
 ## Retrieve a drill map definition
 
-You want to get the definition of a drill map object. The object ID of the drill map is `CC2E6AA3421EFF5C41C2D0939750BB24` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of a drill map object. The object ID of the drill map is `CC2E6AA3421EFF5C41C2D0939750BB24` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
@@ -187,7 +187,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 :::
 
-You want to get the definition of the Sample Drill Map drill map object. The object ID of this drill map is `CC2E6AA3421EFF5C41C2D0939750BB24` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the Sample Drill Map drill map object. The object ID of this drill map is `CC2E6AA3421EFF5C41C2D0939750BB24` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-list-of-objects.md b/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-list-of-objects.md
index 50d634cc1..390de5c42 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-list-of-objects.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/retrieve-a-list-of-objects.md
@@ -8,7 +8,7 @@ description: This workflow sample demonstrates how to get the list of objects as
 
 This workflow sample demonstrates how to get the list of objects associated with a specific drill map.
 
-You want to get the list of objects associated with the `Drill Map for Demo` drill map object in the Strategy Tutorial project. The project ID is `091B51154B22036C53CFBB9958B2E8FC`. The drill map ID is `CC2E6AA3421EFF5C41C2D0939750BB24`.
+You want to get the list of objects associated with the `Drill Map for Demo` drill map object in the MicroStrategy Tutorial project. The project ID is `091B51154B22036C53CFBB9958B2E8FC`. The drill map ID is `CC2E6AA3421EFF5C41C2D0939750BB24`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-drill-maps/update-a-drill-map.md b/docs/common-workflows/modeling/manage-drill-maps/update-a-drill-map.md
index 2d194a0b3..7b73346a1 100644
--- a/docs/common-workflows/modeling/manage-drill-maps/update-a-drill-map.md
+++ b/docs/common-workflows/modeling/manage-drill-maps/update-a-drill-map.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to update an existing drill map object through the Modeling service.
 
-You want to update the existing `Drill Map for Demo` drill map object in the Strategy Tutorial project. The project ID is `091B51154B22036C53CFBB9958B2E8FC`). The drill map ID is `CC2E6AA3421EFF5C41C2D0939750BB24`.
+You want to update the existing `Drill Map for Demo` drill map object in the MicroStrategy Tutorial project. The project ID is `091B51154B22036C53CFBB9958B2E8FC`). The drill map ID is `CC2E6AA3421EFF5C41C2D0939750BB24`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/create-a-fact-object.md b/docs/common-workflows/modeling/manage-fact-objects/create-a-fact-object.md
index 738452262..96c1d9d6b 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/create-a-fact-object.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/create-a-fact-object.md
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to create a fact object through the Modeli
 1. Commit the changeset
 1. Delete the changeset
 
-You want to create a "Profit" fact object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a "Profit" fact object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition-within-a-changeset.md
index 5aa99d824..c1064408e 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition-within-a-changeset.md
@@ -26,7 +26,7 @@ Changesets are used in this workflow. For information on how to create and use c
 1. [Get a fact's definition within a changeset.](#get-a-facts-definition-within-a-changeset)
 1. Delete the changeset.
 
-You want to get the definition of the "Profit" fact object. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the "Strategy Tutorial" project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Profit" fact object. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the "MicroStrategy Tutorial" project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition.md b/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition.md
index 75703c0e9..97028814f 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/retrieve-a-facts-definition.md
@@ -23,7 +23,7 @@ This topic covers two workflows for retrieving a fact’s definition:
 
 This workflow sample demonstrates how to retrieve the definition of a fact through the Modeling service.
 
-You want to get the definition of the "Profit" fact object. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Profit" fact object. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -99,7 +99,7 @@ Response Code: 200 (The fact's definition was returned successfully.)
 
 ## Retrieve a fact's definition with expressions in tree and tokens formats
 
-In this sample workflow, you want to get the definition of the "Profit" fact object, with its expressions returned in tree and tokens formats. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this sample workflow, you want to get the definition of the "Profit" fact object, with its expressions returned in tree and tokens formats. The object ID of the fact is `FDD652E7444ADD7AB6B25F9C1FA15F92` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-fact-objects/update-a-fact-object.md b/docs/common-workflows/modeling/manage-fact-objects/update-a-fact-object.md
index 774f4e6c4..f2541eee3 100644
--- a/docs/common-workflows/modeling/manage-fact-objects/update-a-fact-object.md
+++ b/docs/common-workflows/modeling/manage-fact-objects/update-a-fact-object.md
@@ -19,7 +19,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 1. Commit the changeset.
 1. Delete the changeset.
 
-You want to update the "Profit" fact object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to update the "Profit" fact object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object-with-a-custom-expression.md b/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object-with-a-custom-expression.md
index ffb950ab4..4c9ef9f5a 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object-with-a-custom-expression.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object-with-a-custom-expression.md
@@ -29,7 +29,7 @@ This workflow sample demonstrates how to create a new filter object using a cust
 
 Additional samples are provided in [More samples](#more-samples).
 
-You want to create a new "(Year(CurrentDate()) - 5)< Year@ID" filter object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new "(Year(CurrentDate()) - 5)< Year@ID" filter object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object.md b/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object.md
index a300b1001..d3850bb93 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/create-a-filter-object.md
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to create a new filter object through the
 1. Commit the changeset
 1. Delete the changeset
 
-You want to create a new “Year>2015“ filter object under the Public Objects folder in the Strategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new “Year>2015“ filter object under the Public Objects folder in the MicroStrategy Tutorial project. The folder object ID is `98FE182C2A10427EACE0CD30B6768258`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition-within-a-changeset.md
index 25ab934c5..fafb4ef4d 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition-within-a-changeset.md
@@ -22,7 +22,7 @@ Changesets are used in this workflow. For information on how to create and use c
 1. [Get the filter's definition within a changeset.](#get-a-filter-definition-within-a-changeset)
 1. Delete the changeset.
 
-You want to get the definition of the "Year > 2015" filter object. The object ID of the filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Year > 2015" filter object. The object ID of the filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition.md b/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition.md
index 54595dc05..4f8476de7 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/retrieve-a-filters-definition.md
@@ -25,7 +25,7 @@ This topic covers several workflows for retrieving a filter's definition:
 
 This workflow sample demonstrates how to retrieve the definition of a filter through the Modeling service.
 
-You want to get the definition of the "Year > 2015" filter object. The object ID of the filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the "Year > 2015" filter object. The object ID of the filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-filter-objects/update-a-filters-definition.md b/docs/common-workflows/modeling/manage-filter-objects/update-a-filters-definition.md
index 651663f9e..44b78ff28 100644
--- a/docs/common-workflows/modeling/manage-filter-objects/update-a-filters-definition.md
+++ b/docs/common-workflows/modeling/manage-filter-objects/update-a-filters-definition.md
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to update a filter's definition through th
 1. Commit the changeset using `POST /api/model/changesets/{changesetId}/commit`
 1. Delete the changeset using `DELETE /api/model/changesets/{changesetId}`
 
-You want to update the definition of the "Year > 2015" filter and rename it to "Year > 2020". The filter is in the Strategy Tutorial project. The object ID of the filter is 8018C24FEBC4406CB9E36838C01C82D1. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754
+You want to update the definition of the "Year > 2015" filter and rename it to "Year > 2020". The filter is in the MicroStrategy Tutorial project. The object ID of the filter is 8018C24FEBC4406CB9E36838C01C82D1. The project ID is B7CA92F04B9FAE8D941C3E9B7E0CD754
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-applicable-properties.md b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-applicable-properties.md
index 7dfde705f..aae4d103e 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-applicable-properties.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-applicable-properties.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This topic covers the workflow to retrieve a metric's applicable properties.
 
-Get the applicable properties of the `“Cost Comparison"` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+Get the applicable properties of the `“Cost Comparison"` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition-within-a-changeset.md
index f7e0d4517..6d73edefc 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition-within-a-changeset.md
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 :::
 
-Get the definition of the `“Cost Comparison”` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+Get the definition of the `“Cost Comparison”` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 For different formats of metric expressions, see [Retrieve a metric's definition](../manage-metric-objects/retrieve-a-metrics-definition.md).
 
diff --git a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition.md b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition.md
index 9fce2e3ef..7bcab10bf 100644
--- a/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition.md
+++ b/docs/common-workflows/modeling/manage-metric-objects/retrieve-a-metrics-definition.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This topic covers several workflows for retrieving a metric's definition.
 
-You want to get the definition of the `“Cost Comparison"` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `“Cost Comparison"` metric object. The object ID of the metric is `28F95FDC4EF1CA5746F8E6971A144BED` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/create-a-prompt-within-a-changeset.md b/docs/common-workflows/modeling/manage-prompt-objects/create-a-prompt-within-a-changeset.md
index ba7ba6ce7..e11237ac1 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/create-a-prompt-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/create-a-prompt-within-a-changeset.md
@@ -19,7 +19,7 @@ This workflow sample demonstrates how to create a new prompt object through the
 1. Commit a changeset using `POST /api/model/changesets/{changesetId}/commit`
 1. Delete a changeset using `DELETE /api/model/changesets/{changesetId}`
 
-You want to create a new prompt object for the `"Call Center in USA"` prompt under a specific folder in the Strategy Tutorial project. The folder object ID is `8A1831FF494F528D02A4A8BF5FB73459`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a new prompt object for the `"Call Center in USA"` prompt under a specific folder in the MicroStrategy Tutorial project. The folder object ID is `8A1831FF494F528D02A4A8BF5FB73459`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -39,7 +39,7 @@ Get the project ID from [GET /api/projects](https://demo.microstrategy.com/Micro
 
 ## Create a prompt using [POST /api/model/prompts](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Prompts/ms-postPrompt)
 
-You want to create a `"Call Center in USA"` prompt of an attribute element prompt under a specific folder in the Strategy Tutorial project. To create the prompt, you must submit the request body with the correct information. In `"information"`, provide the `"subType"`, `"name"`, and `"destinationFolderId"` for the prompt you want to create.
+You want to create a `"Call Center in USA"` prompt of an attribute element prompt under a specific folder in the MicroStrategy Tutorial project. To create the prompt, you must submit the request body with the correct information. In `"information"`, provide the `"subType"`, `"name"`, and `"destinationFolderId"` for the prompt you want to create.
 
 If you are constructing the POST prompt request body based on the response of the GET prompt call of an existing prompt, be aware that any embedded objects (`"isEmbedded":true`) cannot be used to create a new prompt, as the embedded objects are only "local" to their owner.
 
diff --git a/docs/common-workflows/modeling/manage-prompt-objects/retrieve-a-prompts-definition.md b/docs/common-workflows/modeling/manage-prompt-objects/retrieve-a-prompts-definition.md
index 3ea02465a..315028133 100644
--- a/docs/common-workflows/modeling/manage-prompt-objects/retrieve-a-prompts-definition.md
+++ b/docs/common-workflows/modeling/manage-prompt-objects/retrieve-a-prompts-definition.md
@@ -14,7 +14,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve a prompt's definition.
 
-You want to get the definition of the `"Call Center in USA"` prompt object. The object ID of the prompt is `2804B5284AFF95E8E0EEB4AC09B5B972` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the `"Call Center in USA"` prompt object. The object ID of the prompt is `2804B5284AFF95E8E0EEB4AC09B5B972` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object-using-a-custom-expression.md b/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object-using-a-custom-expression.md
index 0aefa9bbd..9f69b0d7e 100644
--- a/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object-using-a-custom-expression.md
+++ b/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object-using-a-custom-expression.md
@@ -20,7 +20,7 @@ This workflow sample demonstrates how to create a security filter definition thr
 
 Additional examples are provided in [More samples](#more-samples).
 
-In this workflow sample, you want to create a new security filter object to qualification for the last five years. The custom expression is `“(Year(CurrentDate()) - 5)< Year@ID”`. Save the security filter under the Public Objects folder in the Strategy Tutorial project. The folder ID is `98FE182C2A10427EACE0CD30B6768258`. The Strategy Tutorial project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to create a new security filter object to qualification for the last five years. The custom expression is `“(Year(CurrentDate()) - 5)< Year@ID”`. Save the security filter under the Public Objects folder in the MicroStrategy Tutorial project. The folder ID is `98FE182C2A10427EACE0CD30B6768258`. The MicroStrategy Tutorial project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object.md b/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object.md
index 6c278e39e..849e21001 100644
--- a/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object.md
+++ b/docs/common-workflows/modeling/manage-security-filter-objects/create-a-security-filter-object.md
@@ -21,7 +21,7 @@ This workflow sample demonstrates how to create a new security filter object thr
 
 Additional samples are provided in [More samples](#more-samples).
 
-In this workflow sample, you want to create a "Year > 2015" security filter object under the Public Objects folder in the Strategy Tutorial project. The folder ID is `98FE182C2A10427EACE0CD30B6768258`. The Strategy Tutorial project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to create a "Year > 2015" security filter object under the Public Objects folder in the MicroStrategy Tutorial project. The folder ID is `98FE182C2A10427EACE0CD30B6768258`. The MicroStrategy Tutorial project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-security-filter-objects/retrieve-a-security-filter-definition.md b/docs/common-workflows/modeling/manage-security-filter-objects/retrieve-a-security-filter-definition.md
index 5e6a87db0..07d452207 100644
--- a/docs/common-workflows/modeling/manage-security-filter-objects/retrieve-a-security-filter-definition.md
+++ b/docs/common-workflows/modeling/manage-security-filter-objects/retrieve-a-security-filter-definition.md
@@ -16,7 +16,7 @@ This topic covers several workflows for retrieving a security filter's definitio
 
 ## Retrieve a security filter's definition
 
-In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -104,7 +104,7 @@ Changesets are used in this workflow. For information on how to create and use c
 
 :::
 
-In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::info
 
@@ -252,7 +252,7 @@ Sample Response Code: 204 (The changeset has been deleted successfully)
 
 ## Retrieve a security filter's definition in tokens format
 
-In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the Strategy Tutorial project. This procedure is similar to [Retrieve a security filter's definition](#retrieve-a-security-filters-definition), except you want to enable the `showFilterTokens` parameter to retrieve the security filter's definition in tokens format.
+In this workflow sample, you want to get the definition of the "Year > 2015" security filter object. The object ID of the security filter is `8018C24FEBC4406CB9E36838C01C82D1` in the MicroStrategy Tutorial project. This procedure is similar to [Retrieve a security filter's definition](#retrieve-a-security-filters-definition), except you want to enable the `showFilterTokens` parameter to retrieve the security filter's definition in tokens format.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition-within-a-changeset.md b/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition-within-a-changeset.md
index 9982cd73e..4b580e0e3 100644
--- a/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition-within-a-changeset.md
+++ b/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition-within-a-changeset.md
@@ -22,7 +22,7 @@ An authorization token allows the API layer to hide internal session-related imp
 
 :::
 
-You want to get the definition of an object with the ID of `514C2064DF754990AF60432A1C1E4A77` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of an object with the ID of `514C2064DF754990AF60432A1C1E4A77` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 For different formats of subtotal expressions, see [Retrieve a subtotal's definition](retrieve-a-subtotals-definition.md).
 
diff --git a/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition.md b/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition.md
index 349905d76..c49146023 100644
--- a/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition.md
+++ b/docs/common-workflows/modeling/manage-subtotal-objects/retrieve-a-subtotals-definition.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This topic covers several workflows for retrieving a metric's definition:
 
-You want to get the definition of an object with the ID of `514C2064DF754990AF60432A1C1E4A77` in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of an object with the ID of `514C2064DF754990AF60432A1C1E4A77` in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/create-a-new-table-object.md b/docs/common-workflows/modeling/manage-table-objects/create-a-new-table-object.md
index ea418e3ac..eca28d790 100644
--- a/docs/common-workflows/modeling/manage-table-objects/create-a-new-table-object.md
+++ b/docs/common-workflows/modeling/manage-table-objects/create-a-new-table-object.md
@@ -18,7 +18,7 @@ This workflow sample demonstrates how to create a new table object through the M
 
 ## Create a new table object
 
-In this workflow sample, you create a new `"CITY_CTR_SLS"` table object in the Strategy Tutorial project. Table name should be unique within the project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`. All schema tables are created under the objects/tables folder schema.
+In this workflow sample, you create a new `"CITY_CTR_SLS"` table object in the MicroStrategy Tutorial project. Table name should be unique within the project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`. All schema tables are created under the objects/tables folder schema.
 
 Get the authorization token needed to execute the request with [POST /api/auth/login]([https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Authentication/postLogin).
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-list-of-all-available-table-definitions.md b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-list-of-all-available-table-definitions.md
index d5f181205..af90ce317 100644
--- a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-list-of-all-available-table-definitions.md
+++ b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-list-of-all-available-table-definitions.md
@@ -10,7 +10,7 @@ You can use REST APIs to retrieve the definitions for a list of all available ta
 
 ## Retrieve a list of all available tables' definitions
 
-In this workflow sample, you want to get the definitions of all available tables in the project schema. Use the Strategy Tutorial project. Its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definitions of all available tables in the project schema. Use the MicroStrategy Tutorial project. Its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -89,7 +89,7 @@ Response Code: 200 (The tables' definitions are returned successfully.)
 
 ### Retrieve a list of available tables' definitions within a changeset
 
-In this workflow sample, you want to get the definitions of all available tables in the project schema. Use the Strategy Tutorial project. Its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definitions of all available tables in the project schema. Use the MicroStrategy Tutorial project. Its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-partition-mapping-tables-definition.md b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-partition-mapping-tables-definition.md
index 524c2df8d..06b896f31 100644
--- a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-partition-mapping-tables-definition.md
+++ b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-partition-mapping-tables-definition.md
@@ -34,7 +34,7 @@ Get the project ID from [GET /api/projects](https://demo.microstrategy.com/Micro
 
 ## Retrieve a WHPM table's definition
 
-Use this workflow sample to get the definition of a WHPM table. The object ID of the table is `569A89E78FA1455687F4E327B259B3FB`. The table is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+Use this workflow sample to get the definition of a WHPM table. The object ID of the table is `569A89E78FA1455687F4E327B259B3FB`. The table is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 Get the table's definition with [GET /api/model/tables/\{TableId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Tables/ms-getTableDetails).
 
@@ -245,7 +245,7 @@ Response Code: 200 (The WHPM table's definition is returned successfully.)
 
 ## Retrieve a MDPM table's definition
 
-Use this workflow sample to get the definition of an MDPM table. The object ID of the table is `473718A30DA84A9A814424537879778F`. The table is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`. The API usage is the same as retrieving a WHPM table. Unlike all other tables, you can use "showExpressionAs" and "showFilterTokens" to customize partition filter representation.
+Use this workflow sample to get the definition of an MDPM table. The object ID of the table is `473718A30DA84A9A814424537879778F`. The table is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`. The API usage is the same as retrieving a WHPM table. Unlike all other tables, you can use "showExpressionAs" and "showFilterTokens" to customize partition filter representation.
 
 Get the table's definition with [GET /api/model/tables/\{TableId}](https://demo.microstrategy.com/MicroStrategyLibrary/api-docs/index.html#/Tables/ms-getTableDetails).
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-prompt-of-an-sap-hana-table.md b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-prompt-of-an-sap-hana-table.md
index 915c9844b..762f69a06 100644
--- a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-prompt-of-an-sap-hana-table.md
+++ b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-prompt-of-an-sap-hana-table.md
@@ -22,7 +22,7 @@ This workflow applies only to SAP HANA tables with input parameters because only
 
 This workflow sample demonstrates how to retrieve an existing prompt of an SAP HANA table.
 
-The object ID of the table is `84AF2517E662417D9924FD678B44591A` and the object ID of the prompt is `339585B03F354D11AE8760C4489160F1`. The table is in the Strategy Tutorial Advanced project and its project ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`.
+The object ID of the table is `84AF2517E662417D9924FD678B44591A` and the object ID of the prompt is `339585B03F354D11AE8760C4489160F1`. The table is in the MicroStrategy Tutorial Advanced project and its project ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`.
 
 :::tip
 
@@ -93,7 +93,7 @@ Response Code: 200 (Table's prompt is returned successfully.)
 
 ## Retrieve a table prompt within a changeset
 
-You want to get the prompt of the same table object mentioned in [Retrieve a prompt of a table](#retrieve-a-prompt-of-a-table), while within a changeset. The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the Strategy Tutorial Advanced project and its project ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`.
+You want to get the prompt of the same table object mentioned in [Retrieve a prompt of a table](#retrieve-a-prompt-of-a-table), while within a changeset. The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the MicroStrategy Tutorial Advanced project and its project ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-tables-definition.md b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-tables-definition.md
index 3ad7ea3bc..fa7175782 100644
--- a/docs/common-workflows/modeling/manage-table-objects/retrieve-a-tables-definition.md
+++ b/docs/common-workflows/modeling/manage-table-objects/retrieve-a-tables-definition.md
@@ -18,7 +18,7 @@ You can use REST APIs to retrieve the definition for a table through the Modelin
 
 ## Retrieve a table's definition
 
-In this workflow sample, you want to get the definition of a table that is defined by a normal warehouse table. The object ID of the table is `862780DC499A14D74FEC7EB2EF317DA2`. The table is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definition of a table that is defined by a normal warehouse table. The object ID of the table is `862780DC499A14D74FEC7EB2EF317DA2`. The table is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -323,7 +323,7 @@ Response Code: 200 (The table's definition is returned successfully.)
 
 ## Retrieve a table's definition within a changeset
 
-In this workflow sample, you want to get the definition of the same table object mentioned in [Retrieve a table's definition](#retrieve-a-tables-definition), while within a changeset. The object ID of the table is `862780DC499A14D74FEC7EB2EF317DA2`. The table is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definition of the same table object mentioned in [Retrieve a table's definition](#retrieve-a-tables-definition), while within a changeset. The object ID of the table is `862780DC499A14D74FEC7EB2EF317DA2`. The table is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-a-prompt-of-an-sap-hana-table.md b/docs/common-workflows/modeling/manage-table-objects/update-a-prompt-of-an-sap-hana-table.md
index 09b50d0d3..b6664a600 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-a-prompt-of-an-sap-hana-table.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-a-prompt-of-an-sap-hana-table.md
@@ -28,7 +28,7 @@ You should at least have **read access** to the table to successfully complete t
 
 :::
 
-You want to update the prompt of a table. The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the Strategy Tutorial Advanced project and its ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`. The object ID of the current prompt is `339585B03F354D11AE8760C4489160F1` and you want to update fields of the prompt, for example, the name and default answers.
+You want to update the prompt of a table. The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the MicroStrategy Tutorial Advanced project and its ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`. The object ID of the current prompt is `339585B03F354D11AE8760C4489160F1` and you want to update fields of the prompt, for example, the name and default answers.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-a-tables-definition.md b/docs/common-workflows/modeling/manage-table-objects/update-a-tables-definition.md
index 1e2d04997..46ac73a16 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-a-tables-definition.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-a-tables-definition.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to update an existing table through the Modeling service.
 
-In this workflow sample, you update an existing `"CITY_CTR_SLS"` table object in the Strategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you update an existing `"CITY_CTR_SLS"` table object in the MicroStrategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-a-tables-physical-table-structure.md b/docs/common-workflows/modeling/manage-table-objects/update-a-tables-physical-table-structure.md
index 5daf43329..63eeddf33 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-a-tables-physical-table-structure.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-a-tables-physical-table-structure.md
@@ -14,7 +14,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to update an existing table's physical table structure through the Modeling service.
 
-In this workflow sample, you update an existing `"CITY_CTR_SLS"` table's physical table structure in the Strategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you update an existing `"CITY_CTR_SLS"` table's physical table structure in the MicroStrategy Tutorial project. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-table-objects/update-sap-hana-parameters.md b/docs/common-workflows/modeling/manage-table-objects/update-sap-hana-parameters.md
index e62bd9821..eb57d49d9 100644
--- a/docs/common-workflows/modeling/manage-table-objects/update-sap-hana-parameters.md
+++ b/docs/common-workflows/modeling/manage-table-objects/update-sap-hana-parameters.md
@@ -32,7 +32,7 @@ To replace the current prompt with a standalone prompt, the prompt must either b
 
 :::
 
-The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the Strategy Tutorial Advanced project and its ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`. Different operations on different SAP HANA parameters are done:
+The object ID of the table is `84AF2517E662417D9924FD678B44591A`. The table is in the MicroStrategy Tutorial Advanced project and its ID is `6AB8DFFE4B99B7F6FB0E94AD176C4A28`. Different operations on different SAP HANA parameters are done:
 
 - Keep `IP_Column_Hier_Value_Help` the same
 - Reset `IP_Static_List`
diff --git a/docs/common-workflows/modeling/manage-transformation-objects/create-a-transformation-object.md b/docs/common-workflows/modeling/manage-transformation-objects/create-a-transformation-object.md
index 890a8066d..a50c28c1d 100644
--- a/docs/common-workflows/modeling/manage-transformation-objects/create-a-transformation-object.md
+++ b/docs/common-workflows/modeling/manage-transformation-objects/create-a-transformation-object.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 ## Create a transformation object
 
-In this workflow sample, you want to create a `"Last year’s"` transformation object under the My Personal Objects/My Objects (MSTR User/My Objects) folder in the Strategy Tutorial project. The folder object ID is `9B25D45A4834A213A70C10B1703D4A77`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to create a `"Last year’s"` transformation object under the My Personal Objects/My Objects (MSTR User/My Objects) folder in the MicroStrategy Tutorial project. The folder object ID is `9B25D45A4834A213A70C10B1703D4A77`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-transformation-objects/retrieve-a-transformations-definition.md b/docs/common-workflows/modeling/manage-transformation-objects/retrieve-a-transformations-definition.md
index f319eea45..5c52c0b89 100644
--- a/docs/common-workflows/modeling/manage-transformation-objects/retrieve-a-transformations-definition.md
+++ b/docs/common-workflows/modeling/manage-transformation-objects/retrieve-a-transformations-definition.md
@@ -18,7 +18,7 @@ This topic covers the following workflows for retrieving an transformation’s d
 
 ## Retrieve a transformation's definition
 
-In this workflow sample, you want to get the definition of the `"2 Weeks Ago"` transformation object. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definition of the `"2 Weeks Ago"` transformation object. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
@@ -92,7 +92,7 @@ Response Code: 200 (The transformation's definition is returned successfully.)
 
 ## Retrieve a transformation's definition within a changeset
 
-In this workflow sample, you want to get the definition of the same transformation object mentioned in [Retrieve a transformation's definition](#retrieve-a-transformations-definition), while within a changeset. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you want to get the definition of the same transformation object mentioned in [Retrieve a transformation's definition](#retrieve-a-transformations-definition), while within a changeset. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 Changesets are used in this workflow. For information on how to create and use changesets, see [Changesets](/docs/common-workflows/modeling/changesets.md). If you plan to use the response of `GET /api/model/transformations/{transformationId}` to create a new table or update a specific table's definitions, you should associate all requests with one changeset.
 
@@ -168,7 +168,7 @@ Sample Response Code: 200 (The transformation's definition is returned successfu
 
 ## Retrieve a transformation's definition with transformation attribute form expressions in tree and tokens formats
 
-In this sample workflow, you want to get the definition of the `"2 Weeks Ago"` transformation object, with its transformation attribute form expressions returned in tree and tokens formats. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the Strategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this sample workflow, you want to get the definition of the `"2 Weeks Ago"` transformation object, with its transformation attribute form expressions returned in tree and tokens formats. The object ID of the transformation is `6CB9ABB711D3E4F11000E887EC6DE8A4`. The transformation is in the MicroStrategy Tutorial project and its project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 Expressions are presented in the following formats:
 
diff --git a/docs/common-workflows/modeling/manage-transformation-objects/update-a-transformations-definition.md b/docs/common-workflows/modeling/manage-transformation-objects/update-a-transformations-definition.md
index 562dae998..d373e9473 100644
--- a/docs/common-workflows/modeling/manage-transformation-objects/update-a-transformations-definition.md
+++ b/docs/common-workflows/modeling/manage-transformation-objects/update-a-transformations-definition.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to update an existing transformation through the Modeling service.
 
-In this workflow sample, you update an existing `"Last year’s"` transformation object under the My Personal Objects/My Objects (MSTR User/My Objects) folder in the Strategy Tutorial project. The folder object ID is `9B25D45A4834A213A70C10B1703D4A77`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
+In this workflow sample, you update an existing `"Last year’s"` transformation object under the My Personal Objects/My Objects (MSTR User/My Objects) folder in the MicroStrategy Tutorial project. The folder object ID is `9B25D45A4834A213A70C10B1703D4A77`. The project ID is `B19DEDCC11D4E0EFC000EB9495D0F44F`.
 
 :::info
 
diff --git a/docs/common-workflows/modeling/manage-user-hierarchy-objects/create-a-user-hierarchy.md b/docs/common-workflows/modeling/manage-user-hierarchy-objects/create-a-user-hierarchy.md
index 2b3f94416..a997f6651 100644
--- a/docs/common-workflows/modeling/manage-user-hierarchy-objects/create-a-user-hierarchy.md
+++ b/docs/common-workflows/modeling/manage-user-hierarchy-objects/create-a-user-hierarchy.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to create a user hierarchy object through the Modeling service.
 
-You want to create a Time user hierarchy object, in the Strategy Tutorial project, which contains the relationship between the Year, Month of Year, Quarter, Month, and Day attributes. The folder object ID is `8A1831FF494F528D02A4A8BF5FB73459`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to create a Time user hierarchy object, in the MicroStrategy Tutorial project, which contains the relationship between the Year, Month of Year, Quarter, Month, and Day attributes. The folder object ID is `8A1831FF494F528D02A4A8BF5FB73459`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-list-of-available-user-hierarchies.md b/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-list-of-available-user-hierarchies.md
index 4ad5384a8..10efea294 100644
--- a/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-list-of-available-user-hierarchies.md
+++ b/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-list-of-available-user-hierarchies.md
@@ -8,7 +8,7 @@ description: This workflow sample demonstrates how to retrieve the list of avail
 
 This workflow sample demonstrates how to retrieve the list of available user hierarchies in one project within a changeset.
 
-You want to get all available user hierarchies in the Strategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get all available user hierarchies in the MicroStrategy Tutorial project. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-user-hierarchys-definition.md b/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-user-hierarchys-definition.md
index 013ae803f..1e45e9fbb 100644
--- a/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-user-hierarchys-definition.md
+++ b/docs/common-workflows/modeling/manage-user-hierarchy-objects/retrieve-a-user-hierarchys-definition.md
@@ -16,7 +16,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 This workflow sample demonstrates how to retrieve an user hierarchy's definition within a changeset.
 
-You want to get the definition of the Time user hierarchy object, in the Strategy Tutorial project, which contains the relationship between the Year, Month of Year, Quarter, Month, and Day attributes. The object ID of the user hierarchy is `B793B55C11D3E4E51000E887EC6DE8A4`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
+You want to get the definition of the Time user hierarchy object, in the MicroStrategy Tutorial project, which contains the relationship between the Year, Month of Year, Quarter, Month, and Day attributes. The object ID of the user hierarchy is `B793B55C11D3E4E51000E887EC6DE8A4`. The project ID is `B7CA92F04B9FAE8D941C3E9B7E0CD754`.
 
 :::tip
 
diff --git a/docs/getting-started/improve-performance-by-working-with-partial-resources/improve-performance-by-working-with-partial-resources.md b/docs/getting-started/improve-performance-by-working-with-partial-resources/improve-performance-by-working-with-partial-resources.md
index 71c99a025..f1831a1e0 100644
--- a/docs/getting-started/improve-performance-by-working-with-partial-resources/improve-performance-by-working-with-partial-resources.md
+++ b/docs/getting-started/improve-performance-by-working-with-partial-resources/improve-performance-by-working-with-partial-resources.md
@@ -67,7 +67,7 @@ Here is an example using `GET /api/projects/MicroStrategy%20Tutorial?fields=id,n
 ```json
 {
   "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-  "name": "Strategy Tutorial",
+  "name": "MicroStrategy Tutorial",
   "owner": {
     "name": "Administrator",
     "id": "54F3D26011D2896560009A8E67019608"
@@ -81,10 +81,10 @@ Here is an example of full representation without fields.
 {
   "acg": 255,
   "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-  "name": "Strategy Tutorial",
+  "name": "MicroStrategy Tutorial",
   "status": 0,
   "alias": "",
-  "description": "Strategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
+  "description": "MicroStrategy Tutorial project and application set designed to illustrate the platform's rich functionality. The theme is an Electronics, Books, Movies and Music store. Employees, Inventory, Finance, Product Sales and Suppliers are analyzed.",
   "dateCreated": "2001-01-02T20:42:04.000+0000",
   "dateModified": "2019-06-28T03:32:24.000+0000",
   "owner": {
@@ -116,7 +116,7 @@ Here is an example using `GET /api/projects?fields=id,name`.
   },
   {
     "id": "B19DEDCC11D4E0EFC000EB9495D0F44F",
-    "name": "Strategy Tutorial"
+    "name": "MicroStrategy Tutorial"
   }
 ]
 ```

From 74b85a16fc0e39c534c3acffbb9f902abaea99d6 Mon Sep 17 00:00:00 2001
From: zhe_mstr <zhe@microstrategy.com>
Date: Tue, 11 Feb 2025 13:47:31 +0800
Subject: [PATCH 3/5] fix comments

---
 .../manage-subscriptions/create-and-get-a-subscription.md     | 2 +-
 .../create-subscription-for-multi-content.md                  | 2 +-
 .../create-subscription-with-prompted-content.md              | 4 ++--
 .../manage-licensing/license-audit-compliance.md              | 4 ++--
 .../server-level-privileges/manage-server-level-privileges.md | 2 +-
 .../analytics/object-discovery/folder-browsing.md             | 2 +-
 6 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
index 92ddfcab3..abc1176d8 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
@@ -332,7 +332,7 @@ Sample Response
   [
     {
       "id": "C1E141E611D603A2100086B3A5E8F8A4",
-      "name": "Strategy Web User"
+      "name": "MicroStrategy Web User"
     }
   ]
   ```
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
index 3622c00bf..f637001df 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-for-multi-content.md
@@ -358,7 +358,7 @@ Sample Response
     "recipients": [
       {
         "id": "C1E141E611D603A2100086B3A5E8F8A4",
-        "name": "Strategy Web User",
+        "name": "MicroStrategy Web User",
         "isGroup": false,
         "type": "user",
         "includeType": "TO",
diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
index beda96180..514f9faa6 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-subscription-with-prompted-content.md
@@ -159,7 +159,7 @@ Sample Request
 
   ```bash
   curl -X GET -b ~/cookie-jar.txt --header 'Accept: application/json'
-  --header 'X-MSTR-AuthToken: {AuthToken}' https://demo.microstrategy.com/MicroStrategyLibrary/api/users?nameBegins=Strategy Web User&fields=name,id
+  --header 'X-MSTR-AuthToken: {AuthToken}' https://demo.microstrategy.com/MicroStrategyLibrary/api/users?nameBegins=MicroStrategy Web User&fields=name,id
   ```
 
 Sample Response
@@ -170,7 +170,7 @@ Sample Response
   [
     {
       "id": "",
-      "name": "Strategy Web User"
+      "name": "MicroStrategy Web User"
     }
   ]
   ```
diff --git a/docs/common-workflows/administration/manage-licensing/license-audit-compliance.md b/docs/common-workflows/administration/manage-licensing/license-audit-compliance.md
index 8e50655ac..8551f938b 100644
--- a/docs/common-workflows/administration/manage-licensing/license-audit-compliance.md
+++ b/docs/common-workflows/administration/manage-licensing/license-audit-compliance.md
@@ -158,11 +158,11 @@ Sample Response Body:
   "auditTime": "2023-05-04T10:47:46.766Z",
   "contactLicenses": [],
   "userGroups": [
-    ["3D0F5EF8978D4AE086012C196BF01EBA", "Strategy Groups"],
+    ["3D0F5EF8978D4AE086012C196BF01EBA", "MicroStrategy Groups"],
     ["5F3FAFE011D2D8CC6000CC8E67019608", "System Monitors"],
     ["5F3FAFE111D2D8CC6000CC8E67019608", "System Administrators"],
     ["C82C6B1011D2894CC0009D9F29718E4F", "Everyone"],
-    ["5B6C1434431D99F9A8230191FE5F6849", "Strategy Service Accounts"],
+    ["5B6C1434431D99F9A8230191FE5F6849", "MicroStrategy Service Accounts"],
     ["FB5CDCCE4D0E70EDE48110A0FDCFD370", "Platform Support Administrators"]
   ],
   "userLicenses": [
diff --git a/docs/common-workflows/administration/server-management/server-level-privileges/manage-server-level-privileges.md b/docs/common-workflows/administration/server-management/server-level-privileges/manage-server-level-privileges.md
index ef5ee8ea5..8a594feff 100644
--- a/docs/common-workflows/administration/server-management/server-level-privileges/manage-server-level-privileges.md
+++ b/docs/common-workflows/administration/server-management/server-level-privileges/manage-server-level-privileges.md
@@ -344,7 +344,7 @@ The REST server returns a JSON object that contains the updated information for
     },
     {
       "id": "C2E4DA4A411B972B063FE8A583989959",
-      "name": "Strategy Web Professional",
+      "name": "MicroStrategy Web Professional",
       "source": {
         "type": ["MSTR"]
       }
diff --git a/docs/common-workflows/analytics/object-discovery/folder-browsing.md b/docs/common-workflows/analytics/object-discovery/folder-browsing.md
index 94a0a62fc..c3f4b2121 100644
--- a/docs/common-workflows/analytics/object-discovery/folder-browsing.md
+++ b/docs/common-workflows/analytics/object-discovery/folder-browsing.md
@@ -219,7 +219,7 @@ Sample Response
       }
     },
     {
-      "name": "Strategy Platform Capabilities",
+      "name": "MicroStrategy Platform Capabilities",
       "id": "D64C532E4E7FBA74D29A7CA3576F39CF",
       "type": 8,
       "description": "This folder contains examples of many of the sophisticated capabilities within the Strategy platform.",

From 9240972ac8a555b8628f9744c89a96a7eefd70d9 Mon Sep 17 00:00:00 2001
From: zhe_mstr <zhe@microstrategy.com>
Date: Tue, 11 Feb 2025 13:54:47 +0800
Subject: [PATCH 4/5] fix comments

---
 scripts/convert_title_to_sentence_case.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/convert_title_to_sentence_case.py b/scripts/convert_title_to_sentence_case.py
index 08a69901b..8abe0d7fa 100644
--- a/scripts/convert_title_to_sentence_case.py
+++ b/scripts/convert_title_to_sentence_case.py
@@ -6,7 +6,7 @@
 
 # reserved phrases dictionary, key: all lowercase letters, value: correct format
 reserved_phrases = {
-  'microstrategy': 'Strategy',
+  'microstrategy': 'MicroStrategy',
   '.microstrategy.': '.microstrategy.',
   'microstrategy.': 'microstrategy.',
   'microstrategy-rest-api-samples': 'microstrategy-rest-api-samples',

From edbc9010d2894755ed1992164779505588afb013 Mon Sep 17 00:00:00 2001
From: zhe_mstr <zhe@microstrategy.com>
Date: Tue, 11 Feb 2025 15:28:10 +0800
Subject: [PATCH 5/5] update

---
 .../manage-subscriptions/create-and-get-a-subscription.md     | 2 +-
 .../retrieve-data-from-the-intelligence-server.md             | 4 ++--
 docs/whats-new.md                                             | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
index abc1176d8..c7e752f8a 100644
--- a/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
+++ b/docs/common-workflows/administration/distribution-services/manage-subscriptions/create-and-get-a-subscription.md
@@ -321,7 +321,7 @@ Sample Request
 
   ```bash
   curl -X GET -b ~/cookie-jar.txt --header 'Accept: application/json'
-  --header 'X-MSTR-AuthToken: lb15fie86urdnsldk71a02gls2' https://demo.microstrategy.com/MicroStrategyLibrary/api/users?nameBegins=Strategy Web User&fields=name,id
+  --header 'X-MSTR-AuthToken: lb15fie86urdnsldk71a02gls2' https://demo.microstrategy.com/MicroStrategyLibrary/api/users?nameBegins=MicroStrategy Web User&fields=name,id
   ```
 
 Sample Response
diff --git a/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md b/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md
index e080e6dc0..1185fe402 100644
--- a/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md
+++ b/docs/common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md
@@ -1,6 +1,6 @@
 ---
 title: Retrieve data from the Intelligence Server using the JSON Data API
-description: You can use the Reports API, the Cubes API and the Dashboards API to retrieve definitions and data from the Intelligence Server. Together, they are often referred to as the JSON Data API. They are part of the Strategy REST Server, which is shipped inside the "StrategyLibrary.war" web application.
+description: You can use the Reports API, the Cubes API and the Dashboards API to retrieve definitions and data from the Intelligence Server. Together, they are often referred to as the JSON Data API. They are part of the Strategy REST Server, which is shipped inside the "MicroStrategyLibrary.war" web application.
 ---
 
 :::tip
@@ -11,7 +11,7 @@ Learn more about Strategy REST API Playground [here](/docs/getting-started/playg
 
 :::
 
-You can use the Reports API, the Cubes API and the Dashboards API to retrieve definitions and data from the Intelligence Server. Together, they are often referred to as the JSON Data API. They are part of the Strategy REST Server, which is shipped inside the `StrategyLibrary.war` web application.
+You can use the Reports API, the Cubes API and the Dashboards API to retrieve definitions and data from the Intelligence Server. Together, they are often referred to as the JSON Data API. They are part of the Strategy REST Server, which is shipped inside the `MicroStrategyLibrary.war` web application.
 
 :::tip
 
diff --git a/docs/whats-new.md b/docs/whats-new.md
index 4830671f5..2eee104af 100644
--- a/docs/whats-new.md
+++ b/docs/whats-new.md
@@ -211,7 +211,7 @@ The REST API has been enhanced to support the ability to pass filters into the R
 
 - The stand-alone JSON Data API Server has been removed.
 
-The [JSON Data API](common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md) is made up of four different Strategy API families. All of these families are part of the Strategy REST Server, which is shipped inside the StrategyLibrary.war web application.
+The [JSON Data API](common-workflows/analytics/retrieve-data-from-the-intelligence-server/retrieve-data-from-the-intelligence-server.md) is made up of four different Strategy API families. All of these families are part of the Strategy REST Server, which is shipped inside the MicroStrategyLibrary.war web application.
 
 ## 10.10