docs: support-driven corrections and gap-filling

[brickbots]

Works through the support-driven docs review of docs/source compiled 2026-08-10, verified page-by-page against main at 739b36b.

Corrections

Item	Change
Rev4 Straight	Now says the screen sits at 45°, not "straight back". The old wording read as "rev4 reproduces v3's straight-back geometry", which argues rear-focus telescope owners out of the configuration that actually suits them.
Camera Type	A rev4 takes v3 - imx462. Stated in sd_card, troubleshooting and menu_map, using the literal menu strings. Matters most in sd_card, since rev4's card slot is externally accessible.
SkySafari	Dropped the version-by-version ranking. The floor is stated once, on the page's own requirements line: a paid version, 6 or later. The free version has no telescope control.
Dovetail	One M5 bolt, not "two screws", and you don't remove the PiFinder from the telescope to tighten it.
Temperature	Field reports run to 45°C/110°F, framed as observing reports and scoped as a unit-level figure rather than a battery rating.
Web nav label	"Network Setup" in both places, matching python/views/base.html:19,30. The page previously contradicted itself.

Equatorial platforms (highest severity)

An alt-az telescope on an EQ tracking platform is still operated in alt-az. The docs told those owners to set Mount Type to Equatorial, which is precisely the misconfiguration that makes Push-To corrections jump around. Corrected in the Object Details note and in the troubleshooting FAQ.

Gaps filled

• "Getting a GPS lock" (new user_guide section) — the ephemeris download, why Sats seen/used 0/0 is not a progress bar, why power cycling restarts the wait, why a phone is not a fair comparison, and what the lock types mean. Cross-linked from the quick start's GPS note, its GPS Status section, and a new "The GPS never locks" troubleshooting symptom.
• Comets (CM) and Planets (PL) added to catalogs — both need a GPS lock; comet elements refresh automatically from the MPC, with the practical "power up on WiFi beforehand" advice. Plus a pointer to observing lists for "can I add my own objects?".
• Sleep mode — only key presses hold the PiFinder awake. Motion wakes it but doesn't reset the timer, which is why polar alignment and slow slews dim the screen mid-task.
• rev4 focus lock ring — documented, including refining focus under stars before locking it.
• AFOV whole degrees — a decimal silently discards the eyepiece while still reporting "Eyepiece added".
• Test Mode — surfaced in the FAQ as the cloudy-night answer.

Verified against source, not carried over on trust

Sleep timer semantics (main.py PowerManager), lock type labels (ui/gpsstatus.py), catalog codes and the planet list (catalogs.py, comets.py, de421), the AFOV int() parse (server.py:739), and the nav labels (views/base.html).

One correction to the review itself: it suggested "Limited vs Accurate" is 2D vs 3D. In ui/gpsstatus.py:29-36 the mapping is 0: Limited, 1: Basic, 2: Accurate (2D fix), 3: Precise (3D fix). So 2D vs 3D is Accurate vs Precise; Limited is a pre-fix state. Documented per the code.

Deliberately not done

• Web login password contrast — the review itself says the real fix is CSS, not docs. Raising as a UI bug rather than documenting around it; no doc text added.
• Items in section D (already shipped), and the two the review recommends against (#4 conversion guide, Beta #7 EQ-mount page, #12 PDF polish).

Verification

python -m sphinx -b html -n -q source — zero warnings, clean build from scratch, baseline preserved. Style grep over the added lines shows no em-dashes, semicolons, or off-table terminology.

🤖 Generated with Claude Code