docs: Remove the Compute approval note from the ALB guide

guides/alb-as-httpd.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Use ALB as your HTTP proxy"
 sidebarTitle: "ALB as httpd"
 description: "Replace the NGINX, Apache, Caddy, or Traefik container in front of your app with Datum's Application Load Balancer."
 ---
 
 {/* Keep this page human readable and high level: a few chosen examples, then link to the
@@ -42,7 +42,7 @@
 - [Verifying the migration](#verify-the-migration)
 
 <Note>
-  Compute is in preview. The `v1alpha` APIs can change, and Datum reviews Compute access requests manually.
+  Compute is in preview, and its `v1alpha` APIs can change. Compute turns on for a project the first time you run a `datumctl compute` command there.
 </Note>
 
 ## Before you begin
@@ -288,7 +288,7 @@
 <CodeGroup>
 ```nginx nginx.conf
 upstream web { server web:8080; }
 upstream api { server api:8080; }
 
 server {
     location / {
@@ -538,12 +538,12 @@
 Datum issues and renews a certificate for each hostname on the ALB. These leave with the proxy container:
 
 - Certificate files
 - certbot
 - ACME settings
 
 To check certificate status, run `datumctl alb describe web` and read the `Certificates` line. For more information, see [Serve traffic on your own domain](/alb/operations/custom-domains) and [Serve a wildcard hostname](/alb/configuration/wildcard-hostnames).
 
 ### Health checks and failover
 
 The ALB has no active health checks. Its passive health checks watch real responses instead: once you turn them on, an Instance that returns a run of 5xx errors is taken out of rotation, separately on each edge node. For settings, see [Passive health checks](/alb/configuration/load-balancing#passive-health-checks). For how Instances are replaced during an update, see [How rollouts work](/compute/placement-and-scaling#how-rollouts-work). For test results, see [Load balancing and rollouts](https://github.com/datum-labs/shorts/blob/main/gists/alb/alb-as-httpd-reference.md#load-balancing-and-rollouts) in the reference.
 
@@ -600,7 +600,7 @@
 
 ### Access metrics
 
 For the metrics Datum publishes for each ALB, see [Metrics](/alb/observability#metrics). To send them to Grafana Cloud or another Prometheus remote-write endpoint, see [Metrics export](/operations/metrics-export).
 
 {/* STUB. Where to see request rate, error rate, and latency for the ALB. State how to reach them (datumctl and the portal), the retention window, and which metrics to alert on first. Link to telemetry metrics docs. */}
 
@@ -674,7 +674,7 @@
 
 ### Rollback plan
 
 Keep the old proxy container deployable until the ALB has carried production traffic for a while. Lower your DNS TTL before cutover so you can point back quickly. See [Cut over](https://github.com/datum-labs/shorts/blob/main/gists/alb/alb-as-httpd-reference.md#cut-over) in the reference.
 
 {/* STUB. Keep the old proxy container deployable until verified, and how to cut back if the ALB behaves differently. */}
 
@@ -683,7 +683,7 @@
 Some apps don't speak HTTP. They speak a gateway protocol, and the proxy in front of them translates:
 
 - **FastCGI**: PHP-FPM and similar process managers. NGINX reaches them with `fastcgi_pass`.
 - **uWSGI**: the uwsgi protocol used by many Python apps. NGINX reaches them with `uwsgi_pass`.
 - **CGI**: older scripts that the web server runs once per request.
 
 The ALB forwards only HTTP, and an Instance runs one container, so a proxy sidecar can't do the translation. You have two options.
@@ -691,7 +691,7 @@
 **Switch to an image that serves HTTP directly.** This is the simpler option. Examples:
 
 - PHP: FrankenPHP, or Apache with `mod_php`
 - Python: gunicorn or uvicorn
 
 Then follow this guide from the start. For details, see [Before you begin](https://github.com/datum-labs/shorts/blob/main/gists/alb/alb-as-httpd-reference.md#before-you-begin) in the reference.
 
@@ -740,7 +740,7 @@
 
 ## Clean up
 
 After cutover and your rollback window, retire:
 
 - The old proxy container
 - Its configuration