Streamlining

- mostly stylistic streamlining
- removed 'additional context' sections. They seem to be rarely used and might cause confusion. If more details are needed, users can add them to the 'details' section

.github/ISSUE_TEMPLATE/---new-benchmark.md

@@ -1,5 +1,5 @@
 ---
-name: "\U0001F5A5 New Benchmark"
+name: "\U0001F5A5 New benchmark"
 about: Benchmark a part of this library and share your results
 title: "[Benchmark]"
 labels: ''
@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-# Benchmarking `transformers`
+# 🖥 Benchmarking `transformers`
 
 ## Benchmark
 

.github/ISSUE_TEMPLATE/--new-model-addition.md

@@ -18,7 +18,3 @@ assignees: ''
 * [ ] the model implementation is available: (give details)
 * [ ] the model weights are available: (give details)
 * [ ] who are the authors: (mention them, if possible by @gh-username)
-
-## Additional context
-
-<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/bug-report.md

@@ -7,9 +7,9 @@ assignees: ''
 
 ---
 
-## 🐛 Bug
+# 🐛 Bug
 
-<!-- Important information -->
+## Information
 
 Model I am using (Bert, XLNet ...):
 
@@ -48,7 +48,3 @@ Steps to reproduce the behavior:
 * Using GPU ?
 * Distributed or parallel setup ?
 * Any other relevant information:
-
-## Additional context
-
-<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,5 +1,5 @@
 ---
-name: "\U0001F680 Feature Request"
+name: "\U0001F680 Feature request"
 about: Submit a proposal/request for a new transformers feature
 title: ''
 labels: ''
@@ -7,18 +7,19 @@ assignees: ''
 
 ---
 
-## 🚀 Feature
+# 🚀 Feature request
 
-<!-- A clear and concise description of the feature proposal. Please provide a link to the paper and code in case they exist. -->
+<!-- A clear and concise description of the feature proposal.
+     Please provide a link to the paper and code in case they exist. -->
 
 ## Motivation
 
-<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too. -->
+<!-- Please outline the motivation for the proposal. Is your feature request
+     related to a problem? e.g., I'm always frustrated when [...]. If this is related
+     to another GitHub issue, please link here too. -->
 
 ## Your contribution
 
-<!-- Is there any way that you could help, e.g. by submitting a PR? Make sure to read the CONTRIBUTING.MD readme: https://github.com/huggingface/transformers/blob/master/CONTRIBUTING.md -->
-
-## Additional context
-
-<!-- Add any other context or screenshots about the feature request here. If you have code to share, use code tags rather than screenshots: https://help.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting -->
+<!-- Is there any way that you could help, e.g. by submitting a PR?
+     Make sure to read the CONTRIBUTING.MD readme:
+     https://github.com/huggingface/transformers/blob/master/CONTRIBUTING.md -->

.github/ISSUE_TEMPLATE/migration.md

@@ -7,7 +7,9 @@ assignees: ''
 
 ---
 
-## 📚 Migration
+# 📚 Migration
+
+## Information
 
 <!-- Important information -->
 
@@ -23,7 +25,7 @@ The tasks I am working on is:
 * [ ] an official GLUE/SQUaD task: (give the name)
 * [ ] my own task or dataset: (give details below)
 
-Details of the issue:
+## Details
 
 <!-- A clear and concise description of the migration issue.
     If you have code snippets, please provide it here as well.
@@ -48,7 +50,3 @@ Details of the issue:
  ([pytorch-transformers](https://github.com/huggingface/transformers#migrating-from-pytorch-transformers-to-transformers);
   [pytorch-pretrained-bert](https://github.com/huggingface/transformers#migrating-from-pytorch-pretrained-bert-to-transformers))
 - [ ] I checked if a related official extension example runs on my machine.
-
-## Additional context
-
-<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/question-help.md

@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-## ❓ Questions & Help
+# ❓ Questions & Help
 
 <!-- The GitHub issue tracker is primarly intended for bugs, feature requests,
      new models and benchmarks, and migration questions. For all other questions,
@@ -21,8 +21,9 @@ assignees: ''
      that you posted.
      -->
 
+## Details
 <!-- Description of your issue -->
 
 <!-- You should first ask your question on SO, and only if
-     you didn't get an answer ask it here on GitHub.
-A link to original question on Stack Overflow: 
+     you didn't get an answer ask it here on GitHub. -->
+**A link to original question on Stack Overflow**: