Delete the "load-bearing" filler

test/src/lib/LibFs.buildFileForContract.t.sol

@@ -135,9 +135,9 @@ contract LibFsBuildFileForContractTest is Test {
     }
 
     /// First generation for a contract is the normal case: nothing is at the
-    /// path yet. Removing a file that is not there reverts, so the existence
-    /// check in front of the removal is load bearing and this is what proves
-    /// it.
+    /// path yet. Removing a file that is not there reverts, so dropping the
+    /// existence check in front of the removal would make this case revert.
+    /// This test is what proves it.
     function testBuildFileForContractFreshPath() external {
         string memory name = "LibFsBuildFresh";
         cleanup(name);

test/src/lib/LibFs.buildFileForTaggedContract.t.sol

@@ -118,8 +118,9 @@ contract LibFsBuildFileForTaggedContractTest is Test {
 
     /// The first generation for a tag has no directory yet, which is the normal
     /// case for a release: the snapshot directory is created by the run that
-    /// fills it. `vm.writeFile` does not create a missing parent, so the
-    /// directory creation is load bearing and this is what proves it.
+    /// fills it. `vm.writeFile` does not create a missing parent, so dropping
+    /// the directory creation would make this case fail to write. This test is
+    /// what proves it.
     function testBuildFileForTaggedContractCreatesTheTagDir() external {
         string memory tag = "0_1_1$taggedFreshDir";
         cleanup(tag);