Clean up text with issue template forms

.github/ISSUE_TEMPLATE/bug-report--vs-code-runtime-extension.yml

@@ -1,19 +1,20 @@
-name: "Bug Report"
-description: 'Create a report about something that is a potential bug'
-title: 'Describe the issue you're facing'
+name: 🐞 Bug Report
+description: Create a report a potential bug
+title: Describe the issue you're facing
 labels: ["untriaged"]
 body:
 - type: markdown
   attributes:
     value: |
-         Thanks for taking the time to fill out this bug report!
+        Thanks for taking the time to fill out this bug report!
+        📖 Have you checked existing issues to see whether someone else has already reported your issue?
         ❗ Privacy Alert! The contents in our log files may contain personal data. Prior to posting to GitHub, please remove any personal data which should not be publicly viewable. https://privacy.microsoft.com/en-US/privacystatement"
-        📖 Have checked existing issues to see whether someone else has already reported your issue?
 - type: textarea
   attributes:
-    label: Describe the bug. **Please attach log file(s) here if you have any.**
-    description: Please share some details about the issue you are facing with the .NET Install Tool.
-Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+    label: Describe the bug. *Please attach log file(s) here if you have any.*
+    description: |
+      Please share some details about the issue you are facing with the .NET Install Tool.
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
   validations:
     required: true
 - type: textarea
@@ -21,15 +22,15 @@ Tip: You can attach images or log files by clicking this area to highlight it an
     label: Please attach log file(s) here if you have any.
     description: |
         Our log files are located alongside VS Code logs. If you want to find them manually, navigate here:
-            Linux: ~/.config/Code/logs
-            Mac: ~/Library/Application Support/Code/logs/
-            Windows: c:\Users\USER\AppData\Roaming\Code\logs\
+        Linux: ~/.config/Code/logs
+        Mac: ~/Library/Application Support/Code/logs/
+        Windows: c:\Users\USER\AppData\Roaming\Code\logs\
 
         Then find the folder created at the time you experienced the bug in the logs folder.
         From there, go to window1 -> exthost -> ms-dotnettools.vscode-dotnet-runtime. The log file should be located in this folder.
 
         Note: The window folder may change depending on how many VS Code windows you have open; if our extension is running in the 2nd window, it'd be in a folder called window2.
-    placeholder: "The log file location should be copied to your clipboard if you came from VS Code."
+    placeholder: The log file location should be copied to your clipboard if you came from VS Code.
   validations:
     required: true
 - type: textarea
@@ -51,7 +52,7 @@ Tip: You can attach images or log files by clicking this area to highlight it an
 - type: input
   attributes:
     label: .NET Install Tool Version
-    placeholder: "e.g. v2.0.0. You can find this by hovering over the extension in VS Code, the version number is to the right of the extension name."
+    placeholder: e.g. v2.0.0. You can find this by hovering over the extension in VS Code, the version number is to the right of the extension name.
   validations:
     required: true
 - type: dropdown
@@ -70,6 +71,6 @@ Tip: You can attach images or log files by clicking this area to highlight it an
 - type: input
   attributes:
     label: VS Code Version
-    placeholder: "e.g. 1.84.2. You can find this in VS Code by going to Help -> About -> and finding the Version."
+    placeholder: e.g. 1.84.2. You can find this in VS Code by going to Help -> About -> and finding the Version.
   validations:
     required: false

.github/ISSUE_TEMPLATE/feature-request--vs-code-runtime-extension.yml

@@ -1,6 +1,6 @@
 name: "Feature Request"
 description: 'Request a new feature for this project'
-title: 'Reporting a Vulnerability'
+title: ''
 labels: ["feature-request"]
 body:
 - type: textarea
@@ -11,7 +11,7 @@ body:
     required: true
 - type: textarea
   attributes:
-    label: A clear and **concise** description of what you want to happen. Include any alternative solutions you've considered.
+    label: A clear and concise description of what you want to happen. Include any alternative solutions you've considered.
     placeholder: Example -- I would like to have [...] to change from [...] to [...]. The benefit of this is [...].
   validations:
     required: true

.github/ISSUE_TEMPLATE/security-fix.yml

@@ -1,17 +1,17 @@
-name: "Security fix"
-description: 'Report a security vulnerability'
-title: 'Reporting a Vulnerability'
+name: Security fix
+description: Report a security vulnerability
+title: ''
 labels: ["closeable"]
 body:
 - type: markdown
   attributes:
-    value: "Security issues and bugs should be reported privately to the Microsoft Security Response Center (MSRC), either by emailing secure@microsoft.com or via the portal at https://msrc.microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the MSRC Report an Issue FAQ."
-- type: markdown
-  attributes:
-    value: "⚠️ Please do not open issues for anything you think might have a security implication."
+    value: |
+      Security issues and bugs should be reported privately to the Microsoft Security Response Center (MSRC), either by emailing secure@microsoft.com or via the portal at https://msrc.microsoft.com.
+      You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
+      Further information, including the MSRC PGP key, can be found in the MSRC Report an Issue FAQ."
 - type: textarea
   attributes:
-    label: ‎‎‎‎‎‎‎ㅤ
+    label: ⚠️ Please do not open issues for anything you think might have a security implication.
     placeholder: Close this window and instead email secure@microsoft.com or disclose the issue via the portal at https://msrc.microsoft.com.
     render: cs
   validations: