MC-40585: Removed acronym SUT entries and changed naming convention for the Upgrade Compability Tool (#8553)

* removed acronym SUT entries, changed naming convention to upgrade compatibility tool in all areas of docs

* Modified commands with uct instead of sut

* Fixed page-header.html

* Fixed topic after technical ENG review

* Removed link to tools repo

* Fixed linting issues appear after pulling from master

* Removed mentions to Magento Upgrade Compatibility Tool as per email from Surya

* Fixed linting issues

* Fixed -m command information

* Fixed internal linking

* Reviewed section about -m command option

* Reviewed whats new

Author: danidelcar

src/_data/toc/software-update-guide.yml

@@ -21,26 +21,26 @@ pages:
         - label: Update and upgrade checklist
           url: /comp-mgr/prereq/prereq_compman-checklist.html
 
-    - label: Safe Upgrade Tool
-      url: /safe-upgrade-tool/introduction.html
+    - label: Upgrade Compatibility Tool
+      url: /upgrade-compatibility-tool/introduction.html
       versionless: true
       edition: ee-only
       children:
 
         - label: Prerequisites
-          url: /safe-upgrade-tool/prerequisites.html
+          url: /upgrade-compatibility-tool/prerequisites.html
           versionless: true
 
         - label: Install
-          url: /safe-upgrade-tool/install.html
+          url: /upgrade-compatibility-tool/install.html
           versionless: true
 
         - label: Run the tool
-          url: /safe-upgrade-tool/run.html
+          url: /upgrade-compatibility-tool/run.html
           versionless: true
 
         - label: Developer information
-          url: /safe-upgrade-tool/developer.html
+          url: /upgrade-compatibility-tool/developer.html
           versionless: true
 
     - label: Magento Marketplace example

src/_data/whats-new.yml

@@ -30,7 +30,7 @@ entries:
   link: https://github.com/magento/devdocs/pull/8547
   contributor: dobooth
   profile: https://github.com/dobooth
-- description: Added the [Safe Upgrade Tool](https://devdocs.magento.com/safe-upgrade-tool/introduction.html)
+- description: Added the [Upgrade Compatibility Tool](https://devdocs.magento.com/upgrade-compatibility-tool/introduction.html)
     topics to the Software Update Guide section.
   versions: ''
   type: Major Update, New Topic

src/_includes/layout/page-header.html

@@ -42,9 +42,9 @@ <h2 class="page-subtitle no_toc">{{ page.subtitle }}</h2>
   </div>
   {% endif %}
 
-  {% if page.url contains "safe-upgrade-tool/" %}
+  {% if page.url contains "upgrade-compatibility-tool/" %}
   <div class="message-banner">
-    This tool is an ALPHA version with limited scope, available for all Magento Commerce merchants, and only validating PHP Magento APIs and GraphQL schema. If you are a Magento Commerce user you can download it at the <a href="https://repo.magento.com/">Magento repo</a>.
+    The Upgrade Compatibility Tool is an ALPHA version with limited scope, available for all Magento Commerce merchants, and only validating PHP Magento APIs and GraphQL schema. If you are a Magento Commerce user you can download it at the <a href="https://repo.magento.com/">Magento repo</a>.
   </div>
   {% endif %}
 

src/guides/v2.3/comp-mgr/bk-compman-upgrade-guide.md

@@ -54,7 +54,7 @@ Related topics
 Complete the tasks discussed in [Prerequisites].
 
  {:.bs-callout-info}
-See the [Safe Upgrade Tool ALPHA]({{site.baseurl}}/safe-upgrade-tool/introduction.html) for more information about the new Magento CLI tool that helps you update your Magento software.
+See the [Upgrade Compatibility Tool ALPHA]({{site.baseurl}}/upgrade-compatibility-tool/introduction.html) page for more information about the new Magento command line tool that helps you update your Magento software.
 
 <!-- ABBREVIATIONS -->
 

src/guides/v2.3/extension-dev-guide/framework/datetime.md

@@ -48,4 +48,5 @@ use Magento\Framework\Stdlib\DateTime;
     {
     return $this->dataTime->formatDate(time());
     }
+...
 ```

src/guides/v2.4/comp-mgr/bk-compman-upgrade-guide.md

@@ -49,7 +49,7 @@ Related topics
 Complete the tasks discussed in [Prerequisites].
 
  {:.bs-callout-info}
-See the [Safe Upgrade Tool ALPHA]({{site.baseurl}}/safe-upgrade-tool/introduction.html) for more information about the new Magento CLI tool that helps you update your Magento software.
+See the [Upgrade Compatibility Tool ALPHA]({{site.baseurl}}/upgrade-compatibility-tool/introduction.html) page for more information about the new Magento command line tool that helps you update your Magento software.
 
 <!-- ABBREVIATIONS -->
 

src/safe-upgrade-tool/install.md

@@ -6,25 +6,25 @@ functional_areas:
   - Upgrade
 ---
 
-This topic contains information for developers who want to know more technical information about the Magento Safe Upgrade Tool ALPHA (SUT). It is focused on developers who work closely with the Magento source code. You can use this knowledge to customize the SUT's components.
+This topic contains information for developers who want to know more technical information about the Upgrade Compatibility Tool ALPHA. It is focused on developers who work closely with the Magento source code. You can use this knowledge to customize the tool's components.
 
 ## Magento API index integration
 
 Magento API index integration is an internal integration solution that comprehends a set of tools to explore Magento Extensions developed by Magento, an Adobe Company, Magento Partners and 3rd party vendors based on static code analysis.
 
 The integration with Magento API index is done through:
 
-`Sut\Domain\MRay\MRayInterface`
+`sut\Domain\MRay\MRayInterface`
 
 It is implemented through the `config/services.yaml` file. Its value decides where the response of methods `api()` and `modules()` comes from.
 
-Edit this file to customize the response according to your installation. Just replace the value assigned to `Sut\Domain\MRay\MRayInterface`:
+Edit this file to customize the response according to your installation. Just replace the value assigned to `sut\Domain\MRay\MRayInterface`:
 
 ### Example of a custom value
 
-`Sut\Domain\MRay\MRayInterface : "@sut_mray_mock"`
+`sut\Domain\MRay\MRayInterface : "@sut_mray_mock"`
 
-In the previous example, the SUT uses `@sut_mray_mock` as the `MRayInterface` implementation. The responses from the `api()` and `modules()` methods come from the following files:
+In the previous example, the Upgrade Compatibility Tool uses `@sut_mray_mock` as the `MRayInterface` implementation. The responses from the `api()` and `modules()` methods come from the following files:
 
 *  `dev/mray_mock_files/api.json`
 *  `dev/mray_mock_files/modules.json`
@@ -59,7 +59,7 @@ To run the integration tests, execute one of the following commands:
 
 ## JS unit testing for GraphQL
 
-We used the [Jest](https://jestjs.io/docs/en/getting-started.html) framework to create these JS unit tests:
+The [Jest](https://jestjs.io/docs/en/getting-started.html) framework was used to create these JS unit tests:
 
 {:.bs-callout-info}
 To run JS unit tests for GraphQL, you must have Node.js installed.
@@ -99,7 +99,7 @@ This score is based on the results extracted from the analysis:
 *  Number of issues identified
 *  Severity of issues identified
 
-The SUT calculates this score according to the following formula:
+The Upgrade Compatibility Tool calculates this score according to the following formula:
 
 ### Complexity score formula