From 239354d20598912cd1473a65ea1fe56956edff21 Mon Sep 17 00:00:00 2001 From: iris Date: Tue, 8 Sep 2026 13:24:35 +0200 Subject: [PATCH] docs/networking: drop leading 'So' tripping write-good.So argus caught this on PR review: the passive-to-active rewrite of the packet-authentication sentence in snapshot-store.md started with 'So ', which write-good.So flags as a new error not present on main. Drop the leading word; meaning is unchanged. --- docs/networking/snapshot-store.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/networking/snapshot-store.md b/docs/networking/snapshot-store.md index 599b1e26..72adf238 100644 --- a/docs/networking/snapshot-store.md +++ b/docs/networking/snapshot-store.md @@ -84,8 +84,8 @@ deliberate rather than an omission. WireGuard's cryptokey routing already binds a peer's source address to its public key: the swarm module configures each peer with `allowedIPs = [ peer.wireguardAddress ]`, so a packet arriving from -that address provably came from the holder of that private key. So by -the time a packet reaches the receiver, the kernel has already +that address provably came from the holder of that private key. By the +time a packet reaches the receiver, the kernel has already authenticated it. Layering TLS client certs on top would authenticate _the same fact_ a