Fix code review suggestion

Author: Kyle-Ye

.github/ISSUE_TEMPLATE/BUG_REPORT.yml

@@ -2,23 +2,19 @@ name: Bug Report
 description: Something isn't working as expected
 labels: [bug]
 body:
-- type: markdown
-  attributes:
-    value: "## Thank you for contributing to Swift-DocC!"
 - type: markdown
   attributes:
     value: |
-      Before you submit your issue, please complete each textarea
-      below with the relevant details for your bug, and complete
-      the steps in the checklist
+      Thank you for contributing to Swift-DocC! 
+      
+      Before you submit your issue, please complete each text area below with the relevant details for your bug, and complete the steps in the checklist
 - type: textarea
   attributes:
     label: Description
     description: |
       A short description of the incorrect behavior. 
-      If you think this issue has been recently introduced and did not occur in an 
-      earlier version, please note that. If possible, include the last version that 
-      the behavior was correct in addition to your current version.
+
+      If you think this issue has been recently introduced and did not occur in an earlier version, please note that. If possible, include the last version that the behavior was correct in addition to your current version.
   validations:
     required: true
 - type: checkboxes
@@ -46,12 +42,15 @@ body:
     label: Steps To Reproduce
     description: |
       Explanation of how to reproduce the incorrect behavior. 
-      This could include a reduced version of your documentation bundle,
-      or a link to the documentation (or code) that is exhibiting the issue.
+      
+      This could include a reduced version of your documentation bundle, or a link to the documentation (or code) that is exhibiting the issue.
     placeholder: |
       1. In this environment...
+
       2. With this config...
+      
       3. Run '...'
+      
       4. See error...
   validations:
     required: false
@@ -61,10 +60,19 @@ body:
     description: |
       examples:
         - **Swift-DocC version:** `5.6.0` for example, or a commit hash.
+    value: |
+        - Swift-DocC version: 
+    render: markdown
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Swift Compiler Version Information
+    description: |
+      examples:
         - **Swift Compiler version:** Output from `swiftc --version`.
     value: |
-        - Swift-DocC version:
-        - Swift Compiler version:
+        - Swift Compiler version: 
     render: markdown
   validations:
     required: false

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.yml

@@ -2,17 +2,12 @@ name: Feature Request
 description: A suggestion for a new feature
 labels: [enhancement]
 body:
-- type: markdown
-  attributes:
-    value: "## Thank you for contributing to Swift-DocC!"
 - type: markdown
   attributes:
     value: |
-      Before you submit your issue, please replace each textarea
-      below with information about your proposed feature.
-- type: markdown
-  attributes:
-    value: "## Feature Request"
+      Thank you for contributing to Swift-DocC!
+      
+      Before you submit your issue, please replace each text area below with information about your proposed feature.
 - type: input
   attributes:
     label: Feature Name
@@ -23,9 +18,8 @@ body:
     label: Description
     description: |
       A description of your proposed feature.
-      Sample documentation catalogs that show what's missing, 
-      or what new capabilities will be possible, are very helpful! 
-      Provide links to existing issues or external references/discussions, if appropriate.
+
+      Sample documentation catalogs that show what's missing, or what new capabilities will be possible, are very helpful! Provide links to existing issues or external references/discussions, if appropriate.
   validations:
     required: true
 - type: textarea
@@ -39,9 +33,8 @@ body:
     label: Importance
     description: |
       A description of the importance of this change.
-      Does this feature unlock entirely new use-cases?
-      Or is it possible to achieve the same functionality with existing functionality
-      and this change would improve the user experience?
+
+      Does this feature unlock entirely new use-cases? Or is it possible to achieve the same functionality with existing functionality and this change would improve the user experience?
   validations:
     required: false
 - type: textarea