clean up existing content

Author: sg-writer

docs/iam/index.mdx

@@ -4,20 +4,16 @@ sidebar_label: Overview
 pagination_next: iam/users
 ---
 
-# Identity and Access Management
-
-## Overview
-
-ngrok includes a robust identity and access management (IAM) system. ngrok's
-IAM functionality enables you to:
+ngrok includes a robust identity and access management (IAM) system. 
+ngrok's IAM functionality enables you to:
 
 - 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
 
-## Concepts
+## Features
 
 Before diving into ngrok's IAM system, it's helpful to be acquainted with the
 terminology and concepts ngrok uses to describe its IAM primitives.
@@ -44,3 +40,11 @@ terminology and concepts ngrok uses to describe its IAM primitives.
 - [**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.
+
+## Use cases
+
+TK
+
+## What's next
+
+TK

docs/k8s/index.mdx

@@ -5,13 +5,18 @@ 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.
+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.
 
 Check out the [how it works](/k8s/how-it-works) and [architecture](/k8s/installation/architecture) pages for more info on how the operator functions.
 
-## When Should I Use The ngrok Kubernetes Operator?
+## Features
+
+TK
+
+## Use cases
 
 You should use the ngrok Kubernetes Operator if you want to:
 
@@ -20,7 +25,7 @@ You should use the ngrok Kubernetes Operator if you want to:
 1. Perform cross-cluster networking
 1. Use Kubernetes with ngrok without using ngrok's SDKs
 
-## What Type of Config Can I Use With The Operator?
+## Configuration
 
 The Operator supports its own native custom resource types, including:
 
@@ -42,3 +47,7 @@ controller incur a cost. More details can be found on our [pricing page](https:/
 
 [Kubernetes Ingress docs]: https://kubernetes.io/docs/concepts/services-networking/ingress/
 [Gateway API docs]: https://gateway-api.sigs.k8s.io/
+
+## What's next
+
+TK

docs/obs/index.mdx

@@ -4,28 +4,20 @@ sidebar_label: Overview
 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
-view of requests and a fully-fledged event system to export events to your own
-logging systems.
+ngrok provides two powerful mechanisms that allow you to observe and introspect 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.
 
 ## Traffic Inspector
 
-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.
+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.
 
 [Get Started with Traffic Inspector →](/obs/traffic-inspection/)
 
 ## 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.
+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.
 
 [Get Started with Log Exporting Events →](/obs/events/)

docs/traffic-policy/concepts/index.mdx

@@ -1,15 +1,18 @@
 ---
 sidebar_position: 0
-title: Overview
+title: Traffic Policy Overview
+sidebar_title: Overview
 pagination_next: traffic-policy/concepts/phases
 pagination_label: Phases
 ---
 
-# Traffic Policy Overview
+## What is Traffic Policy?
 
 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.
 
+## Features
+
 Traffic Policy is composed of a few key components:
 
 - [**Phases:**](./phases) Defined points in the traffic lifecycle where you can apply logic.
@@ -18,4 +21,10 @@ Traffic Policy is composed of a few key components:
 - [**Actions:**](./actions) Logic that is triggered when a Phase Rule condition is met.
 - [**CEL Interpolation:**](./cel-interpolation) A way to dynamically evaluate variables and macros inside configuration values, such as URLs or headers.
 
-By combining these components, Traffic Policy provides a powerful way to control your traffic flow at a fine-grained level.
+## Use cases
+
+TK
+
+## What's next?
+
+TK

docs/universal-gateway/overview.mdx

@@ -13,7 +13,7 @@ The Universal Gateway can be used with software running locally or in the cloud,
 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 for multiple environments with minimal configuration.
 
-## Universal Gateway features
+## Features
 
 Here are some of the key features of the Universal Gateway platform:
 
@@ -22,7 +22,7 @@ Here are some of the key features of the Universal Gateway platform:
 - [**Identity and access management**](/docs/iam/): manage credentials for human users and automated processes.
 - [**Kubernetes support**](/docs/k8s/): ngrok's Kubernetes Operator supports ingress resources as well as cross-platform Gateway API configuration resources.
 
-## Universal Gateway use cases
+## Use cases
 
 Here are some of the most common use cases for the Universal Gateway, from the [examples collection](/universal-gateway/examples/):