@@ -441,25 +441,27 @@ associated with those hashes.
441441
442442`busy` tracks whether or not the request is currently being fulfilled.
443443
444−#### `++rang:clay`, data store
444+#### `$rang:clay`, data repository
445445
446446```hoon
447− ++ rang $: hut=(map tako yaki) ::
448− lat=(map lobe blob) ::
449− == ::
447+ +$ rang :: repository
448+ $: hut=(map tako yaki) :: changes
449+ lat=(map lobe blob) :: data
450+ == ::
450451```
451452
452−This is a set of data keyed by hash. Thus, this is where the "real" data
453+This is a data repository keyed by hash. Thus, this is where the "real" data
453454is stored, but it is only meaningful if we know the hash of what we're
454455looking for.
455456
456−`hut` is a map from hashes to commits. We often get the hashes from
457−`hit:dome:clay`, which keys them by logical id. Not every commit has an id.
457+`hut` is a `map` from commit hashes (`tako`s) to commits (`yaki`s). We often get
458+the hashes from `hit:dome`, which keys them by numerical id. Not every commit
459+has an numerical id.
458460
459−`lat` is a map from hashes to the actual data. We often get the hashes
460−from a `++yaki`, a commit, which references this map to get the data.
461−There is no `++blob:clay` in any `++yaki:clay`. They are only accessible through
462−this map.
461+`lat` is a `map` from content hashes (`lobe`s) to the actual content (`blob`s).
462+We often get the hashes from a `yaki`, which references this `map` to get the
463+data. There is no `blob` in `yaki:clay`. They are only accessible through
464+`lat`.
463465
464466#### `++tako:clay`, commit reference
465467