fix(.net config): fixing some precedence wording

newrelic · Jun 5, 2023 · c2b6177 · c2b6177
1 parent 9036060
commit c2b6177
Showing 1 changed file with 4 additions and 6 deletions.
diff --git a/src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx b/src/content/docs/apm/agents/net-agent/configuration/net-agent-configuration.mdx
@@ -72,12 +72,10 @@ Here are details about the configuration methods shown in the diagram, and their
 
       <td>
         Configuration settings set in these files take highest precedence.
-
-        However, if the agent is disabled in the local or global newrelic.config, the NewRelic.AgentEnabled settings in these files will be ignored.
 
-        If the agent is disabled in the local or global `newrelic.config`, the `NewRelic.AgentEnabled` settings in an `appsettings.json` these files **will enable the agent**.
-
-        However, if the agent is disabled in the local or global `newrelic.config`, the `NewRelic.AgentEnabled` settings in a `web.config` or `app.config` **will be ignored**.
+        If the agent is disabled in the local or global `newrelic.config`: 
+            * The `NewRelic.AgentEnabled` settings in `appsettings.json` **will enable the agent**.
+            * The `NewRelic.AgentEnabled` settings in a `web.config` or `app.config` file **will be ignored**.
 
       </td>
     </tr>
@@ -3419,7 +3417,7 @@ For ASP.NET and .NET Framework console apps you can also configure the following
     ```
 
     <Callout variant="important">
-      If the agent is disabled in the local or global `newrelic.config`, the `NewRelic.AgentEnabled` settings in these files will enable the agent.
+      If the agent is disabled in the local or global `newrelic.config`, the `NewRelic.AgentEnabled` settings in these files will **not** enable the agent.
     </Callout>
   </Collapser>