i18n(he): apply the second translation review

- RECORD is «רשומה», a record rather than a recording.
- Time abbreviations end in the geresh again (דק׳, שנ׳, שע׳, ימ׳), and the
  counted forms agree with 1.
- Numbers after a Latin name, ordinals and units keep their order in RTL.
- Meaning, agreement and domain terms fixed across the catalog: cyclone
  advisories and storm centre, sensor swath, track-up, cinematic, tropical
  depression, pilot and sailing vessels, chips, metered billing, radio static,
  airspace, NOT AN ALL-CLEAR, and the remaining review items.
- LOOK and OFF-NADIR are translated; {value} KM stays Latin as an instrument
  readout, like KM/S.
- rtl.css shares the Arabic and Hebrew letter-spacing reset and drops the
  duplicated Arabic rules; he.md and its glossary follow the catalog.

src/i18n/same-as-english.json

@@ -1279,13 +1279,11 @@
     "STARLINK",
     "STARLINK ···",
     "STARLINK ✕",
-    "LOOK {elevation}",
     "{range} NM",
-    "OFF-NADIR {angle}° · {offset}",
     "NORAD {id}",
     "EPOCH {time}",
     "TLE",
-    "OFF-NADIR {angle}°",
+    "{value} KM",
     "{value} KM/S",
     "Ironbow"
   ]

src/ui/styles/rtl.css

@@ -4,11 +4,12 @@
    express. */
 
 /* Arabic letters join: letter-spacing tears every word into separate glyphs.
+   Hebrew letters do not join, but tracking only spaces their words out.
    Latin marked translate="no" and the intel HUD's Latin telemetry keep their
    tracking; the HUD's translated lines are released below. Unlike cjk.css, a
    container that merely holds a translate="no" span is not spared: its own
-   Arabic text would come apart. */
-html:lang(ar)
+   text would come apart. */
+html:is(:lang(ar), :lang(he))
   body
   :not(#intel-hud, #intel-hud *, [translate='no'], [translate='no'] *) {
   letter-spacing: 0 !important;
@@ -31,8 +32,7 @@ html[dir='rtl'] #intel-hud :is(.hud-mode, .hud-summary-label, .hud-summary) {
    letter apart. Noto Sans Arabic (loaded with the other Google fonts; its
    files download only when the page shows Arabic) leads the mono stack, so
    the spaces between Arabic words come from it too and not from the
-   fixed-pitch Latin face. The intel and cockpit HUDs keep JetBrains Mono for
-   their Latin telemetry and column-aligned digits. */
+   fixed-pitch Latin face. */
 html:lang(ar) {
   --font-mono:
     'Noto Sans Arabic', 'JetBrains Mono', 'SF Mono', 'Fira Code', 'Geeza Pro',
@@ -41,32 +41,11 @@ html:lang(ar) {
     'Inter', 'Noto Sans Arabic', -apple-system, BlinkMacSystemFont, 'Geeza Pro',
     Tahoma, sans-serif;
 }
-/* The Global Context lines and their buttons set ui-monospace through the
-   `font` shorthand; route them through the Arabic-aware stack too. */
-html:lang(ar)
-  :is(
-    #military-awareness-panel,
-    .military-awareness-controls button,
-    .military-awareness-standby button,
-    .military-awareness-compass-label,
-    .military-awareness-compass-heading,
-    .military-awareness-direction-label,
-    .tr3b-toggle
-  ) {
-  font-family: var(--font-mono);
-}
-html:lang(ar) :is(#intel-hud, #cockpit-hud) {
-  --font-mono:
-    'JetBrains Mono', 'SF Mono', 'Fira Code', 'Noto Sans Arabic', 'Geeza Pro',
-    Tahoma, monospace;
-}
 
 /* Hebrew: JetBrains Mono and Inter also lack Hebrew glyphs. Noto Sans Hebrew
    (loaded with the other Google fonts; its files download only when the page
    shows Hebrew) leads the stack so the body text keeps one proportional
-   Hebrew face across platforms. Hebrew letters do not join, so tracking on
-   them only spaces a word out; the body is released the same way, and the
-   HUDs keep their instrument tracking inside. */
+   Hebrew face across platforms. */
 html:lang(he) {
   --font-mono:
     'Noto Sans Hebrew', 'JetBrains Mono', 'SF Mono', 'Fira Code', Tahoma,
@@ -102,10 +81,6 @@ html:lang(he) :is(#intel-hud, #cockpit-hud) {
     'JetBrains Mono', 'SF Mono', 'Fira Code', 'Noto Sans Hebrew', Tahoma,
     monospace;
 }
-html:lang(he) body
-  :not(#intel-hud, #intel-hud *, [translate='no'], [translate='no'] *) {
-  letter-spacing: 0 !important;
-}
 
 /* The Display/Context rail moves to the left edge. It keeps a physical
    `right` in layers.css because the attribution-clearance model