Fix broken commands and false claims in the connect guides

[GuanzhouSong]

Six reviews (Opus 5, Opus 4.8, GPT-5.6 Sol — two repos each) scored the docs against a written standard derived from Diátaxis, the CloudNativePG layout, the PostgreSQL documentation guide, and failures reproduced against DocumentDB's own published pages.

Website mean: 29/50. The packages page scored ~46 on its own; the connect guides — which never got the same cold-start treatment — dragged the rest down. Every item below was reproduced against the published 0.116.0 image.

---

1. The certificate command was wrong on three pages

docker cp documentdb:/home/documentdb/gateway/pg_documentdb_gw/cert.pem ~/documentdb-cert.pem
Error: Could not find the file ... in container

Real path: /home/documentdb/.local/state/documentdb-gateway/tls/cert.pem. One wrong string, retyped on three pages — exactly the drift a single source prevents.

2. "Sample data loads by default" was false

--init-data defaults to false. A container started as the guides showed returns listDatabases → [], so every use sampledb block silently returned nothing. The documentdb-local page already said the opposite ("starts empty"), so the two contradicted each other.

Now stated as opt-in, and stated where the reader starts the container rather than where they hit the empty result.

3. The projection referenced a field that doesn't exist

sampledb.users has firstName/lastName, no name. The documented { name: 1, email: 1 } printed only the email while the prose promised names.

4. mongosh install broke on ARM

The RHEL repo was pinned to .../mongodb-org/8.0/x86_64/. This page already carries an ARM substitution table for the DocumentDB and PGDG lines — the MongoDB line was missed. Now $(uname -m), matching the EL-9-$(uname -m) form already documented for PGDG.

5. Docker Quick Start: three gaps the standard treats as defects

• Published on every interface. -p 10260:10260 while calling the instance "local" → now -p 127.0.0.1:10260:10260, with a note on when to widen it.
• Readiness race. The page ran docker ps, then immediately told the reader to connect. docker ps reports Up well before the gateway accepts connections — documentdb-local documents this race; this page ignored it. Now waits for === DocumentDB is ready ===.
• No day-2 lifecycle at all. The fastest and most-recommended path had no stop/start/restart/remove. Anyone following two guides in sequence hit Conflict. The container name "/documentdb" is already in use with no documented recovery.

---

Verification

• All edits confirmed in rendered output via getArticleByPath; the old cert path returns zero matches across all four guides.
• npm test 130 passed · eslint clean · tsc --noEmit clean.

Note on the review process

Two of six reviewers reported a "broken URI" containing ******. That was the credential-redaction filter masking mongodb://user:pass@host in their own transcripts — ****** appears nowhere in either repo. Verified against raw bytes and discarded; one reviewer (Opus 5) caught it independently. No finding here was acted on without confirming it in the actual file.

Related

documentdb/docs#71 — the docs-repo half: non-functional Python samples, a vector index that cannot be created as documented, stale version floors, and five orphaned stub pages.

[guanzhousongmicrosoft]

Verified against the published 0.116.0 image. Approving.