fix(.net): retriggering build

newrelic · Apr 27, 2022 · 965a64d · 965a64d
1 parent 3088f1a
commit 965a64d
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/src/content/docs/logs/logs-context/net-configure-logs-context-all.mdx b/src/content/docs/logs/logs-context/net-configure-logs-context-all.mdx
@@ -51,7 +51,7 @@ You have three options to configure APM logs in context to send your app's logs
   >
 
   This is the simplest approach, and it's a great choice for developers who may not have the access or interest in setting up a log forwarder, or for accounts that want to see the power of logs and other linking metadata in context of their apps, without a lot of overhead.
-  
+
   Using this option, your logs will include `span.id`, `trace.id`, `hostname`, `entity.guid`, and `entity.name`. These attributes automatically link your logs to spans, traces, and other telemetry, making it easier to troubleshoot.
 
   All you need to do is install an agent version with log forwarding capabilities ([.NET agent 9.7.0 or higher](/docs/release-notes/agent-release-notes/net-release-notes)), and update your configuration to enable forwarding: