expand scope

Author: sg-writer

docs/iam/index.mdx

@@ -43,5 +43,4 @@ terminology and concepts ngrok uses to describe its IAM primitives.
   email address to an Account.
 - [**RBAC**](/iam/rbac/): Role Base Access Control is used to limit the permissions of what
   actions a User may take within your account.
-- [**Account Domain Controls**](/iam/domain-controls/): Account Domain Controls are used to create
-  policy on Users who log in or sign up with a given email domain.
+- [**Account Domain Controls**](/iam/domain-controls/): Account Domain Controls are used to create policy on Users who log in or sign up with a given email domain.

docs/k8s/index.mdx

@@ -4,7 +4,8 @@ sidebar_label: Overview
 pagination_next: k8s/how-it-works
 ---
 
-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. When using Kubernetes Ingresses or the Gateway API resources, the ngrok Kubernetes Operator will translate them into managed instances of the ngrok custom resources for you.
+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. When using Kubernetes Ingresses or the Gateway API resources, the ngrok Kubernetes Operator will translate them into managed instances of the ngrok custom resources for you.
 
 The ngrok Kubernetes Operator is deployed to a cluster and allows developers to self-service endpoints to their apps and services using a shared ngrok account.
 

docs/obs/index.mdx

@@ -7,7 +7,8 @@ pagination_next: obs/traffic-inspection
 # Traffic Observability
 
 ngrok provides two powerful mechanisms that allow you to observe and introspect
-the network traffic flowing through your Endpoints. An in-dashboard real-time
+the network traffic flowing through your Endpoints. 
+An in-dashboard real-time
 view of requests and a fully-fledged event system to export events to your own
 logging systems.
 

docs/traffic-policy/concepts/index.mdx

@@ -7,7 +7,8 @@ pagination_label: Phases
 
 # Traffic Policy Overview
 
-The ngrok Traffic Policy engine enables you to manage traffic consistently across your endpoints. It allows you to inspect, manipulate, and route traffic in a structured way.
+The ngrok Traffic Policy engine enables you to manage traffic consistently across your endpoints. 
+It allows you to inspect, manipulate, and route traffic in a structured way.
 
 Traffic Policy is composed of a few key components:
 

docs/universal-gateway/overview.mdx

@@ -34,6 +34,6 @@ Here are some of the most common use cases for the Universal Gateway, from the [
 
 ## What's next?
 
-- Explore key concepts for working with the Universal Gateway such as [endpoint types](/universal-gateway/types/), [protocols](/universal-gateway/protocols/), [bindings](/universal-gateway/bindings/), and [pooling](/universal-gateway/endpoint-pooling/).
 - Check out the [Universal Gateway examples collection](/docs/universal-gateway/examples/) to see how to implement even more common use cases.
+- Explore key concepts for working with the Universal Gateway such as [endpoint types](/universal-gateway/types/), [protocols](/universal-gateway/protocols/), [bindings](/universal-gateway/bindings/), and [pooling](/universal-gateway/endpoint-pooling/).
 - Proceed to the Guides section to get started with ngrok as an [API gateway](/guides/api-gateway/get-started/), [device gateway](/guides/device-gateway/agent/), [identity-aware proxy](/guides/identity-aware-proxy/securing-with-oauth/), or for [site-to-site connectivity](/guides/identity-aware-proxy/securing-with-oauth/).