diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 19a8a6568..b0b017c8c 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -6,54 +6,18 @@ about: Report a bug in MatterControl
 
 Bug Report
 ============
-
-<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 -->
-
-<!--
-Before filing, check if the issue already exists (either open or closed) by using the search bar on the issues page. If it does, comment on the original issue. Even if it's closed, we can reopen it based on your comment.
-
-Please COMPLETELY fill in the information below. The template is designed to avoid unnecessary delays to confirm and fix reported issues. Issues with missing information generally end up with a `need-info` label and take significantly more time to fix. Please help us help you!
--->
-
-**MatterControl Build Number**
-<!-- Example: 2.0.0-9999. To find this, go to the MatterControl menu in the top left and click "About MatterControl" -->
-
-**Operating System Version**
-<!-- Examples: Windows 10, macOS 10.14, Ubuntu 18.10, Android -->
-
-**Printer Make/Model**
-<!-- Example: Pulse C-232 -->
-
 **Steps to Reproduce**
-<!--
-Describe how to make the bug happen. Fixing a bug depends on the developers being able to get it to happen themselves, on their computer. Start at the very beginning (opening MatterControl) and explain exactly what you did leading to the issue, step by step. Follow the steps yourself and make sure that you can get the issue to happen again. If it is difficult to explain, then you are encouraged to include screenshots or a screen recording. You can do this using a tool like ScreenToGif (https://www.screentogif.com/). If the problem is related to a particular file you are working with, include it in the next section.
--->
-
 1. 
 2. 
 3. 
 
 **Expected Behavior**
-<!-- What should happen after the above steps have been followed -->
 
 **Actual Behavior**
-<!-- What really happens after the above steps have been followed -->
 
-**Attachments**
-<!--
-Include any of the files below which may be related to your issue. These are necessary in order for the developers to recreate and diagnose your problem. If in doubt, upload as many of these as possible. It is better for us to have too much information than too little. You may have to pack them in a .zip in order to upload them to GitHub.
--->
+**MatterControl Build Number**
+(To find this, go to the MatterControl menu in the top left and click "About MatterControl")
 
-* Model you are trying to print
-<!-- This may be an STL file or a design you created in MatterControl. If you made it in MatterControl, export it as a ZIP file. -->
-* Printer Settings File
-<!-- A lot of the behavior in MatterControl is related to your printer configuration. To export your settings, go to the three dots menu in the top right of MatterControl (next to the hot end controls) and choose "Export All Settings". -->
-* Print Log
-<!--
-This log details all the communications between MatterControl and your printer. It is helpful for diagnosing hardware/firmware errors and communications issues.
+**Operating System Version**
 
-    1. Run a print as you normally would.
-    2. Once the problem occurs, open the G-Code terminal by going to Options > Show Terminal.
-    3. Click the 'Export' button at the bottom of the screen.
-    4. Save the print log.
--->
+**Printer Make/Model**
diff --git a/.github/ISSUE_TEMPLATE/crash-report.md b/.github/ISSUE_TEMPLATE/crash-report.md
deleted file mode 100644
index ce4d80798..000000000
--- a/.github/ISSUE_TEMPLATE/crash-report.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-name: Crash report
-about: Report a crash in MatterControl
-
----
-
-Crash Report
-============
-
-<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 -->
-
-<!--
-Before filing, check if the issue already exists (either open or closed) by using the search bar on the issues page. If it does, comment on the original issue. Even if it's closed, we can reopen it based on your comment.
-
-Please COMPLETELY fill in the information below. You are must also upload a crash log.
--->
-
-**MatterControl Build Number**
-<!-- Example: 2.0.0-9999. To find this, go to the MatterControl menu in the top left and click "About MatterControl" -->
-
-**Operating System Version**
-<!-- Examples: Windows 10, macOS 10.14, Ubuntu 18.10, Android -->
-
-**Printer Make/Model**
-<!-- Example: Pulse C-232 -->
-
-**Steps to Reproduce**
-<!-- Describe how to make the crash happen. Start at the very beginning (opening MatterControl) and explain everything you did to make the crash occur, step by step. Follow the steps yourself and make sure that you can get the crash to happen again. If it is difficult to explain, then you are encouraged to include screenshots or a screen recording. If the crash is related to a particular file you are working with, include it in the next section. -->
-
-1. 
-2. 
-3. 
-
-**Other Attachments**
-<!-- Include any other files related to the crash here. You may have to pack them in a .zip in order to upload them to GitHub. For instance, this might include the STL file you were trying to print. If the crash is related to slicing, then also include your exported printer settings. To export your settings, go to the three dots menu in the top right of MatterControl (next to the hot end controls) and choose "Export All Settings". -->
-
-**Crash Log**
-<!--
-A crash log is required for us to determine what went wrong. If you do not include a crash log, your report will be closed. Follow the instructions for your platform to collect the log.
-
-WINDOWS
-
-    1. Right click on ‘My Computer’ and select ‘Manage.’
-    2. In the menu on the left, navigate to ‘System Tools’ > ‘Event Viewer’ > ‘Windows Logs’.
-    3. Click on ‘Application’ to show logs in the middle window pane, then click ‘Filter Current Log’ in the right window pane, then check ‘Error’ and hit ‘OK’.
-    4. In the right window pane, choose ‘Save Filtered Log File As’. Give the file (should be in .evtx format) a descriptive name.
-    5. Attach the .evtx file to this report.
-
-MAC
-
-    1. Close any open instances of MatterControl.
-    2. Go to the 'Applications' folder.
-    3. Locate the MatterControl.app file.
-    4. Right-click and select "Show Package Contents".
-    5. Navigate to 'Contents' > 'MacOS'.
-    6. Double click the 'MatterControlMac' file (this will open a terminal window and start the application).
-    7. Copy the output. If MatterControl crashes upon startup copy the message that appears in the terminal window immediately. If the crash is triggered by a specific event, recreate the event and then copy the message that appears.
-    8. Paste the output below, between the triple tick marks.
-
-LINUX
-
-    Run `mattercontrol` from a terminal. Copy all output and paste it below, between the triple tick marks.
-
-ANDROID (MatterControl T10, T7X)
-
-    Crash logs are difficult to collect from Android. If possible, try to make the same crash happen on a PC and collect the log from there.
--->
-
-```
-Paste crash log here
-```
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index 2cb923a9c..dc836025d 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -7,14 +7,8 @@ about: Suggest an idea for MatterControl
 Feature Request
 ===============
 
-<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 -->
-
-<!--
-Feature requests are welcome, but take a moment to find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
--->
-
 **Problem**
-<!-- Describe the problem which your feature would solve. In other words, explain the situation in which it would be necessary or beneficial. -->
+Describe the problem you feel needs to be solved.
 
 **Solution**
-<!-- Describe your feature and why it is the best solution for the problem. Explain how it would benefit people who use MatterControl. -->
+Explain how this feature will solve the problem.