chore(NR solutions): Sweeping remaining docs

src/content/docs/new-relic-solutions/index.mdx

@@ -39,7 +39,7 @@ redirects:
     title="New Relic solutions."
     icon="fe-check"
   >
-    Read more about our solutions and [how to track objectives.](/docs/new-relic-solutions/new-relic-solutions/establish-objectives-baselines-define-team-slos/)
+    Read more about our solutions: [Track objectives](/docs/new-relic-solutions/new-relic-solutions/establish-objectives-baselines-define-team-slos/), [improve customer experience](/docs/new-relic-solutions/new-relic-solutions/customer-experience-improvement-track-experience-indicators/), and [measure impact](/docs/new-relic-solutions/new-relic-solutions/iterate-measure-impact-track-metrics-after-deployments/).
   </LandingPageTile>
 
   <LandingPageTile

src/content/docs/new-relic-solutions/new-relic-solutions/create-application-baselines.mdx

@@ -198,7 +198,7 @@ Here are the New Relic products to use for baselining, depending on the componen
 
 * [**APM**](/docs/apm): Monitor your web apps with APM. See [Compatibility and requirements for New Relic agents and products](/docs/agents/manage-apm-agents/installation/compatibility-requirements-new-relic-agents) to learn precise compatibility details for each supported language.
 * [**Infrastructure**](/docs/infrastructure): Monitor your hosts with infrastructure. See [Compatibility and requirements for infrastructure](/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructure) for supported operating systems and environments. You can also instrument other products and services with [on-host integrations](/docs/integrations/host-integrations/host-integrations-list).
-* [**Synthetics**](/docs/synthetics): Monitor web frontends and APIs with [synthetics](/docs/synthetics). Sometimes, you may not be able to instrument your on-premise environment with APM or Infrastructure. For example, maybe your organization's policy forbids installing an agent behind a firewall. In these cases, if the application has a web frontend, use Synthetics, as it offers non-agent monitoring while still providing the ability to establish a baseline.
+* [**Synthetics**](/docs/synthetics): Monitor web frontends and APIs with [synthetics](/docs/synthetics). Sometimes, you may not be able to instrument your on-premise environment with APM or infrastructure. For example, maybe your organization's policy forbids installing an agent behind a firewall. In these cases, if the application has a web frontend, use Synthetics, as it offers non-agent monitoring while still providing the ability to establish a baseline.
 
 <CollapserGroup>
   <Collapser
@@ -231,7 +231,7 @@ Here are the New Relic products to use for baselining, depending on the componen
           </th>
 
           <th>
-            New Relic Products
+            New Relic products
           </th>
         </tr>
       </thead>
@@ -385,7 +385,7 @@ Based on the component-product matches you made, deploy agents or monitors acros
 
   <Collapser
     id="deploy-infrastructure"
-    title="Deploy New Relic Infrastructure"
+    title="Deploy infrastructure"
   >
     After reviewing the requirements for infrastructure, follow the instructions to install the infrastructure agent on your hosts:
 
@@ -397,16 +397,16 @@ Based on the component-product matches you made, deploy agents or monitors acros
 
   <Collapser
     id="deploy-infrastructure-on-host"
-    title="Deploy Infrastructure on-host integrations"
+    title="Deploy infrastructure on-host integrations"
   >
     To gain extended visibility into applications that your code depends on, deploy [on-host integrations](/docs/infrastructure/host-integrations/host-integrations-list). Available integrations include Apache, MySQL, NGINX, and others.
   </Collapser>
 
   <Collapser
     id="create-synthetics-monitor"
-    title="Create New Relic Synthetics monitors"
+    title="Create synthetic monitors"
   >
