fix: feedback from doc

packages/contracts-bedrock/test/properties/helpers/CompatibleAssert.t.sol

@@ -5,7 +5,7 @@ import { console } from "forge-std/console.sol";
 
 /// @title CompatibleAssert
 /// @notice meant to add compatibility between medusa assertion tests and
-/// foundry invariant test's required arquitecture
+/// foundry invariant test's required architecture
 contract CompatibleAssert {
     bool public failed;
 
@@ -15,10 +15,13 @@ contract CompatibleAssert {
 
     function compatibleAssert(bool condition, string memory message) internal {
         if (!condition) {
+            if(bytes(message).length != 0) console.log("Assertion failed: ", message);
+            else console.log("Assertion failed");
+
             // for foundry to call & check
             failed = true;
+
             // for medusa
-            console.log("Assertion failed: ", message);
             assert(false);
         }
     }

packages/contracts-bedrock/test/properties/medusa/handlers/Protocol.t.sol

@@ -155,6 +155,8 @@ contract ProtocolHandler is TestBase, StdUtils, Actors {
     {
         // this salt would be used in production. Tokens sharing it will be bridgable with each other
         bytes32 realSalt = keccak256(abi.encode(remoteToken, name, symbol, decimals));
+        // Foundry invariant erroneously show other unrelated invariant breaking
+        // when this deployment fails due to a create2 collision, so we revert eagerly instead
         require(MESSENGER.superTokenAddresses(chainId, realSalt) == address(0), "skip duplicate deployment");
 
         // what we use in the tests to walk around two contracts needing two different addresses