new copy, shaquil early feedback

Author: sg-writer

docs/universal-gateway/overview.mdx

@@ -13,9 +13,15 @@ The Universal Gateway is a flexible and composable platform that can be used wit
 You can deliver traffic to internal and public APIs as well as orchestrate traffic across your devices. 
 It's globally distributed by default and provides support across multiple environments with minimal configuration.
 
-:::tip
-Check out the [front door pattern](/universal-gateway/examples/front-door-pattern/) in the [examples collection](/universal-gateway/examples/) to see one of the most common use cases.
-:::
+## Common use cases
+
+Here are some of the most common use cases for the Universal Gateway, from the [examples collection](/universal-gateway/examples/):
+
+- [**The front door pattern**](/universal-gateway/examples/front-door-pattern/): A single public endpoint serves as the centralized entrance to all upstream services.
+- [**Route to endpoints by geography**](/universal-gateway/examples/route-by-geography/): Forward requests based on IP geolocation data for improved latency or country-specific features.
+- [**Create identity-based rate limits**](/universal-gateway/examples/pre-tier-requests/): Pre-tier requests based on your packaging or pricing model.
+- [**Secure a public Minecraft server**](/universal-gateway/examples/minecraft/): Restrict server access to a specific set of IP addresses.
+- [**Intercept and rewrite headers**](/universal-gateway/examples/rewrite-headers-redirects/): Intercept 302 redirect headers to preserve UX and agent behavior.
 
 ## Universal Gateway features
 
@@ -30,44 +36,27 @@ Learn more in the [Traffic Policy documentation](/docs/traffic-policy/).
 
 ### Kubernetes Operator
 
-The ngrok Kubernetes Operator is the best way to use ngrok if your applications run in Kubernetes environments. 
-It comes with custom resources for configuration and also supports both  Ingress resources as well as the new cross-platform Gateway API configuration resources.
-
-You should use the ngrok Kubernetes Operator if you want to:
+ngrok's Kubernetes Operator is the best way to build with the Universal Gateway if your applications run in Kubernetes environments. 
+It comes with custom resources for configuration and also supports both ingress resources as well as cross-platform Gateway API configuration resources.
+You can use the Operator to integrate Kubernetes workloads with workloads outside of Kubernetes, such as those running on virtual machines, bare metal, embedded devices, and anywhere else you can run ngrok.
 
-Send traffic to your Kubernetes workloads
-Integrate Kubernetes workloads with workloads outside of Kubernetes, such as those running on virtual machines, bare metal, embedded devices, and anywhere else you can run ngrok
-Perform cross-cluster networking
-Use Kubernetes with ngrok without using ngrok's SDKs
+Learn more in the [Kubernetes Operator documentation](/docs/obs/).
 
-### Traffic Observability
+### Traffic observability
 
-#### Traffic Inspector
+The Universal Gateway provides several options for observing the traffic flowing through your endpoints, including the Traffic Inspector and ngrok's event logging system.
+With Traffic Inspector, you can choose to capture full request and response bodies or just metadata, and replay requests against your endpoints for easy debugging replication.
+With ngrok's event logging system, you can subscribe to events triggered whenever traffic transits through your endpoints, and publish them to destinations such as AWS Cloudwatch Logs, AWS Firehose, AWS S3, Datadog Logs, and Azure Monitor.
 
-Traffic Inspector gives you a view into the HTTP traffic flowing through the endpoints in your account. You can choose whether Traffic Inspector captures only request metadata or full request and response bodies. You can even replay requests against your endpoints for easy debugging replication.
-
-#### Log exporting
-
-Whenever changes occur in your ngrok account or when traffic transits through your endpoints, an event is fired. You may subscribe to these events and publish them to destinations like AWS Cloudwatch Logs, AWS Firehose, AWS S3, Datadog Logs, Azure Monitor and more.
+Learn more in the [traffic observability documentation](/docs/k8s/).
 
 ### Identify and access management
 
 ngrok includes a robust identity and access management (IAM) system. 
-ngrok's IAM functionality enables you to:
+With ngrok's IAM functionality, you can manage credentials for human users and automated processes; record all changes by principal in audit logs; configure single sign-on (SS0); and more.
 
-- Issue, rotate and revoke unique credentials for each principal in your account (either a human user or an automated process).
-- Enforce least-privilege access for each principal acting within your ngrok account
-- Attribute all mutations to distinct principals in your ngrok account recorded in audit logs
-- Configure single sign-on (SSO) to federate identity and SCIM to enable provisioning from your own IdP
-- Administrate multiple ngrok accounts with a single user
+Learn more in the [IAM documentation](/docs/iam/).
 
-## Common use cases
-
-- [**The front door pattern**](/universal-gateway/examples/front-door-pattern/): A single public endpoint serves as the centralized entrance to all upstream services.
-- [**Route to endpoints by geography**](/universal-gateway/examples/route-by-geography/): Forward requests based on IP geolocation data for improved latency or country-specific features.
-- [**Create identity-based rate limits**](/universal-gateway/examples/pre-tier-requests/): Pre-tier requests based on your packaging or pricing model.
-- [**Secure a public Minecraft server**](/universal-gateway/examples/minecraft/): Restrict server access to a specific set of IP addresses.
-- [**Intercept and rewrite headers**](/universal-gateway/examples/rewrite-headers-redirects/): Intercept 302 redirect headers to preserve UX and agent behavior.
 
 ## What's next?