I would guess the code once contained a person field, that has since been removed, and the documentation hasn't been fully updated to reflect this; a few of the changes fix just that:
fixed model.item being referred to as model.person
removed the additional save() function explanation that wasn't needed (there is no person field that needs to be changed to item).
Other changes:
changed model.rebind() to model.rollback() as this is the code that is truly analogous to model.rebind { item = person2 }
removed the passage that stated the PersonModel code is not included in the code (it is); as well as the passage in the PersonModel Implementation paragraph
changed the PersonModel paragraph to explain the updated code (using Class::property instead of lambdas)
lots of fixes due to the ItemViewModel being seen as a ViewModel; once again, I would guess the code used to be for a ViewModel and was updated for an ItemViewModel
added explanations for the low-level ViewModel (since it is no longer used; the ItemViewModel is used and explained instead) and moved the paragraph explaining the differences here
I would guess the code once contained a
personfield, that has since been removed, and the documentation hasn't been fully updated to reflect this; a few of the changes fix just that:model.itembeing referred to asmodel.personsave()function explanation that wasn't needed (there is nopersonfield that needs to be changed toitem). Other changes:model.rebind()tomodel.rollback()as this is the code that is truly analogous tomodel.rebind { item = person2 }PersonModelcode is not included in the code (it is); as well as the passage in thePersonModel ImplementationparagraphPersonModelparagraph to explain the updated code (usingClass::propertyinstead of lambdas)ItemViewModelbeing seen as aViewModel; once again, I would guess the code used to be for aViewModeland was updated for anItemViewModelViewModel(since it is no longer used; theItemViewModelis used and explained instead) and moved the paragraph explaining the differences here