Further cleanup with headings

Author: thekaveman

.github/ISSUE_TEMPLATE/feature-request---proposal.md

@@ -7,27 +7,34 @@ assignees: ''
 
 ---
 
-**Is your feature request related to a problem? Please describe.**
+### Is your feature request related to a problem? Please describe.
+
 A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
 
-**Describe the solution you'd like**
+### Describe the solution you'd like
+
 A clear and concise description of what you want to happen.
 
-**Is this a breaking change**
+### Is this a breaking change
+
 A breaking change would require consumers or implementors of the API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint). 
 
 * [ ] Yes, breaking
 * [ ] No, not breaking
 * [ ] I'm not sure
 
-**`Provider` or `agency`**
+### `Provider` or `agency`
+
 For which API is this feature being requested:
+
 * [ ] `provider`
 * [ ] `agency`
 * [ ] both
 
-**Describe alternatives you've considered**
+### Describe alternatives you've considered
+
 A clear and concise description of any alternative solutions or features you've considered.
 
-**Additional context**
+### Additional context
+
 Add any other context or screenshots about the feature request here.