Merge branch 'master' into imported-misuadobe-devdocs-9328

Author: jeff-matthews

src/_data/core-releases.json

@@ -111,7 +111,7 @@
                 "tagName":"2.3.0"
             }
         ],
-        "end-of-support": "2022-04-??"
+        "end-of-support": "2022-09-08"
     },
     "2.2": {
         "releases": [

src/_includes/config/redis-verify.md

@@ -52,7 +52,7 @@ If you use Redis for page caching, you'll see output similar to the following:
 
 ### Inspecting compressed data
 
-To inspect compressed Session data and Page Cache, the [Redis Desktop Manager](https://flathub.org/apps/details/dev.rdm.RDM) supports the automatic decompression of Magento 2 Session and Page cache and displays PHP session data in a human-readable form.
+To inspect compressed Session data and Page Cache, the [RESP.app](https://flathub.org/apps/details/app.resp.RESP) supports the automatic decompression of Magento 2 Session and Page cache and displays PHP session data in a human-readable form.
 
 ### Redis ping command
 

src/cloud/cdn/cloud-vcl-custom-snippets.md

@@ -241,7 +241,7 @@ Use the Fastly API [create snippet](https://docs.fastly.com/api/config#snippet_4
 curl -H "Fastly-Key: $FASTLY_API_TOKEN" https://api.fastly.com/service/$FASTLY_SERVICE_ID/version/$FASTLY_EDIT_VERSION/snippet -H 'Content-Type: application/json' -X POST --data @<filename.json>
 ```
 
-The `<filename.vcl>` is the name of the file you prepared in the previous step. Repeat this command for each VCL snippet.
+The `<filename.json>` is the name of the file you prepared in the previous step. Repeat this command for each VCL snippet.
 
 If you receive a `500 Internal Server Error` response from the Fastly service, check the JSON file syntax to make sure you are uploading a valid file.
 

src/cloud/project/log-locations.md

@@ -19,14 +19,7 @@ You can view the logs from the file system, the project web UI, and the `magento
 -  **Magento Cloud CLI**—You can view logs using the `magento-cloud log` command.
 
 {:.bs-callout-tip}
-For Pro environments, automatic log rotation, compression, and removal are enabled for log files with a fixed file name. Each log file type has a rotating pattern and lifetime. Starter environments do not have log rotation.
-
-Full details of the environment's log rotation and lifespan of compressed logs can be found in the following locations :
-
-```terminal
-/etc/logrotate.conf
-/etc/logrotate.d/<various>
-```
+For Pro environments, automatic log rotation, compression, and removal are enabled for log files with a fixed file name. Each log file type has a rotating pattern and lifetime. Starter environments do not have log rotation. Full details of the environment's log rotation and lifespan of compressed logs can be found in: `/etc/logrotate.conf` and `/etc/logrotate.d/<various>`
 
 ## Manage log data
 

src/cloud/project/new-relic.md

@@ -43,7 +43,7 @@ The aggregated data includes information from the following logs:
 -  Logs for cloud services from the `var/log/platform/<project-ID>` directory
 -  Fastly CDN and WAF logs
 
-As soon as your project is connected to New Relic, you can use the New Relic Logs service to complete tasks like the following:
+When your project is connected to New Relic, you can use the New Relic Logs service to complete tasks like the following:
 
 -  Use [New Relic queries][New Relic query syntax for logs] to search aggregated log data
 -  Visualize log data through the New Relic Logs application
@@ -59,9 +59,9 @@ When Adobe provisions your {{site.data.var.ece}} project, the License Owner rece
 A New Relic account can have only one person assigned to the Owner role. If you must change the account owner, assign the Admin role to the current Owner, then assign the Owner role to another user. See [Update the account owner] in the New Relic documentation for instructions.
 
 {:.bs-callout-tip}
-Before assigning the Owner role to a user, verify that the user exists on the New Relic account for {{site.data.var.ece}}. If you need to add the user to that account and an existing account Owner or Admin cannot help, any user with access to the [Adobe Partnership Owner Account] for New Relic can add users on behalf of the customer.
+Before assigning the Owner role to a user, verify that the user exists on the New Relic account for {{site.data.var.ece}}. If you must add the user to that account and an existing account Owner or Admin cannot help, any user with access to the [Adobe Partnership Owner Account] for New Relic can add users on behalf of the customer.
 
-We recommend adding at least one Admin user to your New Relic account to manage all access, integrations, and tool usage. {{site.data.var.ece}} Project Owners and Admin users can add and remove users from the New Relic account.
+We recommend adding at least one **Admin** user to your New Relic account to manage all access, integrations, and tool usage. {{site.data.var.ece}} Project Owners and Admin users can add and remove users from the New Relic account. We also recommend that you do not create more than five full-access **Users**. Only grant full access to users that strictly require access to the complete feature set. There is no specific guidance on free **Restricted** users.
 
 {:.procedure}
 To add a user:

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

@@ -3,7 +3,6 @@ group: software-update-guide
 title: Commerce upgrade overview
 functional_areas:
   - Upgrade
-redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/overview.html
 ---
 
 <!-- Topic variables

src/guides/v2.3/comp-mgr/cli/cli-rc1-samp.md

@@ -3,7 +3,6 @@ group: software-update-guide
 title: Command-line upgrade with sample data
 functional_areas:
   - Upgrade
-redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html
 ---
 
 {%include install/sampledata/sample-data-rc1-cli.md %}

src/guides/v2.3/comp-mgr/cli/cli-upgrade.md

@@ -3,7 +3,6 @@ group: software-update-guide
 title: Upgrade Commerce
 functional_areas:
   - Upgrade
-redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html
 ---
 
 <!-- Topic variables

src/guides/v2.3/comp-mgr/cli/dev_update-magento.md

@@ -5,7 +5,6 @@ functional_areas:
   - Upgrade
 redirect_from:
   - guides/v2.3/install-gde/install/cli/dev_update-magento.html
-redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/developer/git-installs.html
 ---
 
 This topic discusses how a contributing developer can update Magento without reinstalling it. To perform an upgrade if you're *not* a contributing developer, see [Updating the Magento application and components](https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/overview.html).

src/guides/v2.3/comp-mgr/manage-module.md

@@ -3,7 +3,6 @@ group: software-update-guide
 title: Manage modules
 functional_areas:
   - Upgrade
-redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/modules/manage.html
 ---
 
 You must use the command line to manage Magento modules.