diff --git a/zfs-check.md b/zfs-check.md
index a5c28a2..491e3c6 100644
--- a/zfs-check.md
+++ b/zfs-check.md
@@ -17,7 +17,7 @@ Its kind of like sha1sum, but incremental: It generates a sha1 hash per "chunk"
 
 A tool like this wouldn't seem necessary for ZFS: ZFS has full check summing, so you can be 100% sure the data doesn't get corrupted, right?
 
-While this is true to a certain extend, it IS possible that data gets corrupted during transfer with zfs send/recv. This can happen because of certain bugs in ZFS. For example: https://github.com/openzfs/zfs/issues/12762
+While this is true to a certain extend, it IS possible that data gets corrupted during transfer with zfs send/recv. This can happen because of certain bugs in ZFS. For example: https://github.com/openzfs/zfs/issues/12762 and https://github.com/openzfs/zfs/issues/6224
 
 In such cases the checksums are still OK, but they are of the wrong (corrupt) data.