diff --git a/infra/lxc/index.njk b/infra/lxc/index.njk
index db4499a..9398e5a 100644
--- a/infra/lxc/index.njk
+++ b/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="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>
\ No newline at end of file
diff --git a/infra/monitoring/index.njk b/infra/monitoring/index.njk
index ee4906d..5b8b2ba 100644
--- a/infra/monitoring/index.njk
+++ b/infra/monitoring/index.njk
@@ -50,7 +50,7 @@ temperature thresholds) are planned but not yet implemented.</p>
 <h2>Open items</h2>
 <ul>
 <li>Alerting rules are not yet configured for most services.</li>
-<li>The secondary (test) Proxmox host isn't monitored yet, it's usually powered off.</li>
+<li>The secondary (test) Proxmox host isn't monitored yet; it's usually powered off.</li>
 <li>Retention policy for Prometheus data hasn't been tuned.</li>
 </ul>
 
diff --git a/smarthome/kids-rfid-player/index.njk b/smarthome/kids-rfid-player/index.njk
index b0e1b42..57b5cd6 100644
--- a/smarthome/kids-rfid-player/index.njk
+++ b/smarthome/kids-rfid-player/index.njk
@@ -25,7 +25,7 @@ layout: base.njk
 </ul>
 
 <h2>How it works</h2>
-<p>Each RFID card is mapped to a specific audio file on the SD card. Hold a card against the reader and the corresponding story or song starts playing. Hold the RFID keychain against the reader to pause; hold it again to resume. No other buttons exist on the device, the design intentionally minimizes interaction points so even a toddler can use it independently.</p>
+<p>Each RFID card is mapped to a specific audio file on the SD card. Hold a card against the reader and the corresponding story or song starts playing. Hold the RFID keychain against the reader to pause; hold it again to resume. No other buttons exist on the device; the design intentionally minimizes interaction points so even a toddler can use it independently.</p>
 
 <h2>Auto-shutdown behavior</h2>
 <p>The power management distinguishes between two states to avoid unnecessary battery drain:</p>
@@ -35,7 +35,7 @@ layout: base.njk
 </ul>
 
 <h2>The case</h2>
-<p>The enclosure is a custom-built retro-style wooden box, painted by hand. The name "Rocky Box" came from my son, who painted a Paw Patrol character on the front. The design is deliberately quirky and homemade rather than polished, it has character.</p>
+<p>The enclosure is a custom-built retro-style wooden box, painted by hand. The name "Rocky Box" came from my son, who painted a Paw Patrol character on the front. The design is deliberately quirky and homemade rather than polished; it has character.</p>
 
 <h2>What's missing (by design)</h2>
 <ul>
diff --git a/smarthome/octoprint/index.njk b/smarthome/octoprint/index.njk
index 7eae3d4..e7cd77e 100644
--- a/smarthome/octoprint/index.njk
+++ b/smarthome/octoprint/index.njk
@@ -27,7 +27,7 @@ go back from once you've experienced it.</p>
 camera-server project provides two streaming modes: MJPEG for the
 OctoPrint dashboard (low latency, works in any browser) and HLS for
 remote viewing over slower connections. The MJPEG stream is the primary
-way to check on prints, it loads quickly and updates in real time in the
+way to check on prints; it loads quickly and updates in real time in the
 OctoPrint web interface.</p>
 
 <h2>History</h2>
diff --git a/smarthome/tasmota-energy/index.njk b/smarthome/tasmota-energy/index.njk
index 6d5d6b2..22d6ae1 100644
--- a/smarthome/tasmota-energy/index.njk
+++ b/smarthome/tasmota-energy/index.njk
@@ -35,7 +35,7 @@ one strip while still tracking each socket's consumption separately.</p>
 <p>New devices go through a standard conversion flow (from the
 manufacturer's original cloud-dependent firmware to Tasmota) using a
 well-documented community process. It occasionally fails on the first
-attempt due to a transient Wi-Fi handshake issue, retrying resolves it
+attempt due to a transient Wi-Fi handshake issue; retrying resolves it
 without any special handling.</p>
 
 <h2>How the data flows</h2>
@@ -60,8 +60,8 @@ via Flux to display real-time and historical usage charts.</p>
 
 <h2>Why Tasmota over alternatives</h2>
 <p>Tasmota was chosen over alternatives like ESPHome or Tuya firmware for
-several reasons. The local-only control means no cloud dependency, the
-plugs work even if the internet is down. The MQTT integration is mature
+several reasons. The local-only control means no cloud dependency; the
+plugs keep working offline. The MQTT integration is mature
 and well-documented. The energy monitoring sensors are accurate enough
 for home use (typically within 5% of a dedicated energy meter). And the
 firmware supports a wide range of hardware, making it easy to find