Fix nasa#559, resolve doxygen warnings

lbleier-GSFC · Apr 28, 2020 · 7df54d6 · 7df54d6
1 parent ecb8866
commit 7df54d6
Show file tree

Hide file tree

Showing 5 changed files with 238 additions and 236 deletions.
diff --git a/docs/src/cfe_api.dox b/docs/src/cfe_api.dox
@@ -1,5 +1,5 @@
 /**
-  \page cfeapi cFE Application Programmer's Interface (API) Reference 
+  \page cfeapi cFE Application Programmer's Interface (API) Reference
   <H4> Executive Services API </H4>
   <UL>
     <LI> \ref CFEAPIESEntryExit

diff --git a/docs/src/cfe_sb.dox b/docs/src/cfe_sb.dox
@@ -532,7 +532,7 @@
            can get confusing. How can I be sure that the correct address is given for this
            parameter.
         </B><TR><TD WIDTH="5%"> &nbsp; <TD WIDTH="95%">
-           Typically a caller declares a ptr of type cfe_sb.h::CFE_SB_Msg_t  (i.e. CFE_SB_Msg_t *Ptr)
+           Typically a caller declares a ptr of type CFE_SB_Msg_t (i.e. CFE_SB_Msg_t *Ptr)
            then gives the address of that pointer (&Ptr) as this parameter. After a successful
            call to #CFE_SB_RcvMsg, Ptr will point to the first byte of the software bus message
            header. This should be used as a read-only pointer. In systems with an MMU, writes