Fix spacing in issue templates (#56189)

Author: jakebailey

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -13,8 +13,7 @@ body:
 
         List them here so people in the future can find this one more easily.
       placeholder: |
-        List of keywords you searched for before creating this issue.
-        Write them down here so that others can find this bug more easily and help provide feedback.
+        List of keywords you searched for before creating this issue. Write them down here so that others can find this bug more easily and help provide feedback.
 
         e.g. "function inference any", "jsx attribute spread", "move to file duplicate imports", "discriminated union inference", "ts2822"
     validations:
@@ -52,7 +51,6 @@ body:
 
         This should have the same code as the code snippet below, and use whichever settings are relevant to your report.
 
-
         As a last resort, you can link to a repo, but these will be slower for us to investigate.
       placeholder: 'Playground link with relevant code: https://www.typescriptlang.org/play?#code/PTAEFkE9QYwewCYFNQHM5IM6gBZIE5JA'
     validations:
@@ -63,6 +61,7 @@ body:
       label: 💻 Code
       description: |
         Please post the relevant code sample here as well.
+
         This code and the Playground code should be the same, do not use separate examples.
 
         We can quickly address your report if:
@@ -72,6 +71,7 @@ body:
           - The incorrectness of the behavior is readily apparent from reading the sample.
 
         Reports are slower to investigate if:
+
           - We have to pare too much extraneous code.
           - We have to clone a large repo and validate that the problem isn't elsewhere.
           - The sample is confusing or doesn't clearly demonstrate what's wrong.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -15,8 +15,7 @@ body:
 
         The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests
       placeholder: |
-        List of keywords you searched for before creating this issue.
-        Write them down here so that others can find this suggestion more easily and help provide feedback.
+        List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
 
         e.g. "isArray readonly", "regex string types", "json const assertion import"
     validations:
@@ -26,9 +25,7 @@ body:
     attributes:
       label: '✅ Viability Checklist'
       description: |
-        Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
-        We always recommend reviewing the TypeScript design goals before investing time writing
-        a proposal for ideas outside the scope of the project.
+        Suggestions that don't meet all these criteria are very, very unlikely to be accepted. We always recommend reviewing the TypeScript design goals before investing time writing a proposal for ideas outside the scope of the project.
 
         My suggestion meets the following guidelines.
       options:
@@ -54,8 +51,7 @@ body:
     attributes:
       label: '📃 Motivating Example'
       description: |
-        If you were announcing this feature in a blog post, what's a short
-        explanation that shows a developer why this feature improves the language?
+        If you were announcing this feature in a blog post, what's a short explanation that shows a developer why this feature improves the language?
     validations:
       required: true
   - type: textarea

.github/ISSUE_TEMPLATE/lib_change.yml

@@ -12,18 +12,13 @@ body:
         * Array methods - see https://github.com/microsoft/TypeScript/issues/36554
         * `parseInt`, `parseFloat`, `isFinite`, `isNaN`, etc. - see https://github.com/microsoft/TypeScript/issues/4002
 
-
-        The DOM lib is maintained elsewhere and you can skip a step by filing issues/PRs for the DOM at that repo.
-        See https://github.com/microsoft/TypeScript-DOM-lib-generator
+        The DOM lib is maintained elsewhere and you can skip a step by filing issues/PRs for the DOM at that repo. See https://github.com/microsoft/TypeScript-DOM-lib-generator
   - type: markdown
     attributes:
       value: |
-        If you're missing common new methods like `Array.includes`, you may have a misconfigured project.
-        Try setting `lib: "es2020"` and checking whether the type you want is present.
-        You can diagnose further by running `tsc` with `--listFilesOnly` or `--showConfig`.
+        If you're missing common new methods like `Array.includes`, you may have a misconfigured project. Try setting `lib: "es2020"` and checking whether the type you want is present. You can diagnose further by running `tsc` with `--listFilesOnly` or `--showConfig`.
 
-        Conversely, if you are seeing built-in methods you expect to *not* see, check your 'lib' setting or review your dependencies for lib/reference directives that might be polluting
-        your global scope. This is common when using the 'node' type library. See https://github.com/microsoft/TypeScript/issues/40184
+        Conversely, if you are seeing built-in methods you expect to *not* see, check your 'lib' setting or review your dependencies for lib/reference directives that might be polluting your global scope. This is common when using the 'node' type library. See https://github.com/microsoft/TypeScript/issues/40184
   - type: input
     id: compilation_target
     attributes:
@@ -58,5 +53,4 @@ body:
     attributes:
       label: 'Documentation Link'
       description: |
-        Link to relevant documentation (e.g. MDN, W3C, ECMAScript Spec) to consult for this property.
-        Note that lib.dom.d.ts intentionally does not include browser-specific extensions or early experimental features.
+        Link to relevant documentation (e.g. MDN, W3C, ECMAScript Spec) to consult for this property. Note that lib.dom.d.ts intentionally does not include browser-specific extensions or early experimental features.

.github/ISSUE_TEMPLATE/module_resolution.yml

@@ -27,8 +27,7 @@ body:
         4. The configuration of the target module
         5. A difference in runtime behavior
 
-        You will also be required to post a cloneable repository.
-        This repo must involve running `tsc`, not a third-party tool (e.g. vue-tsc, ngc, expo, ...)
+        You will also be required to post a cloneable repository. This repo must involve running `tsc`, not a third-party tool (e.g. vue-tsc, ngc, expo, ...)
 
   - type: input
     id: repo-url