MCLOUD-3180 update the Configuration management topic (#7147)

* MCLOUD-3180 update the Configuration management topic

fixed broken links due to extensive updates

* Update sens-data-over.md

* additional tidbits

Co-authored-by: Margaret Eker <[email protected]>

Author: hguthrie

src/cloud/cdn/trouble-fastly.md

@@ -270,7 +270,7 @@ Based on the status returned, use the following instructions to update the Fastl
 
 -  `Module is disabled`—If the Fastly module is disabled, update the environment configuration on an Integration branch in your local environment to enable it. Then, push the changes to Staging and Production. See [Manage extensions]({{ site.baseurl }}/cloud/howtos/install-components.html).
 
-   If you use [Configuration Management]({{site.baseurl}}/cloud/live/sens-data-over.html#cloud-config-specific-recomm), check the Fastly CDN module status in the `app/etc/config.php` configuration file before you push changes to the Production or Staging environment.
+   If you use [Configuration Management]({{site.baseurl}}/cloud/live/sens-data-over.html), check the Fastly CDN module status in the `app/etc/config.php` configuration file before you push changes to the Production or Staging environment.
 
    If the module is not enabled (`Fastly_CDN => 0`) in the `config.php` file, delete the file and run the following command to update `config.php` with the latest configuration settings.
 

src/cloud/live/sens-data-initial.md

@@ -8,7 +8,7 @@ functional_areas:
 
 Configuration management exports your configurations to a file for pushing across your environments. This file, `config.php`, keeps your configurations consistent across all environments, decreases downtime by moving static deploy to build, and much more. This information details an example for configuring your settings, exporting the file, and deploying it.
 
-This example shows how to use the [recommended procedure]({{ site.baseurl }}/cloud/live/sens-data-over.html#cloud-config-specific-recomm) for managing the configuration:
+This example shows how to use the [recommended procedure]({{ site.baseurl }}/cloud/live/sens-data-over.html) for managing the configuration:
 
 1. Enter your configurations in your Integration environment Admin panel.
 1. Create `config.php` and transfer it to your local system.
@@ -45,7 +45,7 @@ To complete these configuration management tasks, you need the following:
 
 ## Configure Magento through the Integration Admin panel {#configure}
 
-Log into the Magento Admin panel in Integration to modify configurations. For a list of settings, see [List of system-specific configuration settings]({{ site.baseurl }}/cloud/live/sens-data-over.html#cloud-clp-settings) for details.
+In the Integration environment, you can log in to the Magento Admin panel to modify system configuration settings for stores, websites, modules or extensions, static file optimization, and system values related to static content deployment. See [Configuration data]({{ site.baseurl }}/cloud/live/sens-data-over.html#configuration-data).
 
 To change locale and static file optimization settings:
 
@@ -75,7 +75,7 @@ To change locale and static file optimization settings:
 
 This step creates and transfers the `config.php` configuration file on the Integration environment using a command you run on your local machine.
 
-This procedure corresponds to step 2 in the [recommended procedure]({{ site.baseurl }}/cloud/live/sens-data-over.html#cloud-config-specific-recomm). After you create `config.php`, transfer it to your local system so you can add it to Git.
+This procedure corresponds to step 2 in the [recommended procedure]({{ site.baseurl }}/cloud/live/sens-data-over.html). After you create `config.php`, transfer it to your local system so you can add it to Git.
 
 To create and transfer `config.php`:
 
@@ -136,7 +136,7 @@ The following snippet from `config.php` shows an example of changing the default
 
 ## Push and deploy config.php to environments {#deploy}
 
-Now that you've created `config.php` and transferred it to your local system, commit it to Git and push it to your environments. This procedure corresponds to step 3 and 4 in the [recommended procedure]({{ site.baseurl }}/cloud/live/sens-data-over.html#cloud-config-specific-recomm).
+Now that you've created `config.php` and transferred it to your local system, commit it to Git and push it to your environments. This procedure corresponds to step 3 and 4 in the [recommended procedure]({{ site.baseurl }}/cloud/live/sens-data-over.html).
 
 The following command adds, commits, and pushes to master:
 
@@ -178,7 +178,7 @@ If you need to modify any of these settings and update `config.php`, you will ne
 
 To add new configurations, modify your Integration environment and run the command again to generate the file. Any new configurations are appended to the code in the file. Push it to Git following the previous steps.
 
-For an overview, see the [recommended procedure]({{ site.baseurl }}/cloud/live/sens-data-over.html#cloud-config-specific-recomm).
+For an overview, see the [recommended procedure]({{ site.baseurl }}/cloud/live/sens-data-over.html).
 
 For this example, we'll modify static file optimization settings and add a new setting for JavaScript.