Rename redacted-note class to note (reader callout, not redacted content)

infra/dev-environment/index.njk

@@ -33,5 +33,5 @@ layout: base.njk
 <li><strong>PyCharm</strong>, used the same way for Python projects.</li>
 </ul>
 
-<p class="redacted-note">This setup deliberately treats the dev VM as ephemeral infrastructure, not a pet, the philosophy is: keep state in Git, keep the VM replaceable, and let daily backups absorb the risk of giving an AI agent real write access to the system.</p>
+<p class="note">This setup deliberately treats the dev VM as ephemeral infrastructure, not a pet, the philosophy is: keep state in Git, keep the VM replaceable, and let daily backups absorb the risk of giving an AI agent real write access to the system.</p>
 </div>

infra/lxc/index.njk

@@ -40,5 +40,5 @@ layout: base.njk
 <li><strong>Advantage</strong>, simple backup via <code>mysqldump</code>, straightforward remote access configuration (bind-address, dedicated service users per consuming application), and one central database that multiple Docker containers on other hosts can connect to over the network instead of each running their own database container.</li>
 </ul>
 
-<p class="redacted-note">All three LXCs run exclusively on the main Proxmox host (PVE), not on pve2 or the Synology, they're intentionally kept centralized since they're few in number and don't need the multi-host redundancy that the Docker setup has. IPs, credentials and specific VMIDs are omitted here; only the reasoning behind the LXC-vs-Docker choice is shown.</p>
+<p class="note">All three LXCs run exclusively on the main Proxmox host (PVE), not on pve2 or the Synology, they're intentionally kept centralized since they're few in number and don't need the multi-host redundancy that the Docker setup has. IPs, credentials and specific VMIDs are omitted here; only the reasoning behind the LXC-vs-Docker choice is shown.</p>
 </div>

retro/amiga-hardware-landscape/index.njk

@@ -43,5 +43,5 @@ accelerator card features that neither platform emulates perfectly.
 And the perennial question of Kickstart ROM versions, 3.1 for
 compatibility, 3.2 for features, applies equally to both setups.</p>
 
-<p class="redacted-note">Both setups now run side by side without any real winner, MiSTer for authenticity and demos, the Pi for tinkering and RTG resolutions.</p>
+<p class="note">Both setups now run side by side without any real winner, MiSTer for authenticity and demos, the Pi for tinkering and RTG resolutions.</p>
 </div>

retro/amiga-modern-platforms/index.njk

@@ -19,7 +19,7 @@ parent: "/retro/"
 <li><strong>The real decision factor</strong>, not speed, but compatibility, stability, and how much you value hardware-accurate timing versus raw throughput.</li>
 </ul>
 
-<p class="redacted-note">Conclusion after digging through all three: if you already own a working MiSTer, there's no compelling reason to chase the newer ARM boards for "better" performance, the practical difference is marginal, and MiSTer's broader core library wins in the long run.</p>
+<p class="note">Conclusion after digging through all three: if you already own a working MiSTer, there's no compelling reason to chase the newer ARM boards for "better" performance, the practical difference is marginal, and MiSTer's broader core library wins in the long run.</p>
 
 <h2>How I Run My Amiga Today</h2>
 <p>For now I'm not running original hardware, I reproduce my Amiga on the <a href="/retro/mist-mister-fpga/">MiSTer FPGA</a> using the Minimig core. My classic Amiga is mapped out there with Workbench and the tools I used back in the day, spread across different configurations and several Workbench versions, so I can revisit exactly how the machine felt across the years.</p>

retro/atari-mega-st-fleet/index.njk

@@ -19,5 +19,5 @@ parent: "/retro/"
 <li><strong>The spare Mega ST 2</strong>, a reserve and donor machine, kept in largely original condition, used to safely test upgrades before they go into the "real" machines.</li>
 </ul>
 
