AdobeDocs · dshevtsov · Oct 29, 2024 · Oct 29, 2024
diff --git a/src/pages/community/best-practices.md b/src/pages/community/best-practices.md
@@ -26,8 +26,8 @@ The Adobe team verifies and provides the following best practices and recommenda
 *  [Observers Best Practices](https://developer.adobe.com/commerce/php/best-practices/extensions/observers/)
 *  [Theme Development Best Practices](https://developer.adobe.com/commerce/frontend-core/guide/best-practices/)
 *  [Performance Best Practices](https://experienceleague.adobe.com/docs/commerce-operations/performance-best-practices/overview.html)
-*  [Best Practices for Store Configuration](https://devdocs.magento.com/cloud/configure/configure-best-practices.html) for Adobe Commerce on cloud infrastructure
-*  [Deployment Process](https://devdocs.magento.com/cloud/reference/discover-deploy.html) for Adobe Commerce on cloud infrastructure
+*  [Best Practices for Store Configuration](https://experienceleague.adobe.com/en/docs/commerce-cloud-service/user-guide/configure-store/best-practices) for Adobe Commerce on cloud infrastructure
+*  [Deployment Process](https://experienceleague.adobe.com/en/docs/commerce-cloud-service/user-guide/develop/deploy/best-practices) for Adobe Commerce on cloud infrastructure
 
 ## Want to contribute?
 

diff --git a/src/pages/guides/code-contributions/backward-compatibility-policy.md b/src/pages/guides/code-contributions/backward-compatibility-policy.md
@@ -137,7 +137,7 @@ Prefix the type name with a question mark when declaring a parameter with a `nul
 ```php
 <?php
 /**
- * Copyright © Magento, Inc. All rights reserved.
+ * Copyright &copy; Magento, Inc. All rights reserved.
  * See COPYING.txt for license details.
  */
 
@@ -422,7 +422,7 @@ Deprecated code is preserved for the following time frames:
 
 ## Documentation of Backward Incompatible Changes
 
-Backward incompatible changes must be approved by an architect and documented in the scope of the task that introduces those changes.
+[Backward incompatible changes](https://developer.adobe.com/commerce/php/development/backward-incompatible-changes/) must be approved by an architect and documented in the scope of the task that introduces those changes.
 
 Examples of these tasks include:
 
@@ -439,9 +439,6 @@ These backward incompatible changes do not need manual documentation:
 -  Adding/removing a class/interface constant
 -  Adding removing a class property
 
-Auto-generated [Magento Open Source changes]https://devdocs.magento.com/guides/v2.4/release-notes/backward-incompatible-changes/reference.html)
-Auto-generated [Adobe Commerce changes](https://devdocs.magento.com/guides/v2.4/release-notes/backward-incompatible-changes/reference.html)
-
 ### Where to document
 
 In the [magento/devdocs](https://github.com/magento/devdocs) repository, manually add backward incompatible changes to the following file:

diff --git a/src/pages/guides/code-contributions/index.md b/src/pages/guides/code-contributions/index.md
@@ -37,7 +37,7 @@ Adobe and Community Maintainers process contributions based on the issue/pull re
 
 <InlineAlert variant="info" slots="text"/>
 
-**Severity** is a measure of how ‘bad’ the bug is and how much disruption it causes, without regard to remaining work or the release schedule.
+**Severity** is a measure of how 'bad' the bug is and how much disruption it causes, without regard to remaining work or the release schedule.
 
 ### Priority and severity descriptions
 
@@ -47,7 +47,7 @@ Adobe and Community Maintainers process contributions based on the issue/pull re
 | Severity: S1 | -  Affects critical data or functionality and forces users to employ a workaround.<br />-  Impact to the key product qualities.<br />-  An immediate fix is needed.<br /> |
 | Severity: S2 | -  Affects non-critical data or functionality and forces users to employ a workaround.<br />-  Impact to the product qualities that makes the product more usable.<br />-  Major restrictions or short-term circumventions are required until a fix is available. A fix is important.<br /> |
 | Severity: S3 | -  Affects non-critical data or functionality and does not force users to employ a workaround.<br />-  Problem has moderate impact requiring some restrictions. The fix is in an area that is not critical.<br /> |
-| Severity: S4 | -  A minor problem, annoyance, or technical issue with minimal impact.<br />-  Impact that does not prevent or hinder functionality.<br />-  Affects aesthetics, professional look and feel, “quality” or “usability”.<br /> |
+| Severity: S4 | -  A minor problem, annoyance, or technical issue with minimal impact.<br />-  Impact that does not prevent or hinder functionality.<br />-  Affects aesthetics, professional look and feel, "quality" or "usability".<br /> |
 
 | Priority | Description |
 | ------------- | ------------- |
@@ -344,8 +344,8 @@ To maintain an effective bug fix workflow, we ask reporters to follow some simpl
 
 Before creating an issue, do the following:
 
--  Check the [Developer Documentation](https://developer.adobe.com/commerce) and [User Guide](https://docs.magento.com/user-guide/getting-started.html) to make sure the behavior you are reporting is really a bug, not a feature.
--  Check the [existing issues](https://github.com/magento/magento2/issues) to make sure you are not duplicating somebody’s work.
+-  Check the [Developer Documentation](https://developer.adobe.com/commerce) and [User Guide](https://experienceleague.adobe.com/en/docs/commerce-admin/user-guides/home) to make sure the behavior you are reporting is really a bug, not a feature.
+-  Check the [existing issues](https://github.com/magento/magento2/issues) to make sure you are not duplicating somebody's work.
 -  Ensure that information you are reporting is a technical issue. Refer to the [Community Forums](https://community.magento.com/) or [Magento Stack Exchange](http://magento.stackexchange.com/) for technical questions, feature requests, etc.
 -  Verify that the issue you are reporting does not relate to Adobe Commerce. GitHub is intended for Magento Open Source users to report on issues related to Open Source only. You can report Commerce-related issues one of two ways:
 

diff --git a/src/pages/guides/install/change-version.md b/src/pages/guides/install/change-version.md
@@ -27,14 +27,14 @@ You have the following options:
 
 To change versions after cloning:
 
-1. Log in to your web server as, or switch to, [the file system owner](https://devdocs.magento.com/guides/v2.4/install-gde/prereq/file-sys-perms-over.html).
+1. Log in to your web server as, or switch to, [the file system owner](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/file-system/overview).
 1. Use the following command to uninstall the Magento Open Source software:
 
    ```bash
    php <your Magento clone dir>/bin/magento setup:uninstall
    ```
 
-1. Either remove your old Magento clone directory or [update the software](https://devdocs.magento.com/guides/v2.4/install-gde/install/cli/dev_update-magento.html).
+1. Either remove your old Magento clone directory or [update the software](https://experienceleague.adobe.com/en/docs/commerce-operations/upgrade-guide/developer/git-installs).
 1. If you have not already done so, clone the Magento 2 GitHub repository as follows:
 
    ```bash
@@ -53,15 +53,15 @@ To change versions after cloning:
    git checkout tags/2.2.0 -b 2.2.0
    ```
 
-1. Install the Magento Open Source software using the [command line](https://devdocs.magento.com/guides/v2.4/install-gde/install/cli/install-cli-install.html).
+1. Install the Magento Open Source software using the [command line](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/tutorials/install).
 
 ## Change versions by installing the software in a new database instance
 
 To change versions after cloning:
 
-1. Log in to your Magento server as, or switch to, [the file system owner](https://devdocs.magento.com/guides/v2.4/install-gde/prereq/file-sys-perms-over.html).
-1. Create a [new database instance](https://devdocs.magento.com/guides/v2.4/install-gde/prereq/mysql.html#instgde-prereq-mysql-config) for your installation.
-1. [Back up](https://devdocs.magento.com/guides/v2.4/install-gde/install/cli/install-cli-backup.html#instgde-cli-uninst-back) the Magento file system, database, and media files:
+1. Log in to your Magento server as, or switch to, [the file system owner](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/file-system/overview).
+1. Create a [new database instance](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/database-server/mysql) for your installation.
+1. [Back up](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/tutorials/backup) the Magento file system, database, and media files:
 
    ```bash
    php <magento_root>/bin/magento setup:backup --code --media --db
@@ -87,4 +87,4 @@ To change versions after cloning:
 
 1. Install the Magento software in your new database instance.
 
-   You must install using the [command line](https://devdocs.magento.com/guides/v2.4/install-gde/install/cli/install-cli-install.html).
+   You must install using the [command line](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/tutorials/install).
diff --git a/src/pages/guides/install/clone-repository.md b/src/pages/guides/install/clone-repository.md
@@ -9,7 +9,7 @@ keywords:
 
 You can clone the latest code from the [Magento Open Source GitHub repository](https://github.com/magento/magento2), and use code from a release branch or a development branch.
 
--  A **release branch** is a _stable_, full-featured code branch officially released with a version number, such as 2.4. You _must_ use a release branch with the [Data Migration Tool](https://devdocs.magento.com/guides/v2.4/migration/bk-migration-guide.html).
+-  A **release branch** is a _stable_, full-featured code branch officially released with a version number, such as 2.4. You _must_ use a release branch with the [Data Migration Tool](https://experienceleague.adobe.com/en/docs/commerce-operations/tools/data-migration/how-migration-works).
 
 -  A **development branch**, or feature branch, is a less-stable code branch with the latest code intended as the next version or to introduce a specific feature.
 
@@ -19,13 +19,13 @@ You can checkout a specific branch after you clone the repository to your local
 
 The Adobe Commerce repository requires authentication, so you must prepare the following:
 
--  **[Authentication key](https://devdocs.magento.com/guides/v2.4/install-gde/prereq/connect-auth.html)**—You must have an authentication key to access the Adobe Commerce Composer package on `repo.magento.com` and to enable install and update commands for your project.
+-  **[Authentication key](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/authentication-keys)**—You must have an authentication key to access the Adobe Commerce Composer package on `repo.magento.com` and to enable install and update commands for your project.
 
 -  **[GitHub personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/)**—Composer requires a _personal access token_ in the `github-oauth` property to authorize GitHub repository access. When you create this token, select all options in the `repo` scope.
 
 ## Authentication file
 
-You must create an `auth.json` file that contains your Adobe Commerce [authorization credentials](https://devdocs.magento.com/guides/v2.4/install-gde/prereq/connect-auth.html) in the Magento root directory.
+You must create an `auth.json` file that contains your Adobe Commerce [authorization credentials](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/authentication-keys) in the Magento root directory.
 
 To create an authentication file:
 

diff --git a/src/pages/guides/install/docker.md b/src/pages/guides/install/docker.md
@@ -20,6 +20,6 @@ As well as using the native installation path to set up a system with all the re
 
 The following two scenarios describe when a Docker-based environment is most useful:
 
--  For demos, Commerce Cloud compatibility testing, and basic development we recommend [Magento Cloud Docker](https://github.com/magento/magento-cloud-docker). See [Cloud Docker Development](https://devdocs.magento.com/cloud/docker/docker-development.html).
+-  For demos, Commerce Cloud compatibility testing, and basic development we recommend [Magento Cloud Docker](https://github.com/magento/magento-cloud-docker). See [Cloud Docker Development](https://developer.adobe.com/commerce/cloud-tools/docker/).
 
 -  For development, aside from Magento Cloud Docker, there are several community projects that provide a Docker environment suitable for coding, like [Docker Magento]( https://github.com/markshust/docker-magento) and [Magento2Docker](https://github.com/yvoronoy/magento2docker). Refer to each project's documentation for more details.
diff --git a/src/pages/guides/install/index.md b/src/pages/guides/install/index.md
@@ -11,12 +11,12 @@ If you are a code or documentation contributor, this install guide is for you! U
 
 <InlineAlert variant="success" slots="text"/>
 
-Are you a non-contributor? Check out our [Quick start install](https://devdocs.magento.com/guides/v2.4/install-gde/composer.html) guide. Do you have more advanced install problems to solve? Check out our [Advanced install](https://devdocs.magento.com/guides/v2.4/install-gde/install/cli/install-cli.html) guide.
+Are you a non-contributor? Check out our [Quick start install](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/composer) guide. Do you have more advanced install problems to solve? Check out our [Advanced install](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/advanced) guide.
 
 ## Intended audience
 
 The audience for this topic is anyone who contributes to the Magento Open Source codebase.
-You should be highly technical, understand Composer and Git commands, and be able to upgrade the Magento system software and extensions using those commands. If that isn't you, go back and [choose another starting point](https://devdocs.magento.com/guides/v2.4/install-gde/bk-install-guide.html).
+You should be highly technical, understand Composer and Git commands, and be able to upgrade the Magento system software and extensions using those commands. If that isn't you, go back and [choose another starting point](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/overview).
 
 <InlineAlert variant="warning" slots="text"/>
 
@@ -27,8 +27,8 @@ You cannot have a live store that accepts orders and so on.
 
 Before you continue, make sure you've done all of the following:
 
--  Set up a server that meets our [system requirements](https://devdocs.magento.com/guides/v2.4/install-gde/system-requirements.html)
--  Created the [file system owner](https://devdocs.magento.com/guides/v2.4/install-gde/prereq/file-sys-perms-over.html)
+-  Set up a server that meets our [system requirements](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/system-requirements)
+-  Created the [file system owner](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/prerequisites/file-system/overview)
 
 We use [Composer](https://getcomposer.org/) to manage Magento components and their dependencies. Using Composer to get the Magento software metapackage provides the following advantages: