fix(user type): fix log mgmt capabilities

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx

@@ -344,17 +344,6 @@ Here's a detailed comparison of capabilities by user type. For tips on why you'd
               name="fe-check"
             /></td>
         </tr>
-     <tr>
-          <td>
-            [Logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents)
-          </td>
-          <td style="text-align:center"></td>
-          <td></td>
-          <td style="text-align:center"><Icon
-              style={{color: '#328787'}}
-              name="fe-check"
-            /></td>
-        </tr>
      <tr>
           <td>
             [Network performance monitoring](/docs/network-performance-monitoring/get-started/npm-introduction) (NPM)
@@ -587,7 +576,7 @@ On January 12, 2022, basic users had some log management capabilities removed. T
 
 Log-related capabilities: 
 * Basic users: can only view and search the [log management UI](/docs/logs/get-started/get-started-log-management). They don't have access to the more advanced log management features described below. 
-* Core users: have access to log management UI features, but not log data management and configuration capabilities or [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents).
+* Core users: have access to log management UI features, but not log data management and configuration. They have access to [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents) for any UI experiences they can access (for example, errors inbox).
 * Full platform users: Have access to all log management features, including [patterns](/docs/logs/ui-data/find-unusual-logs-log-patterns), parsing](/docs/logs/ui-data/parsing), [data partitions](/docs/logs/ui-data/data-partitions), and [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents). 
 
 </Collapser>