Fix #2413, Update Dev Guide to fix out-of-date references and broken

links

Author: thnkslprpt

docs/README_functionaltest.md

@@ -19,10 +19,6 @@ This must be the first library loaded for any functional test.
 - `cfe_testcase`: a CFE-compatible library implementing test cases for CFE core apps.
 This must be loaded after `cfe_assert`.
 
-- `cfe_testrunner`: a CFE application that actually executes the tests.  This is a very
-simple app that waits for CFE startup to complete, then executes all registered test
-cases.  It also must be loaded after `cfe_assert`.
-
 
 ## Example startup script entries
 

docs/cFE Application Developers Guide.md

@@ -163,7 +163,7 @@
   \ref cfeevsugmsgfilter (only the Binary Filtering Scheme
   exists currently).   Note that applications are limited in the number of events that
   they can register for filtering (see #CFE_PLATFORM_EVS_MAX_EVENT_FILTERS in cfe_platform_cfg.h
-  for the mission defined limit).  The filtering method uses a mask to determine if the
+  for the mission-defined limit).  The filtering method uses a mask to determine if the
   message is forwarded to the software bus, making it available in telemetry (see
   \ref cfeevsugmsgfilter for a description on filtering).  Commands are available to
   \link #CFE_EVS_SET_FILTER_CC modify the filter mask \endlink for any registered event.

docs/src/cfe_evs.dox

@@ -106,10 +106,10 @@
 
    \section cfebackground_s1 Core Flight Executive (cFE) Goals
 
-   The main long term goal of the cFE is to form the basis for a platform and project
+   The main long-term goal of the cFE is to form the basis for a platform and project
    independent reusable software framework. The cFE with the OSAL allow the development
    of portable embedded system software that is independent of a particular Real Time
-   Operating System and hardware platform. A secondary long term goal is to create a
+   Operating System and hardware platform. A secondary long-term goal is to create a
    standardized, product-line approach for development of embedded aerospace flight
    software. <BR>
 
@@ -121,7 +121,7 @@
    promoting the growth of the application and library layers where new applications, libraries,
    tools, and lessons learned can be contributed and shared. <BR>
 
-   It is important for application developers to realize the long term and functional
+   It is important for application developers to realize the long-term and functional
    goals of the cFE.  With a standard set of services providing a standard API, all
    applications developed with the cFE have an opportunity to become useful on
    future missions through code reuse.  In order to achieve this goal,

docs/src/cfe_frontpage.dox

@@ -44,7 +44,7 @@
              cFE following a Processor Reset.
      <TR>
         <TD> \anchor cfeadg_crc Cyclic Redundancy Check
-        <TD> A polynomial based method for checking that a data set
+        <TD> A polynomial-based method for checking that a data set
              has remained unchanged from one time period to another.
      <TR>
         <TD> \anchor cfeadg_developer Developer

docs/src/cfe_glossary.dox

@@ -116,7 +116,7 @@
   The default table type for a cFE Application to use is a single buffered table.  The principle
   advantage of a single buffered table is that it can share one of several shared table buffers
   for uploaded and pending table images.  Since many cFE Applications have relatively small tables
-  that are not changed at time critical moments or are not changed very often during a mission,
+  that are not changed at time-critical moments or are not changed very often during a mission,
   single buffered tables represent the most memory resource efficient method of being managed.
 
   The number of single buffered tables that can have inactive table images being manipulated at one

docs/src/cfe_tbl.dox

@@ -68,7 +68,7 @@
   easily be manipulated and utilized. These components include:
 
   The <B>Ground Epoch</B> is an arbitrary date and time that establishes the zero point
-  for spacecraft time calculations.  The selection of the epoch is mission specific,
+  for spacecraft time calculations.  The selection of the epoch is mission-specific,
   although in the past, it was common to select the same epoch as defined for the
   Operating System used by the computers hosting the ground system software.  Recent
   mission epoch selections have also included using zero seconds after midnight,
@@ -247,7 +247,7 @@
   #define CFE_MISSION_TIME_CFG_DEFAULT_UTC  TRUE
   \endverbatim
 
-  The choice of time format is a mission specific decision and is not directly
+  The choice of time format is a mission-specific decision and is not directly
   affected by the hardware configuration.
 
   \sa #CFE_MISSION_TIME_CFG_DEFAULT_TAI, #CFE_MISSION_TIME_CFG_DEFAULT_UTC <BR>
@@ -659,7 +659,7 @@
   to the current STCF.  In addition there is a 1Hz adjustment
   (#CFE_TIME_ADD_1HZ_ADJUSTMENT_CC and #CFE_TIME_SUB_1HZ_ADJUSTMENT_CC)
   that can be made to the STCF to compensate for oscillator drift.
-  Mission specific ground correlation should be used to assist in
+  Mission-specific ground correlation should be used to assist in
   determining the proper values to use. The Leap Seconds should be
   set to the current TAI-UTC. Note that the International Earth
   Rotation and Reference Systems Service Bulletin C, which defines

docs/src/cfe_time.dox

@@ -1,6 +1,6 @@
 #---------------------------------------------------------------------------
 # Each of the following assignment statements should have the documentation
-# mnemonic on the left followed by the mission specific command mnemonic
+# mnemonic on the left followed by the mission-specific command mnemonic
 # on the right of the equals operator.
 #
 # FORMATTING DETAILS TO REMEMBER!

docs/src/mnem_maps/cfe_es_cmd_mnem_map

@@ -1,6 +1,6 @@
 #---------------------------------------------------------------------------
 # Each of the following assignment statements should have the documentation
-# mnemonic on the left followed by the mission specific telemetry mnemonic
+# mnemonic on the left followed by the mission-specific telemetry mnemonic
 # on the right of the equals operator.
 #
 # FORMATTING DETAILS TO REMEMBER!

docs/src/mnem_maps/cfe_es_tlm_mnem_map

@@ -1,6 +1,6 @@
 #---------------------------------------------------------------------------
 # Each of the following assignment statements should have the documentation
-# mnemonic on the left followed by the mission specific command mnemonic
+# mnemonic on the left followed by the mission-specific command mnemonic
 # on the right of the equals operator.
 #
 # FORMATTING DETAILS TO REMEMBER!