Figure 9 combines and eliminates the separate Controllable Component, Life Cycle, Property Set, Testable Object, and Component Identifier interfaces that had appeared in earlier versions. Change Figure 9 to separate interfaces as described in 10.5.2.2-10.5.2.5:
10.5.2.2 Add LifeCycle interface containing:
o APP_Initialize()
o APP_ReleaseObject()
10.5.2.3 Add PropertySet interface containing:
o APP_Query()
o APP_Configure()
10.5.2.4 Add TestableObject interface containing:
o APP_RunTest()
10.5.2.5 Add ControllableComponent interface containing:
o APP_Start()
o APP_Stop()
(Figures available.)

In Table 5: Message and Instance are out of alphabetical order and should be switched. As well as TimeWrap and Timerate.

Correct SysML in figure 7. Make table 3 more closely align with figure 7 by deleting unneeded items.

Original comments from Daniel Brookshier "Diagrams are slightly odd in places, but not bad (overlapping Interface Blocks) but readable as to intent (style as opposed to an error). I don’t have any other items. Sorry, should have said that the style issue was figure 7 (all the API blocks which could be converted to ports). I also just noticed a display issue with the association APP API and DATA TRANSFER API which looks weird (I think this is a display setting).
Also, since figure 7 has changed, many lines in table 3 no longer apply."

BufferSize is undefined as type for nb in MessageQueueCreate calling sequence. The variable nb should be an Integer type.

Template preamble had old URLs with http rather than https and needed to be updated. In References, URLs were inconsistently non-linking.
Figure numbers changed and text needs to be updated to correspond. Error occurred when tables were renumbered.
“Error! Reference source not found “ should have been a reference to the following figure 12.
Declaration text is unnecessarily embedded in a blue box in an inconsistent fashion.

OpaqueValue, a new native type introduced in Issue 2162 (void *
in DII Chapter) for add_arg, was never documented in any of the language
mappings. Language Mapping that claim that the DII interfaces map
according to regular rules need to provide mapping rules for OpaqueValue
and document it. The mapping would simply be OpaqueValue --> (void *) or
equivalent.

Summary: When I was working through Chapter 21, Smalltalk mapping, I found that the
>section, Pseudo-Objects Mapping Overview, was missing (and found that it is
>hidden in the main text of 21.26.1 ...)