fix(logs in context): attempt to clarify what LIC is

src/content/docs/logs/logs-context/configure-logs-context-apm-agents.mdx

@@ -1,5 +1,5 @@
 ---
-title: Logs in context of apps and hosts
+title: "Logs in context of your app and host data"
 tags:
   - Logs
   - Enable log management in New Relic
@@ -23,7 +23,7 @@ redirects:
   - /docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-apm-agents
 ---
 
-When you need to correlate log data with other telemetry data, enable logs in context in New Relic. Logs in context functionality adds metadata that links your logs with related APM data, like [errors](/docs/apm/apm-ui-pages/error-analytics/errors-page-find-fix-verify-problems/) or [distributed traces](/docs/apm/distributed-tracing/ui-data/understand-use-distributed-tracing-data), or your platform performance data from [infrastructure monitoring logs](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/) in New Relic One.
+Enabling New Relic's **logs in context** links and correlates your log data with other New Relic-monitored app and infrastructure data. This means that, when applicable, you'll see logs data or links to log data in other New Relic UI experiences, such as our APM UI, infrastructure monitoring UI, distributed tracing, errors inbox, and more.  
 
 To see how logs in context and [log patterns](/docs/logs/ui-data/find-unusual-logs-log-patterns) can help you find the root cause of an issue, watch this short video (approx. 5 minutes):
 
@@ -45,30 +45,24 @@ Don't spend extra time trying to narrow down all your logs from different parts
 
 ## Basic process to enable logs in context [#enable-logs]
 
-Here is an example of logs for your app's UI. You can see logs in context of events for the selected time period, and drill down into detailed data for any of the highlighted attributes. To take advantage of even more capabilities, click **Query logs** from here to go directly to the **Logs** UI.
+Here's an example of the New Relic APM UI showing logs in context. You can see logs in context of events for the selected time period, and drill down into detailed data for any of the highlighted attributes. To take advantage of even more capabilities, click **Query logs** from here to go directly to the **Logs** UI.
 
 ![Logs in context in APM UI](./images/demotron-logs-123021.png "Logs in context in APM UI")
 
-The process to enable logs in context is basically the same, regardless of which APM agent you use to monitor your application:
-
-1. Make sure you have already [set up logging in New Relic](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/enable-log-management-new-relic/). This includes configuring a supported log forwarder that collects your application logs and extends the metadata that is forwarded to New Relic.
-2. Update to a supported APM agent version for your app, and enable [distributed tracing](/docs/distributed-tracing/concepts/introduction-distributed-tracing/).
-3. Configure logs in context for your APM agent or for your infrastructure monitoring agent.
-4. View your logs within the context of your apps or infrastructure in [New Relic One](/docs/logs/log-management/ui-data/use-logs-ui/#links).
-
-The main differences in this procedure are which log appenders you can use to extend and enrich your log data, and how to configure the log appender you select for your APM agent.
-
-For detailed information, see the logs-in-context procedures for:
-
-* [C SDK](/docs/logs/enable-log-management-new-relic/configure-logs-context/c-sdk-configure-logs-context)
-* [Go](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-go/)
-* [Java](/docs/logs/enable-log-management-new-relic/configure-logs-context/java-configure-logs-context-all/)
-* [.NET](/docs/logs/enable-log-management-new-relic/configure-logs-context/net-configure-logs-context-all/)
-* [Node.js](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-nodejs/)
-* [PHP](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-php/)
-* [Python](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-python/)
-* [Ruby](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-ruby/)
-* [Infrastructure monitoring agent](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent/)
+The process to enable logs in context is basically the same, regardless of whether you're setting up an APM agent or the infrastructure agent:
+
+1. Make sure you have already [set up logging in New Relic](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/enable-log-management-new-relic). This includes configuring a supported log forwarder that collects your application logs and extends the metadata that is forwarded to New Relic.
+2. For enabling this for APM: make sure you have a supported APM agent version for your app, and enable [distributed tracing](/docs/distributed-tracing/concepts/introduction-distributed-tracing/). For specific instructions, select your agent: 
+  * [C SDK](/docs/logs/enable-log-management-new-relic/configure-logs-context/c-sdk-configure-logs-context)
+  * [Go](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-go/)
+  * [Java](/docs/logs/enable-log-management-new-relic/configure-logs-context/java-configure-logs-context-all/)
+  * [.NET](/docs/logs/enable-log-management-new-relic/configure-logs-context/net-configure-logs-context-all/)
+  * [Node.js](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-nodejs/)
+  * [PHP](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-php/)
+  * [Python](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-python/)
+  * [Ruby](/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-ruby/)
+3. For infrastructure monitoring: [enable logs in context for the infrastructure agent](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent).
+4. Look for your logs in context in New Relic One. See [What's next?](#what-next)
 
 ## API and other options [#API]
 
@@ -82,7 +76,7 @@ If our logging solutions don't meet your needs, you can use other options to sen
 
 After you set up logs in context for APM or infrastructuring monitoring, make the most of your logging data in the New Relic One UI:
 
-* Explore the logging data across your platform with our [Logs UI](/docs/logs/log-management/ui-data/use-logs-ui/).
+* Explore the logging data across your platform with our [Logs UI](/docs/logs/log-management/ui-data/use-logs-ui).
 * See your logs in context of your app's performance in the [APM UI](/docs/logs/log-management/ui-data/use-logs-ui/#links). Troubleshoot [errors](/docs/apm/apm-ui-pages/error-analytics/errors-page-find-fix-verify-problems/) with [distributed tracing](/docs/apm/distributed-tracing/ui-data/understand-use-distributed-tracing-data), stack traces, application logs, and more.
 * Get deeper visibility into both your application and your platform performance data by forwarding your logs with our [infrastructure monitoring agent](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent/). Review your [infrastructure logs](/docs/logs/log-management/ui-data/use-logs-ui/#links) in the UI.
 * Set up [alerts](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/).