Whenever an association is mapped at both ends, one of these ends is designated as active and the other as passive. (The passive end is the one that is displayed using mappedBy= or inverse="true" )
Hibernation does not update the passive end of the collection when updating the active end and cannot update it, because it can detect such changes only during a reset. Therefore, it is considered good practice to call code to change both ends of the association to ensure that the object model is always in a consistent state.
Hibernation alone does not care about whether the two ends of the association are consistent, since it only looks at the active end when flushing the database.
When comparing a one-to-many association, the one-to-many end should be marked as passive. The section from the sleep guide you are referencing is trying to explain why.
source share