Update templates, add link to github discussions (#11585) [skip ci]

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -9,26 +9,26 @@ assignees: ''
 
 ## Bug Report
 
-<!-- Check this if you would like to implement a PR, we are more than happy to help you go through the process !-->
+<!-- If you would like to implement a PR, we are more than happy to help you go through the process!-->
 - [ ] I would like to work on a fix!
 
 <!--
 @babel/eslint-parser:
   If you are having issues with JSX you might want to check out eslint-plugin-react. If there's an issue with new experimental syntax you might need check if it's supported by @babel/eslint-plugin.
 -->
 
-**Current Behavior**
+**Current behavior**
 A clear and concise description of the behavior.
 
-- [REPL](babeljs.io/repl), [Codesandbox](https://codesandbox.io/s/babel-repl-custom-plugin-7s08o?file=/src/index.js), or GitHub Repo link if applicable:
+- [REPL](babeljs.io/repl), [Codesandbox](https://codesandbox.io/s/babel-repl-custom-plugin-7s08o?file=/src/index.js), or GitHub Repo helps!
 
 **Input Code**
 
 ```js
 var your => (code) => here;
 ```
 
-**Expected behavior/code**
+**Expected behavior**
 A clear and concise description of what you expected to happen (or code).
 
 **Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)**
@@ -54,5 +54,5 @@ A clear and concise description of what you expected to happen (or code).
 **Possible Solution**
 <!--- If you have suggestions on a fix for the bug -->
 
-**Additional context/Screenshots**
-Add any other context about the problem here. If applicable, add screenshots to help explain.
+**Additional context**
+Add any other context about the problem here. Or a screenshot if applicable

.github/ISSUE_TEMPLATE/Npm_error.md

@@ -9,9 +9,7 @@ assignees: ''
 
 <!------------^ Click "Preview" for a nicer view!  -->
 
-First of all, check if the package for which `npm` throws an error is actually published by searching [on the npm website](https://www.npmjs.com/).
-
-If it is, then there is nothing that we can do about it: it was correctly published, but for some reason your package manager client doesn't find it.
+First, check if the package for which `npm` throws an error is published by searching [on the npm website](https://www.npmjs.com/). If it is, then there is nothing that we can do about it: it was correctly published, but for some reason your package manager client doesn't find it.
 
 If you are using a proxy for the npm registry (maybe it's used by your company, or you are using it because your country blocks the main npm registry), then it's likely that it has cached the old version of the package and it isn't loading the new one. If you can, try clearing the proxy's cache. Otherwise, you will have to wait until the cache is automatically updated (it might take a few hours, or even days).
 

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Ask a Question
+    url: https://github.com/babel/babel/discussions
+    about: Ask any questions with the community!
+  - name: Support the Team!
+    url: https://github.com/sponsors/babel
+    about: Support the Babel project financially!