diff --git a/src/content/docs/release-notes/logs-release-notes/logs-21-07-28.mdx b/src/content/docs/release-notes/logs-release-notes/logs-21-07-28.mdx
index 7b4dfa34f8c..9c0e2d902c1 100644
--- a/src/content/docs/release-notes/logs-release-notes/logs-21-07-28.mdx
+++ b/src/content/docs/release-notes/logs-release-notes/logs-21-07-28.mdx
@@ -14,7 +14,7 @@ Moving forward, we will be summarizing the most recent fixes and enhancements ca
 
 * In addition to the Logs UI for [data partition management](/docs/logs/log-management/ui-data/data-partitions/), you can now use our public API. Data partitions help you query more efficiently by scanning less unrelated data and returning results faster. To get started, see our [NerdGraph tutorial](/docs/apis/nerdgraph/examples/nerdgraph-data-partition-rules-tutorial/). 
 * Parsing rules are also publicly accessible via the [Log API](/docs/logs/log-management/log-api/introduction-log-api/). We already provide [built-in parsing rulesets](/docs/logs/log-management/ui-data/built-log-parsing-rulesets/) to facet or filter logs in useful ways. This in turn helps you build better charts and alerts.
-* If you can't use log forwarders because of situtions such as CDNs, hardware devices, or managed services, you can use `syslog` protocols via a [TCP endpoint](/docs/logs/log-management/log-api/use-tcp-endpoint-forward-logs-new-relic/).
+* If you can't use log forwarders when collecting logs from CDNs, hardware devices, or managed services, you can use `syslog` protocols via a [TCP endpoint](/docs/logs/log-management/log-api/use-tcp-endpoint-forward-logs-new-relic/).
 
 ### Bug fixes