Merge branch 'develop' into NR-356329-browser-logs

src/content/docs/tutorial-create-alerts/create-an-alert.mdx

@@ -162,7 +162,7 @@ For this tutorial, we've included steps for all three of the aforementioned opti
     1. <DNT>**Set the data aggregation options**</DNT>:
        * <DNT>**Window duration**</DNT>: Use the <DNT>**Window duration**</DNT> setting to determine how frequently we aggregate your data, such as groupings of every 5 minutes or every hour. This feature's setting depends on what kind of data you're monitoring. If you're unsure of what it should be, you can leave it at the default setting. You can learn more in our [Create your first alert doc](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/your-first-nrql-condition/#window-duration).
        * <DNT>**Sliding window aggregation**</DNT>: Choose whether or not you want to use [sliding window aggregation](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions/#sliding-window-aggregation). This feature creates smoother charts when dealing with erratic data by creating overlapping aggregation windows. This feature is disabled by default, and we recommend keeping it disabled for your first alert
-       * <DNT>**Streaming method**</DNT>: The options most commonly used are <DNT>**Event flow**</DNT> and <DNT>**Event timer**</DNT>. <DNT>**Event flow**</DNT> is best suited for frequent and consistently reporting data, while <DNT>**Event timer**</DNT> is best suited for data that reports inconsisntely, infrequently, or ingests in batches. If you want to learn more about the individual settings to see which method should be used in each scenario, see [our docs](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/streaming-alerts-key-terms-concepts/#aggregation-methods)
+       * <DNT>**Streaming method**</DNT>: The options most commonly used are <DNT>**Event flow**</DNT> and <DNT>**Event timer**</DNT>. <DNT>**Event flow**</DNT> is best suited for frequent and consistently reporting data, while <DNT>**Event timer**</DNT> is best suited for data that reports inconsistently, infrequently, or ingests in batches. If you want to learn more about the individual settings to see which method should be used in each scenario, see [our docs](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/streaming-alerts-key-terms-concepts/#aggregation-methods)
 
     2. <DNT>**Set the timing option**</DNT>: This determines how long we wait for events in each window before we evaluate them. A longer delay will mean fewer false alerts, but it will also mean longer potential downtime before an incident is open. This capability is also shown differently depending on the option you select: it's called <DNT>**Delay**</DNT> in the <DNT>**Event flow**</DNT> and <DNT>**Cadence**</DNT> options and <DNT>**Timer**</DNT> in <DNT>**Event timer**</DNT>. For your first alert, we recommend keeping the default time setting.
 
@@ -240,7 +240,7 @@ You've now created an alert condition! We offer different configuration options
 
 ## Get more from alerting [#more-alerting]
 
-We have some advanced alerting features that can help you make alerting more efficent and manageable for your team:
+We have some advanced alerting features that can help you make alerting more efficient and manageable for your team:
 
 * If you want greater control over where and when you receive alerts and ensure the right people are notified about issues, see how to use [Workflows](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/).
 * If you want to enable near-instant notification of critical alerts, helping you reduce your mean time to resolution (MTTR), see how to use our [anomaly detection](/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/anomaly-detection-applied-intelligence/).