Fix docs

Replace old devdocs links
Fix Markdown according to the DevSite docs rules

.github/CONTRIBUTING.md

@@ -2,7 +2,7 @@
 
 Contributions to the Magento 2 codebase are done using the fork & pull model.
 This contribution model has contributors maintaining their own fork of the Magento 2 repository.
-The forked repository is then used to submit a request to the base repository to “pull” a set of changes.
+The forked repository is then used to submit a request to the base repository to "pull" a set of changes.
 For more information on pull requests please refer to [GitHub Help](https://help.github.com/articles/about-pull-requests/).
 
 Contributions can take the form of new components or features, changes to existing features, tests, documentation (such as developer guides, user guides, examples, or specifications), bug fixes or optimizations.
@@ -19,11 +19,11 @@ For more detailed information on contribution please read our [beginners guide](
 2. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request being merged quickly and without additional clarification requests.
 3. Commits must be accompanied by meaningful commit messages. Please see the [Magento Pull Request Template](https://github.com/magento/magento2/blob/HEAD/.github/PULL_REQUEST_TEMPLATE.md) for more information.
 4. PRs which include bug fixes must be accompanied with a step-by-step description of how to reproduce the bug.
-3. PRs which include new logic or new features must be submitted along with:
-* Unit/integration test coverage
-* Proposed [documentation](https://devdocs.magento.com) updates. Documentation contributions can be submitted via the [devdocs GitHub](https://github.com/magento/devdocs).
-4. For larger features or changes, please [open an issue](https://github.com/magento/magento2/issues) to discuss the proposed changes prior to development. This may prevent duplicate or unnecessary effort and allow other contributors to provide input.
-5. All automated tests must pass.
+5. PRs which include new logic or new features must be submitted along with:
+   * Unit/integration test coverage
+   * 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, please [open an issue](https://github.com/magento/magento2/issues) to discuss the proposed changes prior to development. This may prevent duplicate or unnecessary effort and allow other contributors to provide input.
+7. All automated tests must pass.
 
 ## Contribution process
 

app/code/Magento/Elasticsearch/README.md

@@ -14,7 +14,7 @@ For information about a module installation in Magento 2, see [Enable or disable
 
 ## Structure
 
-`ElasticAdapter/` - the directory that contains the core files for providing support to ElasticSearch 7.x and 8.x 
+`ElasticAdapter/` - the directory that contains the core files for providing support to ElasticSearch 7.x and 8.x
 version.
 
 `SearchAdapter/` - the directory that contains solutions for adapting ElasticSearch query searching.

app/code/Magento/OfflineShipping/Model/ResourceModel/Carrier/Tablerate.php

@@ -295,7 +295,6 @@ class Tablerate extends \Magento\Framework\Model\ResourceModel\Db\AbstractDb
      * @return Tablerate
      * @throws LocalizedException
      * @todo: this method should be refactored as soon as updated design will be provided
-     * @see https://wiki.corp.x.com/display/MCOMS/Magento+Filesystem+Decisions
      */
     public function uploadAndImport(DataObject $object)
     {

app/code/Magento/OrderCancellation/README.md

@@ -5,5 +5,3 @@ This module allows to cancel an order and specify the order cancellation reason.
 This functionality is enabled / disabled by a feature flag that is set at storeView level.
 
 After the cancellation, the customer receive an email confirming it and this cancellation is reflected in the customer's order history.
-
-

app/code/Magento/ReleaseNotification/README.md

@@ -74,4 +74,4 @@ A clickable link to internal or external content in any text field will be creat
 
 #### Link Format Example:
 
-The text: `https://devdocs.magento.com/ [Magento DevDocs].` will appear as [Magento DevDocs](https://devdocs.magento.com/).
+The text: `https://developer.adobe.com/commerce/docs/ [Adobe Commerce Developer Documentation].` will appear as [Adobe Commerce Developer Documentation](https://developer.adobe.com/commerce/docs/).