message: mstarch: adding types documentation
diff: @@ -74,8 +74,9 @@ while a successful response moves to the next command in the sequence.
  Events represent a log of activities taken by the embedded system. Events can be thought of in the same way as a program
  execution log in that they enable the ability to trace the systems execution. Events are sent out of the system via the
  `Svc::ActiveLogger` component and components defining commands should hook up the log port to it. If console logging is
  -desired, the text log port can be hooked up to the `Svc::PassiveConsoleTextLogger` component. Events are defined by the
  -following properties:
  +desired, the text log port can be hooked up to the `Svc::PassiveConsoleTextLogger` component. Events are defined per
  +component and are typically used to capture what the component is doing. Events can be sporadic; however, should all be
  +captured for downlink. Events are defined by the following properties:
  1. id: a numeric id uniquely define this event. It is automatically offset by the component's base id to ensure global
  uniqueness.
  @@ -92,6 +93,8 @@ uniqueness.
  with the event. These are injected into the format string for a full text representation of the event.
  5. format string: a C-style format string used to reconstruct a text version of the event.
  +**Note:** the use of events to severity levels are based on the judgement of the system designer.
  +
  Code in the component-specific generated base class provides a function to call to emit each event defined by the
  component. This function expects an argument to be supplied for each argument defined by the event. The code generator
  automatically adds ports or retrieving a time tag and sending events. There are two independent ports for sending
  @@ -116,7 +119,8 @@ the port queue and sends it to the ground.
  Channels, also known as Telemetry Channels, or just Telemetry, represent the current reading of some portion of system
  state. This state is either restricted to "send on change" or "send per update" even if the update is already the
  -current value. Channels are id, time, and value triples and are defined per component with the following properties:
  +current value. Channels are broken-up per component and are typically sampled at a set rate and dowlinked. Channels are
  +id, time, and value triples and are defined per component with the following properties:
  1. id: the unique id of the channel. This is offset by the base id of the component for global uniqueness.
  2. name: the unique text name of the channel. This is prepended with the component name for global uniqueness.
  @@ -168,6 +172,7 @@ system during initialization. The initialization subsequently calls *loadParamet
  Components can set and retrieve parameters. The parameter manager saves the updated values to the file system via the
  command.
  +
  ## A Note On Serialized Ports
  The `Svc` components use serialize ports to generically handle port data of different types to support uplink and
  