Merge branch 'develop' into MCLOUD-8958

Author: andriyShevtsov

.github/CONTRIBUTING.md

@@ -13,16 +13,17 @@ 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 [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.
-3. If your PR includes new logic or new features, you must also submit the following information along with the pull request
+5. If your PR includes new logic or new features, you must also submit the following information along with the pull request
    * Unit/integration test coverage
-   * Proposed documentation updates: Submit developer documentation contributions to the [Magento DevDocs repository](https://github.com/magento/devdocs/blob/master/.github/CONTRIBUTING.md). Submit updates to Magento user documentation to the [Magento Merchant documentation repository](https://github.com/magento/merchdocs/blob/master/.github/CONTRIBUTING.md).
-4. For larger features or changes, [open an issue](https://github.com/magento/ece-tools/issues/new) to discuss the proposed changes prior to development. Discussing the updates in advance can prevent duplicate or unnecessary effort and allow other contributors to provide input.
+   * Proposed [documentation](https://developer.adobe.com/commerce) updates. Use feedback buttons __Edit in GitHub__ and __Log an issue__ at the top of a relevant topic.
+6. For larger features or changes, [open an issue](https://github.com/magento/ece-tools/issues/new) to discuss the proposed changes prior to development. Discussing the updates in advance can prevent duplicate or unnecessary effort and allow other contributors to provide input.
 
 ## Contribution process
+
 1. Search current [listed issues](https://github.com/magento/ece-tools/issues) (open or closed) for similar proposals of intended contribution before starting work on a new contribution.
 2. Review and sign the [Contributor License Agreement (CLA)](https://opensource.adobe.com/cla.html) if this is your first time contributing. You only need to sign the CLA once.
 3. Create and test your work.

.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
 <!--

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)
 

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))) {

tests/README.md

@@ -38,15 +38,15 @@ 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
 
 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