UML25 — Location: Page 330, 331, 333, 14.2.3, Page 347, 14.2.4, Page 375, 14.5 PseudostateKind

Title: History State described multiple times
Summary The History State is described here:
State history (p. 330)
Entering a state (p. 331)
PseudostateKind (p. 333)
History State Notation (p. 347)
PseudoStateKind classifier description (p 357).

Though it is OK to have descriptions in the various predefined sections, it seems that in this case I need to read all places to fully understand the history state.
On other occasions the wording is slightly different (e.g., containing state-owning state), so that the reader wonders, whether there is a different meaning.
On page 333 the description of deepHistory is incomplete: It doesn’t describe the default history state. This is described at other places, but not describing it here misleads the reader to think, that only shallowHistory has this feature.

Proposed Res Reduce the number of places. Focus the description on the purpose of the section, hyperlink to other parts of the description where necessary.

Source: axel.scheithauer@oose.de

Agreed: the redundancy is both a maintenance problem and can be confusing due to minor discrepancies
between the texts. Since the duplicate text in question describes the semantics of the pseudostates, it should
be retained in the Semantics section (14.2.3) of the StateMachines chapter and removed from the Classifier
Descriptions section (14.5). It would be convenient to add some kind of hyperlink from the Classifier
Descriptions entry to the corresponding Semantics entry, but, since the descriptions text is auto-generated
from the metamodel, this would be rather difficult to achieve technically. However, it is expected that
readers interested in the semantics of the individual literals will naturally assume that they should refer to
the Semantics section