lint formatting fixes

Design-Architecture.md

@@ -1,15 +1,19 @@
-##### Project:
-::PROJECTNAME(Home)
+##### Project
+
+::PROJECT-NAME(Home)
+
+##### Internal Release Number
 
-##### Internal Release Number:
 ::X.Y.Z
 
-##### Related Documents:
+##### Related Documents
+
 - [Design](Design) > Design Architecture
 - [Software Requirements Specification](SRS)
 - [Glossary](Glossary)
 - ::LINKS TO RELEVANT STANDARDS
 - ::LINKS TO OTHER DOCUMENTS
+
 ---
 
 *TODO: Answer the questions below to help you define your system
@@ -49,11 +53,11 @@ architecture. Some example text is provided.*
 ::The components of this system are listed below by type:
 
 - ::Presentation/UI Components
-  - ::[C-00: COMPONENTNAME](Design-Components#c-00)
+  - ::[C-00: COMPONENT-NAME](Design-Components#c-00)
 - ::Application Logic Components
-  - ::[C-10: COMPONENTNAME](Design-Components#c-10)
+  - ::[C-10: COMPONENT-NAME](Design-Components#c-10)
 - ::Data Storage Components
-  - ::[C-20: COMPONENTNAME](Design-Components#c-20)
+  - ::[C-20: COMPONENT-NAME](Design-Components#c-20)
 
 ### Deployment
 
@@ -68,24 +72,24 @@ defined below:
 - ::All-in-one server
   - ::Tomcat process
     - ::[C-00: Tomcat web server](Design-Components#c-00)
-    - ::[C-10: PROJECTNAME
+    - ::[C-10: PROJECT-NAME
       application](Design-Components#c-10)
   - ::Database process
-    - ::[C-20: COMPONENTNAME](Design-Components#c-30)
+    - ::[C-20: COMPONENT-NAME](Design-Components#c-30)
 
 ::The deployment of components to processes and machines is clearly
 defined below:
 
 - ::Load-balanced front-end servers
-  - ::[C-01: COMPONENTNAME](Design-Components#c-00)
+  - ::[C-01: COMPONENT-NAME](Design-Components#c-00)
 - ::Back-end server
   - ::JVM process
-    - ::[C-00: COMPONENTNAME](Design-Components#c-00)
-    - ::[C-10: COMPONENTNAME](Design-Components#c-10)
-    - ::[C-11: PLUG-IN COMPONENTNAME](Design-Components#c-11)
-    - ::[C-12: PLUG-IN COMPONENTNAME](Design-Components#c-12)
+    - ::[C-00: COMPONENT-NAME](Design-Components#c-00)
+    - ::[C-10: COMPONENT-NAME](Design-Components#c-10)
+    - ::[C-11: PLUG-IN COMPONENT-NAME](Design-Components#c-11)
+    - ::[C-12: PLUG-IN COMPONENT-NAME](Design-Components#c-12)
   - Database process
-    - ::[C-20: COMPONENTNAME](Design-Components#c-30)
+    - ::[C-20: COMPONENT-NAME](Design-Components#c-30)
 
 #### What aspects/resources of their environment are shared?
 
@@ -120,7 +124,6 @@ split or load-balanced.
 
 ### Integration
 
-
 #### How will components be integrated? Specifically, how will they communicate?
 
 ::All of our code uses direct procedure calls. The database is
@@ -166,14 +169,17 @@ components communicate during some important usage scenarios:
 *TODO: Evaluate your architecture with respect to each of your goals.*
 
 #### Ease of integration: Have mechanisms been provided for all needed types of integration?
+
 ::Yes. In this system, all of the new components are designed to
 work together. And, the reused components are integrated via fairly
 simple interfaces.
 
 #### Extensibility: What types of components can be added later and how?
+
 ::See above.
 
 #### Capacity matching: How has this architecture matched component resource needs to machines?
+
 ::The database can be on a machine with RAID disks and a hot-swappable
 power supply, while the web front-end components can be on cheaper
 machines that could fail individually without causing