-    New Relic Synthetics is a suite of automated, scriptable tools to monitor your websites, critical business transactions, and API endpoints. To get started [add a monitor](/docs/synthetics/new-relic-synthetics/using-monitors/add-edit-monitors#adding-monitors).
+    Synthetics is a suite of automated, scriptable tools to monitor your websites, critical business transactions, and API endpoints. To get started [add a monitor](/docs/synthetics/new-relic-synthetics/using-monitors/add-edit-monitors#adding-monitors).
 
     <Callout variant="tip">
       Make sure to verify that your website URL is accessible from the public network. You may also need to [add New Relic IPs to your allow list](/docs/synthetics/new-relic-synthetics/administration/synthetics-public-minion-ips).
@@ -431,19 +431,19 @@ After you deploy the agents and monitors, identify which metrics are the most im
 You can find some of these metrics in [service maps](/docs/using-new-relic/service-maps/get-started/introduction-service-maps), as well as on [APM](/docs/apm/applications-menu/monitoring/apm-overview-page), and [browser](/docs/
 /new-relic-browser/getting-started/browser-overview-page-website-performance-summary) **overview** pages.
 
-For more detailed information about navigating, interpreting, and using APM, check out these New Relic University’s tutorials:
+For more detailed information about navigating, interpreting, and using APM, check out these New Relic University's tutorials:
 
 * [Overview dashboard tour](https://newrelic.wistia.com/medias/nywjt50h8u)
 * [Transactions dashboard](https://newrelic.wistia.com/medias/hf694w8ew2)
 * [Understanding Apdex](https://newrelic.wistia.com/medias/ed0sc5053k)
 
-## 5. Set up Dashboards
+## 5. Set up dashboards
 
-After you define your KPIs, it is easy to visualize them in [dashboards](/docs/dashboards). Dashboards provide a single location to view all the data that New Relic products gather. Dashboards data consists of [events](/docs/using-new-relic/welcome-new-relic/get-started/glossary#event), and each event has an event type, a timestamp, and key-value [attributes](/docs/using-new-relic/welcome-new-relic/get-started/glossary#attribute).
+After you define your KPIs, it's easy to visualize them in [dashboards](/docs/dashboards). Dashboards provide a single location to view all the data that New Relic products gather. Dashboards data consists of [events](/docs/using-new-relic/welcome-new-relic/get-started/glossary#event), and each event has an event type, a timestamp, and key-value [attributes](/docs/using-new-relic/welcome-new-relic/get-started/glossary#attribute).
 
 For more information about events, see [Data collection](/docs/data-analysis/metrics/analyze-your-metrics/data-collection-metric-timeslice-event-data) and [Default events for New Relic products](/docs/insights/insights-data-sources/default-data/insights-default-data-other-new-relic-products).
 
-You can locate your KPIs and business metrics data in New Relic using the [data explorer](/docs/insights/insights-data-sources/default-events-attributes/view-default-data-other-new-relic-products-insights) and the [NRQL query language](/docs/insights/nrql-new-relic-query-language/using-nrql/introduction-nrql). You can also [build dashboards](/docs/dashboards/new-relic-one-dashboards/get-started/introduction-new-relic-one-dashboards) to track the performance of those KPIs:
+You can locate your KPIs and business metrics data in New Relic using the [data explorer](/docs/query-your-data/explore-query-data/browse-data/introduction-data-explorer/) and the [NRQL query language](/docs/insights/nrql-new-relic-query-language/using-nrql/introduction-nrql). You can also [build dashboards](/docs/dashboards/new-relic-one-dashboards/get-started/introduction-new-relic-one-dashboards) to track the performance of those KPIs:
 
 <CollapserGroup>
   <Collapser
@@ -670,9 +670,9 @@ You can locate your KPIs and business metrics data in New Relic using the [data
 
 After your migration, compare these baselines against your [migration acceptance testing](/docs/perform-migration-acceptance-testing) baselines.
 
-## Expert tips
+## Expert tips [#expert-tips]
 
-If you find that you need data that is not captured by default instrumentation, New Relic makes it easy to capture custom data:
+If you find that you need data that is not captured by default instrumentation, we make it easy for you to capture custom data:
 
 * [APM custom instrumentation](/docs/agents/manage-apm-agents/agent-data/custom-instrumentation)
 * [Browser custom data](/docs/insights/insights-data-sources/custom-data/insert-data-via-new-relic-browser)

src/content/docs/new-relic-solutions/new-relic-solutions/customer-experience-improvement-track-experience-indicators.mdx

@@ -79,7 +79,7 @@ For example, if you were collecting a custom `username` attribute, you could use
   ```
 
 <Callout variant="tip">
-  If you include a [`FACET` clause](/docs/insights/nrql-new-relic-query-language/nrql-resources/nrql-syntax-components-functions#sel-facet) in your queries, you’ll be able to click into metric results to see corresponding change in the performance data. For more information on faceting, see [Linking Between Dashboards to Drill Into Your Data](https://discuss.newrelic.com/t/relic-solution-linking-between-dashboards-to-drill-into-your-data/45563).
+  If you include a [`FACET` clause](/docs/insights/nrql-new-relic-query-language/nrql-resources/nrql-syntax-components-functions#sel-facet) in your queries, you'll be able to click into metric results to see corresponding change in the performance data. For more information on faceting, see [Linking Between Dashboards to Drill Into Your Data](https://discuss.newrelic.com/t/relic-solution-linking-between-dashboards-to-drill-into-your-data/45563).
 </Callout>
 
 ## 3. Share dashboards across departments
@@ -100,8 +100,4 @@ After you create your dashboards, use them to scope issues affecting particular
 
 ![Insights-catalyst-user-errors.png](./images/Insights-catalyst-user-errors_0.png "Insights-catalyst-user-errors.png")
 
-<figcaption>
-  **[insights.newrelic.com](https://insights.newrelic.com) > Dashboards**
-</figcaption>
-
 Use attributes that track user and performance to set alerts on high priority users or customers. For example, you could include a [`WHERE` clause](/docs/insights/nrql-new-relic-query-language/nrql-resources/nrql-syntax-components-functions#sel-where) in your NRQL queries to scope the results to a set of user IDs or customer IDs. Set alerts on any performance or business metric that is tied to these attributes.

src/content/docs/new-relic-solutions/new-relic-solutions/establish-objectives-baselines-define-team-slos.mdx

@@ -17,6 +17,8 @@ A DevOps transformation requires a cultural shift so that teams can build new sk
 
 This tutorial defines SLOs for successful service delivery objectives and utilize New Relic instrumentation to surface the current performance metrics relative to those objectives. Measurable SLOs and visibility into your current progress against those SLOs ensure that you will be able to properly assess future optimization efforts.
 
+See also our [service levels management feature](/docs/service-level-management/intro-slm/).
+
 ## Service level components [#slo-sli-sla]
 
 An SLO is an agreed upon means of measuring the performance of your service. The SLO defines a target value of a specified quantitative measure, which is called a service level indicator (SLI); for example:
@@ -533,12 +535,6 @@ To instrument the example applications and components in this tutorial, use thes
 
 After you deploy the agents and monitors, use [service maps](/docs/using-new-relic/service-maps/get-started/introduction-service-maps) to review the default metrics that New Relic captures. For example, a typical service map show many of the common SLIs that application teams rely on, including response time, Apdex, throughput, and error rate metrics from APM. It also shows page load time, Ajax response, throughput, and error rate from browser monitoring.
 
-![catalyst-establish-objectives-1.png](./images/catalyst-establish-objectives-1_4.png "catalyst-establish-objectives-1")
-
-<figcaption>
-  **rpm.newrelic.com > Service maps:** To explore detailed granularity for any area, use the service map's nodes.
-</figcaption>
-
 ## 6. Set up custom instrumentation [#custom-instrumentation]
 
 To close any remaining gaps in visibility for your SLIs, use custom instrumentation. New Relic provides several avenues for adding custom instrumentation, including:

src/content/docs/new-relic-solutions/new-relic-solutions/iterate-measure-impact-track-metrics-after-deployments.mdx

@@ -36,7 +36,7 @@ It’s important to track deployments and how the impact of the code and infrast
 
 APM also provides a chronological list of deployments of your application, and additional metrics, such as error rate and Apdex from the time of the deployment, are available as well.
 
-![APM_Deployments_Catalyst.png](./images/APM_Deployments_Catalyst.png "APM_Deployments_Catalyst.png")
+![APM deployments.png](./images/apm-deployments.png "APM deployments.png")
 
 <figcaption>
   **[one.newrelic.com](https://one.newrelic.com) > APM > (select an app) > Events > Deployments**
@@ -52,18 +52,18 @@ Tracking deployments is an invaluable way to determine the root cause of immedia
   * [Ansible](https://docs.ansible.com/ansible/latest/modules/newrelic_deployment_module.html)
 </Callout>
 
-## 3. Test your pipeline with Infrastructure
+## 3. Test your pipeline with infrastructure
 
 An important part of a successful DevOps transformation is a cultural shift toward smaller, more frequent changes to your code and infrastructure. After you complete the first two steps of this tutorial, begin to test and gather appropriate performance insights about your deployment pipeline to more clearly understand the impact of the changes you make.
 
 Code changes should be as small as possible in terms of the number of lines of code and source files you change. Changes should also involve as few team members as possible. This makes it much easier to identify issue owners and determine root causes if errors occur.
 
-Similarly, infrastructure changes should also have as small a footprint as possible to minimize the number of applications affected by each change. [New Relic Infrastructure](/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-linux) helps you see when an infrastructure change has caused a spike in issues, as shown in the following example:
+Similarly, infrastructure changes should also have as small a footprint as possible to minimize the number of applications affected by each change. Our [infrastructure agent](/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-linux) helps you see when an infrastructure change has caused a spike in issues, as shown in the following example:
 
 ![New Relic infrastructure hosts events](./images/Infra_hosts_events_0.png "Infra_hosts_events.png")
 
 <figcaption>
-  **[one.newrelic.com/apm](https://one.newrelic.com) > Infrastructure > Hosts**
+  **[one.newrelic.com](https://one.newrelic.com) > Infrastructure > Hosts**
 </figcaption>
 
 For cloud infrastructure changes or larger code changes, consider using a [blue/green deployment](https://martinfowler.com/bliki/BlueGreenDeployment.html) strategy. APM supports [multiple app names](/docs/agents/manage-apm-agents/app-naming/use-multiple-names-app) which fits this model quite nicely.
@@ -75,4 +75,4 @@ To implement this strategy:
 3. Ensure that traffic is routed appropriately between both versions.
 4. Compare established KPI dashboards of both versions against one another.
 5. Optimize the new version accordingly to meet your KPI targets.
-6. When you’re satisfied with the application’s performance, deploy the new version across your infrastructure using the original app name, and consider this the new baseline for any future changes you'll make to the application.
+6. When you're satisfied with the application's performance, deploy the new version across your infrastructure using the original app name, and consider this the new baseline for any future changes you'll make to the application.

src/content/docs/new-relic-solutions/new-relic-solutions/measure-code-pipelines.mdx

@@ -41,19 +41,3 @@ The example below uses [AWS CodePipeline](https://aws.amazon.com/codepipeline/)
 
 We chose the tools and products used here as examples—with the goal of illustrating the concepts around the types of data and events you should be thinking about when instrumenting your own code pipeline. The sample code, however, should be generic enough to adapt readily to almost any toolset.
 
-## Outcomes
-
-Here is a sample dashboard you could create to track your code pipeline.
-
-![codepipelinedashboard-edited.png](./images/codepipelinedashboard-edited.png "codepipelinedashboard-edited.png")
-
-<figcaption>
-  Track your code pipeline by creating dashboards in New Relic Insights.
-</figcaption>
-
-A dashboard like this yields a number of benefits, including:
-
-* Faster deploy cycles.
-* The ability to prioritize reliability work by identifying services with frequent deploy failures or gaps in test coverage.
-* Ensuring teams don’t achieve speed at the expense of quality.
-* Responding more effectively to change-related failures.

src/content/docs/new-relic-solutions/new-relic-solutions/optimize-cloud-architecture-spend-continuously-improve-your-modern-cloud-environment.mdx

@@ -107,21 +107,11 @@ Make sure the following products and integrations are instrumented:
 
 ## 2. Create dashboards to display baseline infrastructure metrics; include AWS budgets if available [#create]
 
-[D](https://newrelic.com/insights/)[ashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards) lets you write powerful custom queries about your data and visualize the results in widgets displayed on a common dashboard. You can also feed the results of your queries directly into [New Relic Alerts](https://newrelic.com/alerts), where you can get immediate notifications on any deviation identified.
+[Dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards) lets you write powerful custom queries about your data and visualize the results in widgets displayed on a common dashboard. You can also feed the results of your queries directly into [alerts](https://newrelic.com/alerts), where you can get immediate notifications on any deviation identified.
 
-For this step, you should display baseline infrastructure metrics related to performance and usage (CPU, memory, disk, database, etc.). Include AWS Budgets if available. To get you started, here are ways to use Insights dashboards to visualize your AWS cloud utilization and spend data:
+For this step, you should display baseline infrastructure metrics related to performance and usage (CPU, memory, disk, database, etc.). Include AWS Budgets if available.  
 
-![image-1.png](./images/image-1.png "image-1.png")
-
-<figcaption>
-  This dashboard shows data broken out by the applications and budgets you set up in the AWS budgeting area.
-</figcaption>
-
-![image-2a.png](./images/image-2a.png "image-2a.png")
-
-<figcaption>
-  Create individual dashboards for each application, and then collect those dashboards into a single “[data app](/docs/insights/use-insights-ui/manage-dashboards/data-apps-build-collections-linked-dashboards),” as shown here. This AWS Production Overview data app displays a set of widgets relevant to an AWS production budget. Data apps are great for presentations where you want to step through a series of topics and also provide a clear overview of an entire environment or service.
-</figcaption>
+Create individual dashboards for each application, and then collect those dashboards into a single “[data app](/docs/insights/use-insights-ui/manage-dashboards/data-apps-build-collections-linked-dashboards),” as shown here. This AWS Production Overview data app displays a set of widgets relevant to an AWS production budget. Data apps are great for presentations where you want to step through a series of topics and also provide a clear overview of an entire environment or service.
 
 <CollapserGroup>
   <Collapser