Update doc/manual/src/store/file-system-object/content-address.md

doc/manual/src/store/file-system-object/content-address.md

@@ -48,7 +48,8 @@ The exact specification of the Nix Archive format is in `protocols/nix-archive.m
 Serialising the entire tree and then hashing that binary string is not the only option for content addressing, however.
 Another technique is that of a [Merkle graph](https://en.wikipedia.org/wiki/Merkle_tree), where previously computed hashes are included in subsequent byte strings to be hashed.
 
-We can first hash (serialised) child objects, and then hash parent objects using the hashes of their children in the serialisation of the parent.
+In particular, the Merkle graphs can match the original graph structure of file system objects:
+we can first hash (serialised) child file system objects, and then hash parent objects using the hashes of their children in the serialisation (to be hashed) of the parent file system objects.
 
 Currently, there is one such Merkle DAG content addressing method supported.