Apply suggestions from code review

Co-authored-by: Madelyn Olson <[email protected]>
Signed-off-by: Viktor Söderqvist <[email protected]>

tests/unit/dump.tcl

@@ -128,9 +128,8 @@ start_server {tags {"dump"}} {
         #              str len    RDB 222 CRC64 checksum
         #               |   |      |       |
         set bar_dump "\x00\x03bar\xde\x00\x0fYUza\xd3\xec\xe0"
-        catch {r restore foo 0 $bar_dump replace} e
-        set e
-    } {ERR DUMP payload version or checksum are wrong}
+       assert_error {ERR DUMP payload version or checksum are wrong} {r restore foo 0 $bar_dump replace}
+    }
 
     test {RESTORE key with future RDB version, relaxed version check} {
         #              str len    RDB 222 CRC64 checksum

valkey.conf

@@ -551,7 +551,7 @@ rdbchecksum yes
 
 # Valkey can try to load an RDB dump produced by a future version of Valkey.
 # This can only work on a best-effort basis, because future RDB versions may
-# contain information that's not know to the current version. If no new features
+# contain information that's not known to the current version. If no new features
 # are used, it may be possible to import the data produced by a later version,
 # but loading is aborted if unknown information is encountered. Possible values
 # are 'strict' and 'relaxed'. This also applies to replication and the RESTORE