docs: ASCII typography and style normalization across all repo text

Replace every em dash with real punctuation (rewrites, not hyphen swaps)
in docs, code comments, scripts, configs, and the port records; convert
en dashes, curly quotes, ellipsis glyphs, arrows, and section signs to
ASCII; drop machine-writing tell phrases from living docs. ADR titles
now use a colon. The M2 bring-up DTS model string carried an em dash
into the patch series and its record echoes; fixed at both, and the full
series re-verified to apply cleanly onto pristine 6.18.46. One comment
in freshness.h deliberately names the em dash glyph the UI renders as
the unknown mark; that is data, kept as prose naming it.

Verified: cargo tests (sim, config-lint, rs485-bridge), shellcheck,
both driver MC/DC harnesses, patches-apply.

kernel/rv1106-enablement/dts/README.md

@@ -1,10 +1,10 @@
 # RV1106 6.18 devicetree
 
-- **`rv1106-warden.dts`** — our board DT. `#include`s the vendor `rv1106.dtsi`
-  (the full SoC: pinctrl, gpio×5, dmac, cru+grf_cru, uart, emmc, i2c, saradc,
-  watchdog, usb, vop, npu, rga, …), then enables only what the wall-HMI needs.
+- **`rv1106-warden.dts`**: our board DT. `#include`s the vendor `rv1106.dtsi`
+  (the full SoC: pinctrl, gpiox5, dmac, cru+grf_cru, uart, emmc, i2c, saradc,
+  watchdog, usb, vop, npu, rga, ...), then enables only what the wall-HMI needs.
   No camera/ISP/CSI. Grows one driver batch at a time (see `../DRIVER-PARITY.md`).
-- **`rv1106-warden-m2.dts`** — the earlier standalone minimal DT used to bring up
+- **`rv1106-warden-m2.dts`**: the earlier standalone minimal DT used to bring up
   M2/M3 before the full-SoC transplant; kept for reference.
 
 ## Transplanting the vendor SoC DT onto 6.18 (recipe)
@@ -18,9 +18,9 @@ with the vendor's (it has extra BOOT_CHARGING/UMS/PANIC/WATCHDOG constants the
 DT uses). Then the two hardware deltas:
 
 1. **Delete the `psci` node** from `rv1106.dtsi`. RV1106 has no secure monitor in
-   our boot chain, so `arm,psci-1.0` + `method="smc"` makes the SMC call fault →
-   `Oops - bad mode` → `Attempted to kill the idle task`. (Confirmed on c8a3.)
-2. Enable the peripherals in the board DTS (`&uart2`, `&emmc`, …).
+   our boot chain, so `arm,psci-1.0` + `method="smc"` makes the SMC call fault ->
+   `Oops - bad mode` -> `Attempted to kill the idle task`. (Confirmed on c8a3.)
+2. Enable the peripherals in the board DTS (`&uart2`, `&emmc`, ...).
 
-Verified on warden-c8a3: pinctrl, gpio0–4, pl330 DMA, uart1/2/4, i2c3, dw-wdt all
+Verified on warden-c8a3: pinctrl, gpio0-4, pl330 DMA, uart1/2/4, i2c3, dw-wdt all
 probe; full WardenOS userspace boots.

kernel/rv1106-enablement/dts/rv1106-warden-m2.dts

@@ -1,21 +1,21 @@
 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
 /*
- * Minimal RV1106 devicetree for the WardenOS 86-Panel — M2 "earlycon" bring-up
+ * Minimal RV1106 devicetree for the WardenOS 86-Panel, M2 "earlycon" bring-up
  * of the self-built Linux 6.18 forward-port (warden-sdk kernel/docs/bringup.md).
  *
  * Deliberately NOT the full vendor rv1106.dtsi: just the core needed to reach
- * "it's alive" on the debug UART — CPU, GIC, arch timer, RAM, the CRU (our
+ * "it's alive" on the debug UART: CPU, GIC, arch timer, RAM, the CRU (our
  * ported clk-rv1106), GRF, and uart2 (the console, driven by mainline 8250_dw).
  * earlycon writes uart2's MMIO directly at the bootloader's divisor, so it prints
  * before the clock/pinctrl drivers probe; the real ttyS console then needs the
  * CRU to hand out SCLK_UART2, which is exactly what this validates on hardware.
  *
  * PORT-VERIFY (must be checked against the TRM / on hardware before trusting a
- * boot — a wrong value here silently hangs the board):
+ * boot; a wrong value here silently hangs the board):
  *   - memory size/base (256 MiB @ 0x0 assumed for the 86-Panel; the loader
- *     usually patches this — confirm against the real DDR init);
+ *     usually patches this; confirm against the real DDR init);
  *   - uart2 is the console at 0xff4c0000 (matches the vendor ttyFIQ0 base);
- *   - CRU needs no assigned-clocks here (PLLs keep their loader rates) — fine for
+ *   - CRU needs no assigned-clocks here (PLLs keep their loader rates), fine for
  *     earlycon/console, revisit for the full clock tree.
  */
 /dts-v1/;
@@ -25,7 +25,7 @@
 #include <dt-bindings/clock/rv1106-cru.h>
 
 / {
-	model = "WardenOS 86-Panel (RV1106) — M2 earlycon bring-up";
+	model = "WardenOS 86-Panel (RV1106), M2 earlycon bring-up";
 	compatible = "rockchip,rv1106";
 	#address-cells = <1>;
 	#size-cells = <1>;
@@ -47,7 +47,7 @@
 
 	memory@0 {
 		device_type = "memory";
-		reg = <0x00000000 0x10000000>; /* 256 MiB — PORT-VERIFY */
+		reg = <0x00000000 0x10000000>; /* 256 MiB: PORT-VERIFY */
 	};
 
 	xin24m: oscillator {

kernel/rv1106-enablement/dts/rv1106-warden.dts

@@ -3,7 +3,7 @@
  * WardenOS 86-Panel board DT for the self-built Linux 6.18 forward-port.
  *
  * Includes the full vendor rv1106.dtsi (SoC nodes + pinctrl + gpio + dmac), then
- * enables only what our wall-HMI needs — no camera/ISP/CSI. Grows one driver
+ * enables only what our wall-HMI needs: no camera/ISP/CSI. Grows one driver
  * batch at a time toward full parity with the 5.10 kernel (DRIVER-PARITY.md).
  */
 /dts-v1/;
@@ -31,7 +31,7 @@
 		reset-gpios = <&gpio1 RK_PA2 GPIO_ACTIVE_LOW>;
 	};
 
-	/* SARADC voltage reference (1.8V) — the driver reads this for scale;
+	/* SARADC voltage reference (1.8V): the driver reads this for scale;
 	   without it saradc probes -22 (regulator_get_voltage on the dummy). */
 	vcc_1v8: vcc-1v8 {
 		compatible = "regulator-fixed";
@@ -57,7 +57,7 @@
 	status = "okay";
 };
 
-/* --- M5: AIC8800DC wifi/BT SDIO (on &sdmmc, mmc@ffaa0000 — NOT &sdio) --- */
+/* --- M5: AIC8800DC wifi/BT SDIO (on &sdmmc, mmc@ffaa0000; NOT &sdio) --- */
 &sdmmc {
 	max-frequency = <50000000>;
 	bus-width = <4>;
@@ -95,7 +95,7 @@
 	status = "okay";
 };
 
-/* --- M4: display (VOP + RGB → 720x720 panel + PWM backlight) --- */
+/* --- M4: display (VOP + RGB -> 720x720 panel + PWM backlight) --- */
 &display_subsystem {
 	status = "okay";
 };