diff --git a/src/lib/LibRainDeploySnapshot.sol b/src/lib/LibRainDeploySnapshot.sol
index cb8d8d1..454d1b5 100644
--- a/src/lib/LibRainDeploySnapshot.sol
+++ b/src/lib/LibRainDeploySnapshot.sol
@@ -1282,7 +1282,7 @@ library LibRainDeploySnapshot {
     ///
     /// Strictly greater, so the newest tag itself is refused too: equality is
     /// not "follows". `SnapshotAlreadyFrozen` also refuses that one, and both
-    /// must hold — neither guard is load bearing alone.
+    /// must hold — dropping either one leaves cases the other does not refuse.
     ///
     /// The record root and the tag are parameters, so the refusal is reachable
     /// without a record on disk to re-cut or a `foundry.toml` to rewrite, for
@@ -1307,9 +1307,9 @@ library LibRainDeploySnapshot {
     /// in that order, in one call.
     ///
     /// Every guard runs, and every byte that will be written is in hand, BEFORE
-    /// `<tag>/` is created. That ordering is load bearing rather than tidy.
-    /// Filesystem cheatcodes are not undone by a revert, so a throw once the
-    /// directory exists leaves a partial record behind — and a partial record is
+    /// `<tag>/` is created. Filesystem cheatcodes are not undone by a revert,
+    /// so a throw once the directory exists leaves a partial record behind —
+    /// and a partial record is
     /// a frozen tag, which `SnapshotAlreadyFrozen` then refuses the retry of.
     /// The only exit from that state is deleting a directory this design calls
     /// append-only, so the release is wedged by the failure rather than merely
diff --git a/test/src/lib/GeneratedSnapshotShape.t.sol b/test/src/lib/GeneratedSnapshotShape.t.sol
index d179db1..60168f7 100644
--- a/test/src/lib/GeneratedSnapshotShape.t.sol
+++ b/test/src/lib/GeneratedSnapshotShape.t.sol
@@ -177,8 +177,8 @@ contract GeneratedSnapshotShapeTest is RegistryDeploySuites, Test {
     /// selects is the contract the candidate is anchored to.
     ///
     /// `artifactPath` is the one field of a suite that nothing derives, and
-    /// until this assertion nothing checked either. It is load bearing twice
-    /// over: `LibRainDeploy` prints it as the `forge verify-contract` command a
+    /// until this assertion nothing checked either. Two things read it:
+    /// `LibRainDeploy` prints it as the `forge verify-contract` command a
     /// human runs against a freshly broadcast contract, and
     /// `candidateContractName` above takes the contract this whole shape spec
     /// is about out of it. Only the `:<Name>` half was ever read by a check —
diff --git a/test/src/lib/LibRainDeploySnapshot.t.sol b/test/src/lib/LibRainDeploySnapshot.t.sol
index 507cefd..26b1249 100644
--- a/test/src/lib/LibRainDeploySnapshot.t.sol
+++ b/test/src/lib/LibRainDeploySnapshot.t.sol
@@ -1957,9 +1957,8 @@ contract LibRainDeploySnapshotTest is Test {
 
     /// The newest tag ITSELF MUST be refused: equality is not "follows". The
     /// fail-safe boundary, and the one case `SnapshotAlreadyFrozen` also
-    /// refuses — both must hold, so neither is load bearing alone and this one
-    /// holds against a record root whose directories are not where a freeze
-    /// would look for them.
+    /// refuses — both must hold, and this one holds against a record root
+    /// whose directories are not where a freeze would look for them.
     function testCheckReleaseFollowsRecordRefusesTheNewestTagItself() external {
         writeFixture(string.concat(EQUAL_FIXTURE_ROOT, "/0_2_0/", FIXTURE_CONTRACT, ".sol"));