Unverified Commit 5166b11a authored by Jesse Mapel's avatar Jesse Mapel Committed by GitHub
Browse files

Fixed typos in ControlNetVersioner documentation

parent 9def5041
Loading
Loading
Loading
Loading
+9 −9
Original line number Original line Diff line number Diff line
@@ -114,7 +114,7 @@ namespace Isis {
   *   </ol>
   *   </ol>
   *   </li>
   *   </li>
   *   <li>Write a Pvl header into the original blank header at the start of the
   *   <li>Write a Pvl header into the original blank header at the start of the
   *        file. This header contains a flag indicating the network is a
   *        file. This header contains: a flag indicating the network is a
   *        protobuf formatted network, the version of the format, the byte
   *        protobuf formatted network, the version of the format, the byte
   *        offset and size of the protobuf header, the byte offset and
   *        offset and size of the protobuf header, the byte offset and
   *        size of the block of protobuf control points, and general
   *        size of the block of protobuf control points, and general
@@ -186,7 +186,7 @@ namespace Isis {
   *
   *
   * <h3>Control Network File Format History</h3>
   * <h3>Control Network File Format History</h3>
   *
   *
   * Prior to the creation of this versioning class, which was release with
   * Prior to the creation of this versioning class, which was released with
   *   ISIS 3.2.2, all control network files were Pvl formatted text files.
   *   ISIS 3.2.2, all control network files were Pvl formatted text files.
   *   Reading and writing these files was handled by the ControlNet, ControlPoint,
   *   Reading and writing these files was handled by the ControlNet, ControlPoint,
   *   and ControlMeasure classes. As the file format was changed, those
   *   and ControlMeasure classes. As the file format was changed, those
@@ -243,18 +243,18 @@ namespace Isis {
   *   <ol>
   *   <ol>
   *     <li>
   *     <li>
   *     <em>Pvl File Header:</em> The file starts with a Pvl formatted header
   *     <em>Pvl File Header:</em> The file starts with a Pvl formatted header
   *     that contains offsets to the binary components of the file. This
   *     that contains offsets to the binary components of the file and the
   *     header may also contain general information about the control network.
   *     version number of the file. This header may also contain general
   *     This information is only for user reference is not used when reading
   *     information about the control network that is only for user reference
   *     the file.
   *     is not used when reading the file.
   *     </li>
   *     </li>
   *     <li>
   *     <li>
   *     <em>Protobuf Core:</em> After the Pvl header is the protobuf core that
   *     <em>Protobuf Core:</em> After the Pvl header is the protobuf core that
   *     contains the majority of the network data. This is a hierarchical
   *     contains the majority of the network data. This is a hierarchical
   *     structure with general network information such as the network
   *     structure with general network information such as the network
   *     description at the top level. Below that is the control point
   *     description at the top level. Below that is the control point
   *     information. Lastly, is the control measure information. This
   *     information. The lowest level contains the control measure information.
   *     structure is defined by <em>ControlNetFileProtoV0001.proto</em>.
   *     This structure is defined by <em>ControlNetFileProtoV0001.proto</em>.
   *     </li>
   *     </li>
   *     <li>
   *     <li>
   *     <em>Protobuf Log Data:</em> The final component of the file contains
   *     <em>Protobuf Log Data:</em> The final component of the file contains
@@ -301,7 +301,7 @@ namespace Isis {
   *     the Protobuf Core which contains all of the control point and control
   *     the Protobuf Core which contains all of the control point and control
   *     measure information. This is structured as consecutive protobuf
   *     measure information. This is structured as consecutive protobuf
   *     messages where each message contains all of the information for a
   *     messages where each message contains all of the information for a
   *     control point and its control measures. Because, protobuf messages
   *     control point and its control measures. Because protobuf messages
   *     are not self-delimiting, the size of each message must be known prior
   *     are not self-delimiting, the size of each message must be known prior
   *     to parsing the Protobuf Core. The control point messages are defined
   *     to parsing the Protobuf Core. The control point messages are defined
   *     by <em>ControlPointFileEntryV0002.proto</em>.
   *     by <em>ControlPointFileEntryV0002.proto</em>.