Fix markdown lint errors
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
<!-- markdownlint-disable-next-line MD041 -->
|
||||
<!-- markdownlint-disable-next-line first-line-h1 -->
|
||||
##### Project
|
||||
|
||||
::PROJECT-NAME
|
||||
@@ -15,11 +15,11 @@
|
||||
|
||||
---
|
||||
|
||||
*TODO: Briefly describe each component in the system. Focus on
|
||||
_TODO: Briefly describe each component in the system. Focus on
|
||||
architectural issues such as communication mechanisms, environmental
|
||||
concerns that affect deployment options, and concurrency. Note key
|
||||
aspects of each interface, but avoid duplicating details of interfaces
|
||||
that are specified in the UML class diagrams or other documents.*
|
||||
that are specified in the UML class diagrams or other documents._
|
||||
|
||||
Each interface can be an API (application program interface), standard
|
||||
protocol (e.g., HTTP), config files, input data file format, or
|
||||
@@ -28,8 +28,8 @@ may have multiple interfaces: e.g., a server may handle requests in a
|
||||
standard protocol, but also have a config file, command-line options, an
|
||||
administrative control panel GUI, and a performance monitoring API.
|
||||
|
||||
*TIP: Use an HTML anchor for each component so that a direct link can be
|
||||
made from other documents, issues, and email messages.*
|
||||
_TIP: Use an HTML anchor for each component so that a direct link can be
|
||||
made from other documents, issues, and email messages._
|
||||
|
||||
---
|
||||
|
||||
|
Reference in New Issue
Block a user