-<p class="redacted-note">Fun fact: two of the "problem" machines turned out to have nothing wrong with the boards at all, a badly soldered CPU socket and a leftover blitter patch bridge were the actual culprits. Moral of the story: check your solder joints twice before blaming the silicon.</p>
+<p class="note">Fun fact: two of the "problem" machines turned out to have nothing wrong with the boards at all, a badly soldered CPU socket and a leftover blitter patch bridge were the actual culprits. Moral of the story: check your solder joints twice before blaming the silicon.</p>
 </div>

retro/atari-monitor-compatibility/index.njk

@@ -19,5 +19,5 @@ parent: "/retro/"
 <li><strong>The universal fix</strong>, an Open Source Scan Converter (OSSC) upsamples the 15kHz signal for any HDMI monitor, at the cost of extra hardware and money.</li>
 </ul>
 
-<p class="redacted-note">If you're chasing 15kHz authenticity, buy the specific panel model people have already confirmed working in the forums, don't trust a spec sheet that just says "supports VGA."</p>
+<p class="note">If you're chasing 15kHz authenticity, buy the specific panel model people have already confirmed working in the forums, don't trust a spec sheet that just says "supports VGA."</p>
 </div>

retro/atari-networking-bbs/index.njk

@@ -48,5 +48,5 @@ terminal emulation is a rabbit hole of character sets, escape sequences,
 and display quirks that haven't been relevant for decades but still
 matter when connecting to a BBS that renders ANSI art.</p>
 
-<p class="redacted-note">If you're chasing BBS nostalgia on real hardware: budget far more patience for the networking layer than for the actual computer. The 1980s hardware is the easy part; convincing 2020s Wi-Fi and modern BBS ANSI dialects to cooperate is the real challenge.</p>
+<p class="note">If you're chasing BBS nostalgia on real hardware: budget far more patience for the networking layer than for the actual computer. The 1980s hardware is the easy part; convincing 2020s Wi-Fi and modern BBS ANSI dialects to cooperate is the real challenge.</p>
 </div>

retro/batocera-living-room/index.njk

@@ -19,5 +19,5 @@ parent: "/retro/"
 <li><strong>Division of labour with MiSTer/MiST</strong>, Batocera wins on convenience and breadth, MiSTer/MiST win on accuracy and low-latency feel for serious sessions.</li>
 </ul>
 
-<p class="redacted-note">If you're building a similar box: don't skip the DAT-file cleanup step. An unsorted TOSEC dump makes browsing physically painful once you cross a few thousand entries.</p>
+<p class="note">If you're building a similar box: don't skip the DAT-file cleanup step. An unsorted TOSEC dump makes browsing physically painful once you cross a few thousand entries.</p>
 </div>

retro/et4000-experiment/index.njk

@@ -22,5 +22,5 @@ parent: "/retro/"
 <h2>The Practical Fallback</h2>
 <p>FPGA cores on MiSTer and MiST only emulate the native ST Shifter, there's no ET4000 emulation on the horizon given the FPGA resources it would require. The real answer for higher resolutions turned out to be software: Hatari running in VDI mode on a Raspberry Pi 400, which comfortably delivers 1280×768 with far more colors and zero PSU drama.</p>
 
-<p class="redacted-note">Lesson learned: "just add a graphics card" on 40-year-old hardware is never "just" anything. The ET4000 project isn't dead, but it's shelved until there's a properly beefed-up power supply and cooling solution to go with it.</p>
+<p class="note">Lesson learned: "just add a graphics card" on 40-year-old hardware is never "just" anything. The ET4000 project isn't dead, but it's shelved until there's a properly beefed-up power supply and cooling solution to go with it.</p>
 </div>

retro/mini-arcade-handheld-roundup/index.njk

@@ -19,5 +19,5 @@ parent: "/retro/"
 <li><strong>The maximalist route</strong>, a Raspberry Pi running RetroPie, or a MiSTer FPGA setup, both scale to tens of thousands of games or hardware-accurate arcade cores respectively, at the cost of more setup effort.</li>
 </ul>
 
