@@ -474,23 +474,28 @@ keys in `hut:rang:clay`, where they are associated with the actual `yaki:clay`,
474and as the values in `hit:dome:clay`, where sequential numerical ids are
474and as the values in `hit:dome:clay`, where sequential numerical ids are
475associated with these.
475associated with these.
477−#### `++yaki:clay`, commit
477+#### `$yaki:clay`, commit
481+ $: p=(list tako) :: parents
480− ++ yaki ,[p=(list tako) q=(map path lobe) r=tako t=@da] :: commit
482+ q=(map path lobe) :: namespace
483+ r=tako :: self-reference
483This is a single commit.
488This is a single commit.
485−`p` is a list of the hashes of the parents of this commit. In most
490+`p` is a `list` of the hashes of the parents of this commit. In most
486cases, this will be a single commit, but in a merge there may be more
491cases, this will be a single commit, but in a merge there may be more
487parents. In theory, there may be an arbitrary number of parents, but in
492parents. In theory, there may be an arbitrary number of parents, but in
488practice merges have exactly two parents. This may change in the future.
493practice merges have exactly two parents. This may change in the future.
489For commit 1, there is no parent.
494For commit 1, there is no parent.
491−`q` is a map of the paths on a desk to the data at that location. If you
496+`q` is a `map` of the `path`s on a desk to the content hashes at that location.
492−understand what a `++lobe:clay` and a `++blob:clay` is, then the type signature
497+If you understand what a `lobe:clay` and a `blob:clay` is, then the type
493−here tells the whole story.
498+signature here tells the whole story.
495`r` is the hash associated with this commit.
500`r` is the hash associated with this commit.