Merge pull request #4322 from newrelic/LOGGING6345

fix(Logs): Clarify requirements

src/content/docs/logs/log-management/ui-data/find-unusual-logs-log-patterns.mdx

@@ -4,8 +4,7 @@ tags:
   - Logs
   - Log management
   - UI and data
-metaDescription: 'Use log patterns in New Relic to discover trends in data over
-  time, focus your energy on what matters, and exclude what''s irrelevant.'
+metaDescription: "Use log patterns in New Relic to discover trends in data over time, focus your energy on what matters, and exclude what's irrelevant."
 redirects:
   - /docs/logs/log-management/ui-data/find-unusual-logs-log-patterns-beta
   - /docs/logs/log-management/ui-data/log-patterns-beta
@@ -35,7 +34,9 @@ Log patterns use advanced clustering algorithms to group together similar log me
 
 ## Availability [#availability]
 
-The ability to configure this feature is dependent on role-based permissions. If you see **Patterns are turned off** in your **Log management Patterns UI**, click the **Configure Patterns** button and enable it. If you don't see patterns within 30 minutes of enabling the feature, there may be a lack of data with a message attribute for the system to create a pattern from it.
+The ability to configure this feature is dependent on [role-based permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/). For example, accounts still using our [original pricing model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-changes-pricing-user-model/#user-models) require an Owner or Admin role.
+
+If you see **Patterns are turned off** in your **Log management Patterns UI**, click the **Configure Patterns** button and enable it. If you don't see patterns within 30 minutes of enabling the feature, there may be a lack of data with a message attribute for the system to create a pattern from it.
 
 <table>
   <thead>

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

@@ -113,7 +113,7 @@ To enable logs in context for APM apps monitored by Ruby:
     id="lograge-adv-config"
     title="Lograge configuration"
   >
-  To configure this extension with the [lograge gem](https://rubygems.org/gems/lograge), no additional configuration is required.
+  To configure this extension with the [lograge gem](https://rubygems.org/gems/lograge), follow standard procedures in this doc for [Ruby on Rails configuration](#enable-rails). No additional configuration is required for the lograge gem.
 
   </Collapser>
 

src/content/docs/release-notes/logs-release-notes/logs-21-08-30.mdx

@@ -6,15 +6,15 @@ version: '210830'
 
 ### New public APIs
 
-* Public APIs are now available for [parsing](https://docs.newrelic.com/docs/logs/log-management/ui-data/parsing/) and pipeline configuration (such as [drop filters](https://docs.newrelic.com/docs/logs/log-management/ui-data/drop-data-drop-filter-rules/)). Documentation can be found within the NerdGraph API explorer. Additional external documentation is coming soon!
+* Public APIs are now available for [parsing](/docs/logs/log-management/ui-data/parsing/) and pipeline configuration, such as [drop filters](/docs/logs/log-management/ui-data/drop-data-drop-filter-rules/). For more information, try out NerdGraph, our GraphQL-format API explorer, at [api.newrelic.com/graphiql](https://api.newrelic.com/graphiql). Also see our [NerdGraph parsing rules tutorial](/docs/apis/nerdgraph/examples/nerdgraph-log-parsing-rules-tutorial/) and [drop data tutorial](/docs/telemetry-data-platform/manage-data/drop-data-using-nerdgraph/).
 
 ### Headerless HTTP ingest
 
-*  Added support for [Headerless HTTP log ingest](https://docs.newrelic.com/docs/logs/log-management/log-api/introduction-log-api/#query-parameters). This enables Logs customers to send data to New Relic from sources that do not permit the customization of HTTP request headers (for example, `Api-Key` or `X-License-Key`).  This approach is most often used when forwarding logs from cloud-based platforms.
+*  Added support for [headerless HTTP log ingest](/docs/logs/log-management/log-api/introduction-log-api/#query-parameters). This enables Logs customers to send data to New Relic from sources that do not permit the customization of HTTP request headers (for example, `Api-Key` or `X-License-Key`). This approach is most often used when forwarding logs from cloud-based platforms.
 
 ### More data, more power
 
-* Increased maximum attribute value size. The Logs team recognizes that keeping all data from a log is extremely important, and so we are providing additional functionality to store more data and reduce the chances of truncation. Attributes can now store and display up to 128 kb, the first 4096 bytes of which are searchable. For more information, see our documentation about [finding data in long logs (blobs)](https://docs.newrelic.com/docs/logs/log-management/ui-data/long-logs-blobs/) and the [Log Event API](https://docs.newrelic.com/docs/logs/log-management/log-api/log-event-data/).
+* Increased maximum attribute value size. The Logs team recognizes that keeping all data from a log is extremely important, and so we are providing additional functionality to store more data and reduce the chances of truncation. Attributes can now store and display up to 128 kb, the first 4096 bytes of which are searchable. For more information, see our documentation about [finding data in long logs (blobs)](/docs/logs/log-management/ui-data/long-logs-blobs/) and the [Log Event API](/docs/logs/log-management/log-api/log-event-data/).
 * Added ARM support to our Helm-based [Kubernetes integration](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging).
 
 ### Bug fixes