fix(LIC): various edits, renamed doc file

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

@@ -21,6 +21,7 @@ redirects:
   - /docs/logs/log-monitoring/enable-logs/configure-logs-context-apm-agents
   - /docs/logs/enable-log-management-new-relic/configure-logs-context
   - /docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-apm-agents
+  - /docs/logs/logs-context/configure-logs-context-apm-agents
 ---
 
 Enabling New Relic's **logs in context** correlates your log data with data collected from our APM and infrastructure agents. This means that you'll see logs data or links to log data in other UI experiences, such as APM, infrastructure monitoring, distributed tracing, and errors inbox. You can use that log data to dig deeper into the performance of your app or host, without needing to manually search through log data. 
@@ -49,10 +50,10 @@ Here's an example of the New Relic APM UI showing logs in context. You can see l
 
 ![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 whether you're setting up an APM agent or the infrastructure agent:
+Here's how to set up logs in context for APM and for infrastructure monitoring: 
 
 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: 
+2. If you want logs in context for APM: first update to a supported APM agent version, 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/)
@@ -61,8 +62,8 @@ The process to enable logs in context is basically the same, regardless of wheth
   * [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)
+3. If you want logs in context for infrastructure monitoring, see [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. See [logs data in context with your monitored apps and hosts](#what-next).
 
 ## API and other options [#API]