Update _index.md

content/en/docs/apidocs-mxsdk/apidocs/_index.md

@@ -1,7 +1,7 @@
 ---
 title: "API Documentation"
 url: /apidocs-mxsdk/apidocs/
-description: "Presents an overview of the Mendix Platform API documentation, for Studio Pro, Frontend, Apps, Deployment, Governance, Marketplace, Catalog, and Private Mendix Platform APIs."
+description: "Presents an overview of the Mendix Platform API documentation, for Studio Pro, Frontend, Projects, Deployment, Governance, Marketplace, Catalog, and Private Mendix Platform APIs."
 weight: 1
 no_list: false 
 description_list: true

content/en/docs/apidocs-mxsdk/apidocs/apps/_index.md

@@ -1,12 +1,12 @@
 ---
-title: "APIs for Apps"
+title: "APIs for Projects"
 url: /apidocs-mxsdk/apidocs/apis-for-apps/
 type: swagger
 no_list: false
 description_list: true
-description: "Provides the documentation of APIs for Apps, including App Repository API, Epics API, Feedback API, Projects API, and Team Server API."
+description: "Provides the documentation of APIs for Projects, including App Repository API, Epics API, Feedback API, Projects API, and Team Server API."
 weight: 15
-linktitle: "Apps"
+linktitle: "Projects"
 ---
 
-Mendix offers the following APIs for Apps:
+Mendix offers the following APIs for Projects:

content/en/docs/apidocs-mxsdk/apidocs/apps/app-repository-api.md

@@ -107,7 +107,7 @@ Returns information about the version control repository for a Mendix app.
 
 |Name|Type|Required|Description|
 |---|---|---|---|
