implementing-sme-suggession-and-minor-grammar-correction

src/content/docs/logs/logs-context/configure-logs-context-go.mdx

@@ -103,7 +103,7 @@ Modifications to the Go agent's config options are needed in order to use the fo
   >
     For most users, using the automatic log forwarding built into the Go agent is the best solution. It's easy to set up and works great for a majority of use cases. 
 
-    Using this option, the agent reports your entire log and adds our attributes `span.id`, `trace.id`, `hostname`, `entity.guid`, and `entity.name`. These attributes link your logs to spans, traces, and other telemetry, making it easier to troubleshoot. [Learn about log forwarding limitations.](/docs/logs/logs-context/get-started-logs-context#forwarding-details)
+    Using this option, your logs include `span.id`, `trace.id`, `hostname`, `entity.guid`, and `entity.name`. These attributes link your logs to spans, traces, and other telemetry, making it easier to troubleshoot. [Learn about log forwarding limitations.](/docs/logs/logs-context/get-started-logs-context#forwarding-details)
 
     Automatic application log forwarding is now enabled by default in Go agent version 3.20.0 or higher. If your applications use these Go agent versions, you don't need to change your config options to enable automatic log forwarding.
 
@@ -121,7 +121,7 @@ Modifications to the Go agent's config options are needed in order to use the fo
     title="Option 2: Decorate logs with APM and manually forward logs"
   >
     For users with more custom logging needs, or users who want to send more than 10,000 logs per 60 second cycle, or 833 logs per 5 second cycle, to New Relic we recommend that you manually set up log forwarding.
-    Once you have a log forwarder configured to send logs to New Relic, allow the Go agent to enrich your logs for forwarding by modifying its config to include this setting:
+    Once you have configured a log forwarder to send logs to New Relic, modify the Go agent's configuration to enrich your logs for forwarding. Enriching the logs means that the log forwarder will add APM context data including `span.id`, `trace.id`, `hostname`, `entity.guid`, and `entity.name`to the log:
 
     ```go
     app, err := newrelic.NewApplication(