Each object entered in the document would have to follow different phases of
lifecycle:
(a) Inserting/creating/setting
(b) modifying/editing/updating
(c) removing/deleting/clearing/resetting

In fact, the liffecycle concept applies to the properties of a given object also.

In other words, the lifecycle concept applies to-
>> Objects such as images, text, frames, tables, etc... 
>> Their properties such as format, style, etc..

Therefore, any help topic discussing the item MUST describe ALL the phases, 
or have a cross-reference to other topics that contain this description. 

In other words, regardless of WHERE the user starts reading, the help file/User
guide should be able to describe the entire lifecycle seamlessly.

But the OOo documentation leaves many topics incomplete in this regard.
Some examples (help file):
(a) the "inserting cross-references" topic page of the help file does not have a
link to "deleting cross-references".
(b) try searching for "removing hyperlink"

Desired: Review each topic from this criteria-- "Have we addressed the three
essential stages of its lifecycle?"

Suggested alternative ways to implement this:
1. Do not bury this in the description: provide a linkage to bottom.
2. Have a "standard" structure for each help page. For example-
>> Title
>> What it is (definition), 
>> why/where needed (i.e. scenarios for using it), 
>> Description of lifecycle phases, and how to DO it. (how to use the
menus/toolbar buttons, etc)
>> "See also-" section (to describe similar/opposite effect achieved by other
commands)