diff --git a/src/content/data-streams/architecture.mdx b/src/content/data-streams/architecture.mdx
index 84d5e4d2396..7bdc1e70fe2 100644
--- a/src/content/data-streams/architecture.mdx
+++ b/src/content/data-streams/architecture.mdx
@@ -105,6 +105,6 @@ Automatic failover handles availability and traffic routing in the following sce
 
 - **Automatic Failover:** If one of the origins becomes unavailable, the global load balancer automatically reroutes traffic to the next available origin. This process is transparent to the user and ensures uninterrupted service. During automatic failover, WebSockets experience a reconnect. Failed REST requests must be retried.
 
-- **Manual Trafic Steering:** If you want to bypass the load balancer and target a specific site, you can use the origin headers to direct your requests. This manual targeting does not affect the automated failover capabilities provided by the load balancer, so a request will succeed even if the specified origin is unavailable.
+- **Manual Traffic Steering:** If you want to bypass the load balancer and target a specific site, you can use the origin headers to direct your requests. This manual targeting does not affect the automated failover capabilities provided by the load balancer, so a request will succeed even if the specified origin is unavailable.
 
 - **Multi-origin concurrent WebSocket subscriptions:** In order to maintain a highly available and fault tolerant report stream, you can subscribe to up to two available origins simultaneously. This compares the latest consumed timestamp for each feed and discards duplicate reports before merging the report stream locally.