docs: convert the shared camera includes to the house style

[brickbots]

Full simplified technical English pass over docs/source/includes/camera_prep.rst and docs/source/includes/camera_cable_connect.rst, using the docs skill's seven rules and approved-term table. Part of the manual-wide conversion, one PR per file.

Measured change

  PASS  docs/source/includes/camera_prep.rst
     em-dash 1->0 | semicolon 2->0 | banned 0->0 | words 293->290 (-1%)
  PASS  docs/source/includes/camera_cable_connect.rst
     em-dash 1->0 | semicolon 1->0 | banned 0->0 | words 157->152 (-3%)
OVERALL: PASS

What the converting agent reported

EM_DASHES: 2 -> 0  (both were in non-rendered maintainer comments, not prose)
SEMICOLONS: 3 -> 0
TERMS: board->PCB (PCB already used 4x in the same file for the same part);
  "the dark-grey piece"->"the dark-grey clip" (file used piece/clip for one
  part; now clip x3); "insert the cable"->"slide the cable in" (matching the
  file's own existing phrasing); "Situate"->"Place"
STRUCTURAL: no headings added or changed, no steps reordered, every image path
  byte-identical. Sentence-level splits only. 293->290 and 157->152 words.
LEFT_ALONE: every caution kept and, where modality moved, only strengthened
  ("should sit neatly" -> "must sit neatly" as a fit criterion). Kept "adapter"
  rather than resolving it: the two parent pages disagree with each other on
  this word, and picking one would make the shared text fit the other parent
  worse. Kept "Flip the camera assembly over" because build_guide.rst says
  "Flip the unit over" immediately after the include. No sentence added that
  assumes either a fresh build or an upgrade.
FACT_CONCERNS: "They match the other four, in case they get mixed up" is
  elliptical. Rendered as the plain reading ("so it does not matter if they get
  mixed up"); if the intent was the opposite (keep them separate), this needs a
  maintainer fix.

Safety

Style only. No facts, numbers, procedures or step order were changed.

Verified mechanically against origin/main that every heading (text and underline character), every :ref:, :doc:, image path, substitution, include:: and external URL is unchanged. Headings matter because autosectionlabel turns each one into a cross-reference target that other pages depend on, and a rename would break them silently.

Sphinx builds clean under -n (nitpicky).

Any FACT_CONCERNS above were deliberately not fixed. They are reported for a maintainer decision, since changing them would be a content edit rather than a style one.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HqTCarGCgTRWBQ1ysG8XFD