From 7367b86988e34bac92daa4e11253fc651d3eca73 Mon Sep 17 00:00:00 2001
From: Dmytro Shevtsov <shevtsov@adobe.com>
Date: Thu, 12 Oct 2023 17:09:32 -0500
Subject: [PATCH] Fix docs links

---
 .github/CONTRIBUTING.md          | 2 +-
 .github/PULL_REQUEST_TEMPLATE.md | 2 +-
 README.md                        | 2 +-
 src/Util/PasswordGenerator.php   | 2 +-
 tests/README.md                  | 4 ++--
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 9af102aeb7..dc3ef9c9db 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -13,7 +13,7 @@ You must have a [GitHub account](https://help.github.com/en/github/getting-start
 
 ## Contribution requirements
 
-1. Contributions must adhere to the [Magento coding standards](https://devdocs.magento.com/guides/v2.3/coding-standards/bk-coding-standards.html).
+1. Contributions must adhere to the [Magento coding standards](https://developer.adobe.com/commerce/php/coding-standards/).
 2. When you submit a Pull request (PR), write a meaningful description to explain the purpose of your contribution. Comprehensive descriptions increase the chances that a pull request can be merged quickly, without requests for additional clarification. See the [Magento Cloud Tools Pull Request Template](https://github.com/magento/ece-tools/blob/develop/.github/PULL_REQUEST_TEMPLATE.md) for more information.
 3. Commits must be accompanied by meaningful commit messages.
 4. If your PR includes bug fixes, provide a step-by-step description of how to reproduce the bug in the pull request description.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index a37f04af25..926ef3acc4 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -34,7 +34,7 @@
 
 ### Release notes
 
-For user-facing changes, add a meaningful release note. For examples, see [Magento Cloud ECE-tools release notes](https://devdocs.magento.com/cloud/release-notes/ece-release-notes.html).
+For user-facing changes, add a meaningful release note. For examples, see [Magento Cloud ECE-tools release notes](https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/ece-tools-package.html).
 
 ### Associated documentation updates
 <!--
diff --git a/README.md b/README.md
index 51f4778e68..0019bdd935 100755
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ The Magento Cloud Suite includes a set of packages designed to deploy and manage
 
 ## Useful Resources
 - [Release Notes](https://github.com/magento/ece-tools/releases)
-- [Magento Cloud Guide DevDocs](https://devdocs.magento.com/cloud/bk-cloud.html)
+- [Magento Cloud Guide DevDocs](https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/overview.html)
 - [Cloud Knowledge Base and Support](https://support.magento.com)
 - [Cloud Slack Channel](https://magentocommeng.slack.com) (join #cloud and #cloud-docker)
 
diff --git a/src/Util/PasswordGenerator.php b/src/Util/PasswordGenerator.php
index 0fc22d104f..f821106228 100644
--- a/src/Util/PasswordGenerator.php
+++ b/src/Util/PasswordGenerator.php
@@ -45,7 +45,7 @@ public function generateRandomPassword(int $length = 20): string
     {
         while (true) {
             $password = $this->generateRandomString($length);
-            /* http://docs.magento.com/m2/ee/user_guide/stores/admin-signin.html
+            /* https://experienceleague.adobe.com/docs/commerce-admin/start/admin/admin-signin.html#admin-sign-in
              * An Admin password must be seven or more characters long, and include both letters and numbers.
              */
             if ((preg_match('/.*[A-Za-z].*/', $password)) && (preg_match('/.*[\d].*/', $password))) {
diff --git a/tests/README.md b/tests/README.md
index c7839badc1..450ac35b34 100755
--- a/tests/README.md
+++ b/tests/README.md
@@ -38,7 +38,7 @@ This test will generate a pretty report for unit test coverage.
 
 1. Run the command `composer test:coverage`
 2. Observe result in CLI output
- - Be sure to enable [xDebug](http://devdocs.magento.com/guides/v2.2/cloud/howtos/debug.html) for this test
+ - Be sure to enable [xDebug](https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/test/debug.html) for this test
 
 ## Code coverage report
 
@@ -46,7 +46,7 @@ This test will generate a pretty report for unit test coverage.
 
 1. Run the command `composer test:coverage-generate`
 2. Navigate to `tests/unit/tmp/coverage` and open `index.html` file in browser
- - Be sure to enable [xDebug](http://devdocs.magento.com/guides/v2.2/cloud/howtos/debug.html) for this test
+ - Be sure to enable [xDebug](https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/test/debug.html) for this test
 
 ## Best practices