💅

Author: ethanpalm

api/static-export/overview.mdx

@@ -5,17 +5,17 @@ keywords: ["static export", "static site", "bundle", "self-host", "enterprise"]
 ---
 
 <Info>
-  Static export is gated behind **Enterprise plans**. To enable it for your organization, [contact sales](https://mintlify.com/contact/sales).
+  Static export requires an [Enterprise plan](https://mintlify.com/pricing?ref=static-export).
 </Info>
 
-Use the Static Export API to programmatically pre-render your documentation into a self-contained set of static files and download the result as a single bundle. The exported bundle is pure HTML, CSS, and JavaScript with no runtime dependencies, so you can host it on any static file storage or CDN.
+Use the static export API to programmatically pre-render your site into a self-contained set of static files and download the result as a single bundle. The exported bundle is pure HTML, CSS, and JavaScript with no runtime dependencies, so you can host it on any static file storage or CDN.
 
-## How it works
+## How static export works
 
 A static export runs as an asynchronous job. You start the job, poll for its status, and then generate a downloadable bundle once the job completes.
 
 <Steps>
-  <Step title="Kick off a static export job">
+  <Step title="Start a static export job">
     Call [Start static export job](/api/static-export/start-job) with the domain you want to export. The API queues the job and returns a `jobId`.
   </Step>
   <Step title="Query the job status">
@@ -28,7 +28,7 @@ A static export runs as an asynchronous job. You start the job, poll for its sta
 
 ## Feature support by deployment
 
-Which features are available depends on how you host your docs. Air-gapped deployments have no outbound network access, so anything that relies on Mintlify's cloud services is unavailable. **Configurable** means availability is determined by your environment's setup.
+Which features are available depends on how you host your deployment. Air-gapped deployments have no outbound network access, so anything that relies on Mintlify's cloud services is unavailable. Features labeled **Configurable** have different availability depending on your environment's setup.
 
 | Feature | Cloud | Client-hosted | Air-gapped |
 | --- | :---: | :---: | :---: |
@@ -40,20 +40,16 @@ Which features are available depends on how you host your docs. Air-gapped deplo
 
 ## Endpoints
 
-- [Start static export job](/api/static-export/start-job): Kick off a static export job for a deployment.
+- [Start static export job](/api/static-export/start-job): Start a static export job for a deployment.
 - [Get static export job status](/api/static-export/get-job-status): Poll the status and progress of a running job.
 - [Generate export bundle](/api/static-export/generate-bundle): Package a completed job and return a single S3 link to the bundle.
 
 ## Authentication
 
-Authenticate requests with your admin API key. Generate one on the [API keys page](https://app.mintlify.com/settings/organization/api-keys) in your dashboard. Admin API keys begin with the `mint_` prefix and are server-side secrets--do not expose them in client-side code.
+Authenticate requests with your admin API key. Generate an admin API key on the [API keys page](https://app.mintlify.com/settings/organization/api-keys) in your dashboard. Admin API keys begin with the `mint_` prefix and are server-side secrets--do not expose them in client-side code.
 
 ## Deploy the bundle to your Enterprise Helm chart
 
-<Note>
-  The Helm values and workflow below are a reference for an upcoming release. Exact value keys and behavior are subject to change. Reach out through your Enterprise channel for the current configuration.
-</Note>
-
 Self-hosted Mintlify is deployed with the Helm chart in the [`mintlify/enterprise`](https://github.com/mintlify/enterprise) repository. Once a static export job produces a bundle, you point the chart at the bundle and the deployment serves it from your own infrastructure.
 
 <Steps>
@@ -81,11 +77,11 @@ Self-hosted Mintlify is deployed with the Helm chart in the [`mintlify/enterpris
   </Step>
 </Steps>
 
-Because presigned links expire, regenerate the bundle and re-run the upgrade whenever you publish new content--or automate the whole loop with GitHub Actions below.
+Because presigned links expire, regenerate the bundle and re-run the upgrade whenever you publish new content or automate the loop with GitHub Actions.
 
 ## Automate with a GitHub Action
 
-The following template workflow runs the full export loop on a schedule (or on demand): it starts a job, polls until the export completes, generates a bundle, and rolls the new `bundleUrl` into the Helm chart.
+The following template workflow runs the full export loop on a schedule or on demand. It starts a job, polls until the export completes, generates a bundle, and rolls the new `bundleUrl` into the Helm chart.
 
 ```yaml .github/workflows/static-export.yml
 name: Publish static export