Updating some of comms library doc links.

Author: arobenko

tutorials/tutorial13/README.md

@@ -157,7 +157,7 @@ starting from the first message having the same numeric ID. In other word the in
 
 **SIDE NOTE**: The [comms::frame::MsgIdLayer](https://commschamp.github.io/comms_doc/classcomms_1_1protocol_1_1MsgIdLayer.html)
 used by the framing is capable of returning the detected index / offset information via special extra parameters
-(see [comms::frame::msgIndex()](https://commschamp.github.io/comms_doc/namespacecomms_1_1protocol.html)). These parameters 
+(see [comms::frame::msgIndex()](https://commschamp.github.io/comms_doc/namespacecomms_1_1frame.html)). These parameters 
 are used by the processing functions from [comms/process.h](https://commschamp.github.io/comms_doc/process_8h.html) to 
 get the numeric message ID and the index (offset) information in order to perform the message dispatch. Extracting this 
 information is a bit out of scope for this tutorial and will be covered in other later one.

tutorials/tutorial18/README.md

@@ -51,9 +51,9 @@ std::size_t ServerSession::processInputImpl(const std::uint8_t* buf, std::size_t
 The [read()](https://commschamp.github.io/comms_doc/classcomms_1_1protocol_1_1ProtocolLayerBase.html)
 member function of every protocol layer receives a variadic `extraValues` last parameter, which can be 
 used to add several output parameters to the function. In this example the 
-[comms::frame::msgId()](https://commschamp.github.io/comms_doc/namespacecomms_1_1protocol.html) is used 
+[comms::frame::msgId()](https://commschamp.github.io/comms_doc/namespacecomms_1_1frame.html) is used 
 to add `msgId` local variable as an output parameter for the message numeric ID. Also the 
-[comms::frame::msgIndex()](https://commschamp.github.io/comms_doc/namespacecomms_1_1protocol.html)
+[comms::frame::msgIndex()](https://commschamp.github.io/comms_doc/namespacecomms_1_1frame.html)
 is used to add `msgIdx` local variable as an output parameter for the index of the message (offset in 
 the tuple of the input messages starting from the first message sharing the same ID).
 Later down the code both `msgId` and `msgIdx` values are used to dispatch message object into the 
@@ -177,8 +177,8 @@ struct DataViewDefaultOptionsT : public TBase
 - The [COMMS Library](https://github.com/commschamp/comms) provides multiple ways to access 
   some or all of the framing fields.
 - The `read()` member function can receive and update selected output parameters via 
-  [comms::frame::msgId()](https://commschamp.github.io/comms_doc/namespacecomms_1_1protocol.html), 
-  [comms::frame::msgIndex()](https://commschamp.github.io/comms_doc/namespacecomms_1_1protocol.html), etc...
+  [comms::frame::msgId()](https://commschamp.github.io/comms_doc/namespacecomms_1_1frame.html), 
+  [comms::frame::msgIndex()](https://commschamp.github.io/comms_doc/namespacecomms_1_1frame.html), etc...
 - In order to get **all** the frame fields the 
   [readFieldsCached()](https://commschamp.github.io/comms_doc/classcomms_1_1protocol_1_1ProtocolLayerBase.html)
   member function needs to be used.

tutorials/tutorial5/README.md

@@ -412,12 +412,12 @@ when the code is recompiled.
 - Every `<frame>` uses internal layers to specify transport fields and their 
   roles.
 - The generated C++ code of the frame(s) resides in [include/&lt;namespace&gt;/frame](include/tutorial5/frame) folder and
-  uses classes from [comms::frame](https://commschamp.github.io/comms_doc/namespacecomms_1_1protocol.html)
+  uses classes from [comms::frame](https://commschamp.github.io/comms_doc/namespacecomms_1_1frame.html)
   namespace to define the layers.
 - The defined framing layers wrap one another, as the result the outermost layer is used 
   to handle the whole transport framing.
 - For available frame API reference open the documentation of the 
-  [outermost layer](https://commschamp.github.io/comms_doc/namespacecomms_1_1protocol.html) type.
+  [outermost layer](https://commschamp.github.io/comms_doc/namespacecomms_1_1frame.html) type.
 - The polymorphic behavior of the common interface class may influence the ability of the 
   frame to perform its `write()` operation. 
 - When write operation returns [commms::ErrorStatus::UpdateRequired](https://commschamp.github.io/comms_doc/ErrorStatus_8h.html)