-|`AppId`|String|Yes|The App ID of the Mendix app for which the repository information should be returned. You can find this under **Project ID** in the [General](/developerportal/general-settings/) tab of the **Settings** page after you open your app in [Apps](https://sprintr.home.mendix.com/). |
+|`AppId`|String|Yes|The App ID of the Mendix app for which the repository information should be returned. You can find this under **Project ID** in the [General](/developerportal/general-settings/) tab of the **Settings** page after you open your app in [Projects](https://projects.home.mendix.com/). |
 
 ##### Example
 

content/en/docs/apidocs-mxsdk/apidocs/catalog/search-api.md

@@ -238,7 +238,7 @@ A successful `GET` call results in a `200` status code and a JSON response body
                 },
                 "icon": "https://catalog.mendix.com/resources/logos/other_icon.png",
                 "uuid": "1bed66d2-4477-39a9-9144-d0f848212f1e",
-                "repositoryLocation": "https://sprintr.home.mendix.com/link/project/369386df-35b4-475b-a917-17adcc81c1b5",
+                "repositoryLocation": "https://projects.home.mendix.com/link/project/369386df-35b4-475b-a917-17adcc81c1b5",
                 "businessOwner": {
                     "email": "john.doe@siemens.com",
                     "uuid": "d9d4b5bc-ffe8-4c5c-b237-7358d01f7981",

content/en/docs/apidocs-mxsdk/apidocs/deployment/deploy-api-1.md

@@ -70,7 +70,7 @@ In the Mendix Portal:
 
 * The [Nodes](/developerportal/deploy/node-permissions/#nodes) screen in the Mendix Portal shows all the licensed apps which are returned by this request, but does not show any Free Apps.
 
-* The [My Apps](/developerportal/#my-apps) screen shows both licensed apps and Free Apps, but also includes apps that are deployed to other platforms (such as Mendix on Kubernetes or SAP BTP) and Free Apps that have not yet been deployed and therefore have no environments set up for them.
+* The [My Projects](/developerportal/#my-apps) screen shows both licensed apps and Free Apps, but also includes apps that are deployed to other platforms (such as Mendix on Kubernetes or SAP BTP) and Free Apps that have not yet been deployed and therefore have no environments set up for them.
 {{% /alert %}}
 
 ```bash

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/sdk-old-versions-howtos/old-creating-your-first-script.md

@@ -142,6 +142,6 @@ The steps for app creation (line 3) and committing to the Team Server (line 10)
 
 ## Opening the App in Studio Pro
 
-1. In [Apps](/developerportal/#my-apps), verify the app you just created is visible at the top of the list.
+1. In [Projects](/developerportal/#my-apps), verify the app you just created is visible at the top of the list.
 2. Open the new app, and on the right side, click **Edit**.
 3. If you have the latest [Mendix Studio Pro](https://marketplace.mendix.com/link/studiopro/), it will start and load the app you just created from the Team Server.

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/using-platform-sdk.md

@@ -66,7 +66,7 @@ const app = client.getApp("33118fbf-7053-482a-8aff-7bf1c626a6d9");
 ```
 
 {{% alert color="info" %}}
-You can get the **App ID** (represented as **Project ID**) in the app's [Settings](/developerportal/general-settings/) page after opening your app in **Apps**.
+You can get the **App ID** (represented as **Project ID**) in the app's [Settings](/developerportal/general-settings/) page after opening your app in **Projects**.
 {{% /alert %}}
 
 ## Getting Information About the Repository of the App {#getting}

content/en/docs/catalog/register/automate-registration.md

@@ -25,7 +25,7 @@ Before you begin, make sure you have the following:
 
 A file called *dependencies.json* lists all published and consumed services in your app. This file contains information you will need to make the API calls in the next steps.
 
-Create an `.mda` package that includes *dependencies.json*. Open your app in [Apps](https://sprintr.home.mendix.com/), go to the **Environments** page and then click **Create Package** From Team server, or run `mxbuild` (see [MxBuild](/refguide/mxbuild/) for information on how to build a Mendix Deployment Package).
+Create an `.mda` package that includes *dependencies.json*. Open your app in [Projects](https://projects.home.mendix.com/), go to the **Environments** page and then click **Create Package** From Team server, or run `mxbuild` (see [MxBuild](/refguide/mxbuild/) for information on how to build a Mendix Deployment Package).
 
 You can also find *dependencies.json* in **Deployment** > **Model** folder of your Mendix application. 
 

content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide.md

@@ -33,11 +33,11 @@ This guide does not give insights into the product roadmap or internal company o
 
 These are branded Mendix product names. However, they do not always need "Mendix" in front of them in the documentation.
 
-### Apps
+### Projects
 
 Refers to a section of the Mendix Portal. Capitalize in all instances (when used in this context rather than as the plural of "app").
 
-This term replaces "Developer Portal", "Sprintr", "Platform Portal," and "Mendix App Platform." These terms are not to be used in the product UI or documentation.
+This term replaces "Developer Portal", "Sprintr", "Platform Portal," "Mendix App Platform", and "Apps". These terms are not to be used in the product UI or documentation.
 
 ### Mendix on Kubernetes
 
@@ -93,7 +93,7 @@ This is a product name, so don't add a definite article.
 
 ### Mendix Platform
 
-Describes Mendix as a product and encompasses all the products released by Mendix (as in, Studio Pro, Apps, etc.).
+Describes Mendix as a product and encompasses all the products released by Mendix (as in, Studio Pro, Projects, etc.).
 
 Capitalize "Platform" when used in "Mendix Platform."
 
@@ -105,7 +105,7 @@ It is fine to use "the Mendix Platform," but do not use "the Platform" (or "the
 
 ### Mendix Portal
 
-The Mendix Portal includes Apps (which replaces "Developer Portal"), Control Center, the Mendix Community, Mendix Marketplace, Catalog, and Mendix Support.
+The Mendix Portal includes Projects (which replaces "Developer Portal" and "Apps"), Control Center, the Mendix Community, Mendix Marketplace, Catalog, and Mendix Support.
 
 ### Mendix Studio Pro
 
@@ -142,7 +142,7 @@ Does not need to be capitalized, and "team" should be used without the qualifier
 
 ### app template
 
-This is the term to use to reflect the create-new-app flow UI in Apps.
+This is the term to use to reflect the create-new-app flow UI in Projects.
 
 Do not use "starter app."
 

content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/terminology.md

@@ -149,7 +149,7 @@ Write as one word.
 
 ## deploy
 
-The act of putting a Mendix app into an environment where it has access to all the resources it needs to run. This is triggered in Apps, or in Studio Pro by clicking **Run** or **Run Locally**.
+The act of putting a Mendix app into an environment where it has access to all the resources it needs to run. This is triggered in Projects, or in Studio Pro by clicking **Run** or **Run Locally**.
 
 Use *deploy to* when referring to a cloud environment.
 
@@ -325,11 +325,11 @@ Use lower-case unless it is part of a term like "Mendix Native Mobile Builder".
 
 ## navigation pane
 
-Use to refer to the navigation interface on the left side of the screen in Apps.
+Use to refer to the navigation interface on the left side of the screen in Projects.
 
 Do not capitalize.
 
-> Select your app in Apps, then click **Backups** in the navigation pane.
+> Select your app in Projects, then click **Backups** in the navigation pane.
 
 ## no-code, no code
 
@@ -461,7 +461,7 @@ When referring to an action which is taking place, use "sign in" and "sign out"
 
 When referring to a button or other element of the UI, refer to the UI text.
 
-> Sign out of Apps by clicking **Log out** in the menu under your avatar.
+> Sign out of Projects by clicking **Log out** in the menu under your avatar.
 
 ## single sign-on
 

content/en/docs/control-center/apps/apps-overview.md

@@ -14,7 +14,7 @@ aliases:
 
 The **Apps** page in Control Center provides a central place to monitor, manage, and interact with all the apps belonging to your company. 
 
-Use the search bar at the top of the page to find an app using either its name or app ID. You can find the app ID under **Project ID** in your app’s [Settings](/developerportal/general-settings/) in [Apps](https://sprintr.home.mendix.com/).
+Use the search bar at the top of the page to find an app using either its name or app ID. You can find the app ID under **Project ID** in your app’s [Settings](/developerportal/general-settings/) in [Projects](https://projects.home.mendix.com/).
 
 {{< figure src="/attachments/control-center/apps/apps-overview/top-search-bar.png" >}}
 
@@ -142,7 +142,7 @@ The consequences of deactivating and deleting a free app are as follows:
 | App code repository stays persistent                        | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="remove-circle-filled" color="red" >}} |
 | App team members can access the app code repository         | {{< icon name="remove-circle-filled" color="red" >}} | {{< icon name="remove-circle-filled" color="red" >}} |
 | App stays persistent                                        | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="remove-circle-filled" color="red" >}} |
-| App team members can access the app in [Apps](https://sprintr.home.mendix.com/) | {{< icon name="remove-circle-filled" color="red" >}} | {{< icon name="remove-circle-filled" color="red" >}} |
+| App team members can access the app in [Projects](https://projects.home.mendix.com/) | {{< icon name="remove-circle-filled" color="red" >}} | {{< icon name="remove-circle-filled" color="red" >}} |
 | Cloud environment stays persistent                          | {{< icon name="remove-circle-filled" color="red" >}} | {{< icon name="remove-circle-filled" color="red" >}} |
 
 {{% alert color="info" %}}

content/en/docs/control-center/resolve-shared-ownership-apps.md

@@ -31,7 +31,7 @@ To resolve this issue, do one of the following:
 
 ### You Own the Node, but Not the App
 
-If an app does not appear in **Apps**, but appears in [Deployed Apps](/control-center/deployed-apps/), or [Cloud](/control-center/cloud/#paid-environments) if you cannot access **Deployed Apps**, this means that you own the node but not the app.
+If an app does not appear in **Apps**, but it appears in [Deployed Apps](/control-center/deployed-apps/), or [Cloud](/control-center/cloud/#paid-environments) if you cannot access **Deployed Apps**, this means that you own the node but not the app.
 
 To resolve this issue, do one of the following:
 

content/en/docs/control-center/security/software-composition/_index.md

@@ -2,7 +2,7 @@
 title: "Software Composition"
 linktitle: "Software Composition"
 url: /control-center/software-composition/
-description: "Describes the Software Composition page in the Mendix Control Center."
+description: "Describes the Software Composition page in Mendix Control Center."
 weight: 20
 ---
 
@@ -50,7 +50,7 @@ A software bill of materials (SBOM) is generated in the following circumstances:
 
 Click **View build output** in the deployment package details in the Mendix Portal to open the log details. For more information on SBOM generation, refer to [SBOM Generation](/refguide/sbom-generation/).
 
-You can find the component dependencies for each non-expired deployment package in the [Software Composition](/developerportal/deploy/software-composition/) page of **Apps** in the Mendix Portal. 
+You can find the component dependencies for each non-expired deployment package in the [Software Composition](/developerportal/deploy/software-composition/) page of **Projects** in Mendix Portal. 
 
 After you create a deployment package, the **Software Composition** page usually becomes visible within a few minutes. However, in rare cases, it can take up to a day. Mendix is working to improve performance.
 

content/en/docs/deployment/general/mendix-pipelines/_index.md

@@ -17,7 +17,7 @@ Once designed and activated from the **Pipelines** page, you can enable automate
 Mendix Pipelines is only available for licensed Mendix apps that are deployed to Mendix Cloud, Mendix on Kubernetes or Mendix on Azure.
 {{% /alert %}}
 
-To access the **Pipelines** page, open your app in [Apps](https://sprintr.home.mendix.com/). Then select **Pipelines** in the navigation pane. (To view this page, you must have a [role](/developerportal/general/team/) with cloud access.)
+To access the **Pipelines** page, open your app in [Projects](https://projects.home.mendix.com/). Then select **Pipelines** in the navigation pane. (To view this page, you must have a [role](/developerportal/general/team/) with cloud access.)
 
 The **Pipelines** page has four tabs: **Runs**, **Designs**, **Variables**, and **Settings**. You can see all four tabs as soon as your app has its first Mendix Pipeline saved.
 

content/en/docs/deployment/general/software-composition.md

@@ -2,7 +2,7 @@
 title: "Software Composition"
 linktitle: "Software Composition"
 url: /developerportal/deploy/software-composition/
-description: "Describes the Software Composition page in Apps."
+description: "Describes the Software Composition page in Projects."
 weight: 80
 ---
 
@@ -12,7 +12,7 @@ A Mendix app can consist of the Mendix Model (which includes pages, domain model
 
 Over time, these dependencies can become deprecated, outdated, or vulnerable. Enterprises also have policies on which of these reusable components can or cannot be used based on support, license, etc. It is important to have an easily accessible, clear view of component dependencies through the development lifecycle in order to address any security finding raised by your admins or security teams.  
 
-To enable this, the **Software Composition** page in **Apps** provides visibility into the component dependencies of each deployment package. The components displayed here will be based on the [Software Bill of Materials (SBOM)](/refguide/sbom-generation/).
+To enable this, the **Software Composition** page in **Projects** provides visibility into the component dependencies of each deployment package. The components displayed here will be based on the [Software Bill of Materials (SBOM)](/refguide/sbom-generation/).
 
 The **Software Composition** page is visible to all members of the Mendix app.
 
@@ -49,7 +49,7 @@ Components are identified in the following manner:
 
 First, when a new deployment package is created via the Mendix Portal with the compatible Mendix Runtime version, a software bill of materials (SBOM) is generated along with it. The log details can be viewed by clicking **View build output** in the deployment package details in the Mendix Portal. For details on SBOM generation, see [SBOM Generation](/refguide/sbom-generation/).
 
-The component dependencies for each non-expired deployment package are available in the **Software Composition** page in **Apps**. 
+The component dependencies for each non-expired deployment package are available in the **Software Composition** page in **Projects**. 
 
 After the creation of a deployment package, the **Software Composition** page usually becomes visible within a few minutes. However, in rare cases, it can take up to a day. Mendix is working to improve the performance on this front.
 

content/en/docs/deployment/general/two-factor-authentication.md

@@ -10,7 +10,7 @@ description: "Describes the purpose and functionality of 2FA in the Mendix Porta
 
 Mendix Cloud provides two-factor authentication (2FA) to help secure your account. 2FA requires you to identify yourself using your password as well as a second authentication mechanism.
 
-This extra layer of authentication is required when you perform sensitive activities on Mendix Cloud nodes, such as deploying packages and handling production data. Actions that require 2FA are indicated by a padlock ({{% icon name="lock" %}}) in [Apps](https://sprintr.home.mendix.com). For example, switching to the production environment requires 2FA.
+This extra layer of authentication is required when you perform sensitive activities on Mendix Cloud nodes, such as deploying packages and handling production data. Actions that require 2FA are indicated by a padlock ({{% icon name="lock" %}}) in [Projects](https://projects.home.mendix.com). For example, switching to the production environment requires 2FA.
 
 {{< figure src="/attachments/deployment/general/two-factor-authentication/production.png" max-width=30% alt="" class="no-border" >}}
 

content/en/docs/deployment/general/webhooks.md

@@ -28,7 +28,7 @@ Webhooks are only available for licensed Mendix apps that are deployed to Mendix
 
 To set up a webhook, do the following:
 
-1. Open your app in [Apps](https://sprintr.home.mendix.com/).
+1. Open your app in [Projects](https://projects.home.mendix.com/).
 1. From the navigation pane, open the **Webhooks** page. On this page, you can see any current webhooks. You can also see whether each webhook is active or inactive. An inactive webhook does not send any payloads to the endpoint.
 1. Click **New Webhook**.
 1. Enter the following information:

content/en/docs/deployment/mendix-cloud-deploy/_index.md

@@ -61,7 +61,7 @@ This section outlines the different ways Free Apps can be deleted from the Mendi
 
 As a [Technical Contact](/developerportal/general/app-roles/#technical-contact) you can manually delete a Free App after publishing it from Studio Pro by following these steps:
 
-1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app.
+1. From [Projects](https://projects.home.mendix.com), go to the **Environments** page of your app.
 2. Click **More Options** ({{< icon name="three-dots-menu-horizontal" >}}) on the **Sandbox** environment.
 3. Click **Delete**.