commenting out mermaid is a fail - need to fully remove for doxy

Author: gigapod

README.md

@@ -35,58 +35,14 @@ Implemented using C++, the SparkFun toolkit follows a simple two layered approac
 
 ![Core Architecture](docs/images/rm_img_01.png)
 
-<!-- ```mermaid
----
-title: General Architecture Structure
----
-classDiagram
-    class CoreToolkit["Core Toolkit Interfaces"] 
-    class PlatformOne["Platform Implementation"]
-    CoreToolkit <|-- PlatformOne
-
-``` -->
 And as additional platforms are added, they also implement/inherit from the SparkFun Toolkit Core.
 
 ![Multi-Platform Structure](docs/images/rm_img_02.png)
 
-<!-- ```mermaid
----
-title: Multi-Platform Structure
----
-classDiagram
-    class CoreToolkit["Core Toolkit Interfaces"]
-    class PlatformOne["Platform One"]
-    class PlatformTwo["Platform Two"]
-
-    CoreToolkit <|-- PlatformOne
-    CoreToolkit <|-- PlatformTwo
-``` -->
-
 When using the SparkFun Toolkit, the intent is for the implementation to follow the same pattern: A platform independent layer that works with the SparkFun Toolkit core, and a platform specific layer that utilizes the SparkFun Toolkit platform specific implementation. 
 
 ![Application Structure](docs/images/rm_img_03.png)
 
-<!-- ```mermaid
----
-title: Application Structure
----
-classDiagram
-    direction TD
-    note for ApplicationCore "Application Logic"
-    class ApplicationCore["Application Core"]
-    class CoreToolkit["Core Toolkit Interfaces"] 
-
-    note for CoreToolkit "SparkFun Toolkit"
-    class ApplicationPlatform["Application Platform"]
-    style ApplicationPlatform fill:#909090
-    class PlatformOne["Platform Implementation"]
-    style PlatformOne fill:#909090
-    
-    CoreToolkit <|-- PlatformOne
-    ApplicationCore <-- > ApplicationPlatform
-
-``` -->
-
 If/when the application is moved to another platform, just the platform specific logic needs implementation. 
 
 ## Documentation