@@ -474,23 +474,28 @@ keys in `hut:rang:clay`, where they are associated with the actual `yaki:clay`,
474474and as the values in `hit:dome:clay`, where sequential numerical ids are
475475associated with these.
476476
477−#### `++yaki:clay`, commit
477+#### `$yaki:clay`, commit
478478
479479```hoon
480− ++ yaki ,[p=(list tako) q=(map path lobe) r=tako t=@da] :: commit
480+ +$ yaki :: commit
481+ $: p=(list tako) :: parents
482+ q=(map path lobe) :: namespace
483+ r=tako :: self-reference
484+ t=@da :: date
485+ == ::
481486```
482487
483488This is a single commit.
484489
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
486491cases, this will be a single commit, but in a merge there may be more
487492parents. In theory, there may be an arbitrary number of parents, but in
488493practice merges have exactly two parents. This may change in the future.
489494For commit 1, there is no parent.
490495
491−`q` is a map of the paths on a desk to the data at that location. If you
492−understand what a `++lobe:clay` and a `++blob:clay` is, then the type signature
493−here tells the whole story.
496+`q` is a `map` of the `path`s on a desk to the content hashes at that location.
497+If you understand what a `lobe:clay` and a `blob:clay` is, then the type
498+signature here tells the whole story.
494499
495500`r` is the hash associated with this commit.
496501