-<p class="redacted-note">If a mini-arcade's game list reads like a string of titles you've genuinely never heard of, that's the tell. Real arcade classics have instantly recognisable names, bootlegs hide behind vague, generic-sounding ones.</p>
+<p class="note">If a mini-arcade's game list reads like a string of titles you've genuinely never heard of, that's the tell. Real arcade classics have instantly recognisable names, bootlegs hide behind vague, generic-sounding ones.</p>
 </div>

retro/mist-mister-fpga/index.njk

@@ -19,5 +19,5 @@ parent: "/retro/"
 <li><strong>Known rough edges</strong>, accessory programs loading but not appearing on the desktop, and disabled XBOOT support, are still open items to chase down on the MiST side.</li>
 </ul>
 
-<p class="redacted-note">The takeaway after months of use: don't assume the shinier, newer board wins every category. Sometimes the "older" FPGA implementation is simply the more mature one for a specific chipset.</p>
+<p class="note">The takeaway after months of use: don't assume the shinier, newer board wins every category. Sometimes the "older" FPGA implementation is simply the more mature one for a specific chipset.</p>
 </div>

retro/pimiga-journey/index.njk

@@ -19,5 +19,5 @@ parent: "/retro/"
 <li><strong>The real decision criterion</strong>, not "which is newest" but "do I care more about trainers/cheats (stick with v4's MegaAGS) or about the latest hardware support and polish (go with v5's iGame)". Running both on separate SD cards sidesteps the choice entirely.</li>
 </ul>
 
-<p class="redacted-note">Also worth knowing: getting the display right on an older 4:3 monitor is almost never a Raspberry Pi config.txt problem, it's nearly always an Amiberry/X11 scaling setting. Check the emulator's Integer Scaling option before touching boot config files.</p>
+<p class="note">Also worth knowing: getting the display right on an older 4:3 monitor is almost never a Raspberry Pi config.txt problem, it's nearly always an Amiberry/X11 scaling setting. Check the emulator's Integer Scaling option before touching boot config files.</p>
 </div>

retro/retro-corner-snapshot/index.njk

@@ -29,5 +29,5 @@ parent: "/retro/"
 <h2>How it all connects</h2>
 <p>All machines share the same network infrastructure, with FTP access to the NAS for file transfers. Disk images and software archives are stored centrally and served to individual machines as needed. The MiSTer and MiST both use SD cards for storage, while the original hardware uses CompactFlash adapters or SCSI-to-IDE bridges depending on the machine. The Raspberry Pi 400 accesses the same NFS shares as the other Pis in the flat.</p>
 
-<p class="redacted-note">The honest status update: several open items remain, documenting the exact handheld models, and the full-size <a href="/retro/the-a1200/">A1200</a> is on pre-order ahead of its 4 December 2026 launch. Retro computing, it turns out, is never really "done."</p>
+<p class="note">The honest status update: several open items remain, documenting the exact handheld models, and the full-size <a href="/retro/the-a1200/">A1200</a> is on pre-order ahead of its 4 December 2026 launch. Retro computing, it turns out, is never really "done."</p>
 </div>

shared/base.css

@@ -129,7 +129,7 @@ main > h1 {
   margin-left: 0.5rem;
 }
 
-.redacted-note {
+.note {
   font-size: 0.85rem;
   color: #666;
   background: #f0f4f8;

smarthome/home-dashboard-controls/index.njk

@@ -53,5 +53,5 @@ parent: "/smarthome/"
 <li><strong>Sensors & MQTT</strong>, shortcuts to server-room and balcony sensor readings, bathroom analog values, and background worker/API status pages (HTML and JSON views).</li>
 </ul>
 
-<p class="redacted-note">This dashboard is intentionally simple: static HTML, no login, meant purely for convenience on the local network rather than as a secured control surface. Device names and room assignments are shown for structure; a few outlets are currently unused or marked defective and simply act as placeholders for future devices.</p>
+<p class="note">This dashboard is intentionally simple: static HTML, no login, meant purely for convenience on the local network rather than as a secured control surface. Device names and room assignments are shown for structure; a few outlets are currently unused or marked defective and simply act as placeholders for future devices.</p>
 </div>