Rewrite OSS docs for ASD-STE100 Simplified Technical English

docs/usage/cli.mdx

@@ -14,14 +14,14 @@ strix (--target <target> | --target-list <path>) [options]
 <ParamField path="--target, -t" type="string">
   Target to test. Accepts URLs, repositories, local directories, domains, IP addresses, API spec files (OpenAPI/Swagger `.json`/`.yaml`, a Postman collection export), or a live Postman collection by id (`postman://<collection-uuid>`). Can be specified multiple times. Fresh runs require at least one target source: `--target` or `--target-list`.
 
-  When the target is an API spec, Strix copies it into the agent's workspace and authorizes the base URLs it declares (including those resolved from a Postman environment) as in-scope hosts - so the agent reads the contract and tests the full declared surface instead of discovering endpoints by crawling. Pair the spec with the deployed base URL (e.g. `--target ./openapi.yaml --target https://api.example.com`) so the agent has a reachable host to attack.
+  When the target is an API spec, Strix copies it into the agent workspace and authorizes its declared base URLs. Strix also resolves base URLs from a Postman environment. The agent reads the contract and tests the declared surface. Pair the spec with a deployed base URL, such as `--target ./openapi.yaml --target https://api.example.com`.
 
   <Note>
     A local directory is mounted into the sandbox live and **writable**, so the agent edits your real files (`.git` excepted). Commit or stash first.
   </Note>
 
   <Note>
-    Fetching a Postman collection by id requires `POSTMAN_API_KEY`. Add `?env=<environment-uuid>` to also pull a Postman environment, which resolves `{{baseUrl}}` / token variables the collection references (e.g. `postman://<collection-uuid>?env=<environment-uid>`).
+    Fetching a Postman collection by ID requires `POSTMAN_API_KEY`. Add `?env=<environment-uuid>` to fetch a Postman environment. Use a target such as `postman://<collection-uuid>?env=<environment-uid>`.
   </Note>
 </ParamField>
 
@@ -46,7 +46,7 @@ strix (--target <target> | --target-list <path>) [options]
 </ParamField>
 
 <ParamField path="--diff-base" type="string">
-  Target branch or commit to compare against (e.g., `origin/main`). Defaults to the repository's default branch.
+  Target branch or commit to compare against, such as `origin/main`. Defaults to the repository's default branch.
 </ParamField>
 
 <ParamField path="--non-interactive, -n" type="boolean">
@@ -88,7 +88,7 @@ strix (--target <target> | --target-list <path>) [options]
     slightly overshoot the limit by any calls already in flight when the
     threshold is crossed (most relevant with several child agents running
     concurrently).
-  - Cost is a best-effort estimate derived from token usage and model pricing;
+  - Cost is a best-effort estimate derived from token usage and model pricing.
     providers that do not expose priced usage may under-count.
   - For LiteLLM-routed models, Strix enables streaming success callbacks to
     capture provider-reported cost. Message content remains excluded, but
@@ -148,6 +148,6 @@ strix --target-list ./targets.txt
 
 | Code | Meaning |
 |------|---------|
-| 0 | Scan completed successfully (interactive mode always exits `0`; in headless mode, `0` means no vulnerabilities were found) |
-| 1 | A fatal error occurred before or during the scan (e.g. missing environment variables, Docker unavailable, invalid config file, diff-scope resolution failure, or an unhandled error) |
+| 0 | Scan completed successfully. In headless mode, no vulnerabilities were found. |
+| 1 | A fatal error occurred before or during the scan, such as missing variables, unavailable Docker, invalid configuration, or an unhandled error. |
 | 2 | Vulnerabilities found (headless mode only) |

docs/usage/scan-modes.mdx

@@ -3,7 +3,7 @@ title: "Scan Modes"
 description: "Choose the right scan depth for your use case"
 ---
 
-Strix offers three scan modes to balance speed and thoroughness.
+Strix offers three scan modes to balance speed and coverage.
 
 ## Quick