diff --git a/issue-templates/dev-test-template.md b/issue-templates/dev-test-template.md
index cdf8f38..58e4461 100644
--- a/issue-templates/dev-test-template.md
+++ b/issue-templates/dev-test-template.md
@@ -15,102 +15,6 @@ Notes and Instructions for Developers:
 
 Assigning @ariel-phet for prioritization.
 
-<!---
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-////////// Section 0: FAQs for QA Members [DO NOT OMIT, DO NOT EDIT]
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
--->
-
-<details>
-<summary><b>FAQs for QA Members</b></summary>
-
-<br>
-  
-  <!--- Subsection 0.1: There are multiple tests in this issue... What should I test first? [DO NOT OMIT, DO NOT EDIT] -->
-
-  <details>
-  <summary><i>There are multiple tests in this issue... Which test should I do first?</i></summary> 
-  
-  Test in order! Test the first thing first, the second thing second, and so on.
-
-  </details>
-
-  <br>
-
-  <!--- Subsection 0.2: How should I format my issue? [DO NOT OMIT, DO NOT EDIT] -->
-
-  <details>
-  <summary><i>How should I format my issue?</i></summary>
-  
-  Here's a template for making issues:
-
-      <b>Test Device</b>
-
-      blah
-
-      <b>Operating System</b>
-
-      blah
-
-      <b>Browser</b>
-
-      blah
-
-      <b>Problem Description</b>
-
-      blah
-
-      <b>Steps to Reproduce</b>
-
-      blah
-
-      <b>Visuals</b>
-
-      blah
-
-      <details>
-      <summary><b>Troubleshooting Information</b></summary>
-
-      blah
-
-      </details>
-
-  </details>
-
-  <br>
-
-  <!--- Subsection 0.3: Who should I assign? [DO NOT OMIT, DO NOT EDIT] -->
-
-  <details>
-  <summary><i>Who should I assign?</i></summary>
-  
-  We typically assign the developer who opened the issue in the QA repository.
-
-  </details>
-  
-  <br>
-
-  <!--- Subsection 0.4: My question isn't in here... What should I do? [DO NOT OMIT, DO NOT EDIT] -->
-
-  <details>
-  <summary><i>My question isn't in here... What should I do?</i></summary>
-  
-  You should:
-
-  1. Consult the [QA Book](link).
-  2. Google it.
-  3. Ask Katie.
-  4. Ask a developer.
-  5. Google it again.
-  6. Cry.
-
-  </details>
-
-<br>
-
-<hr>
-
-</details>
 
 <!---
 ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
@@ -264,3 +168,100 @@ This sim supports keyboard navigation. Please make sure it works as intended on
 <hr>
 
 </details>
+
+<!---
+////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
+////////// Section 0: FAQs for QA Members [DO NOT OMIT, DO NOT EDIT]
+////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
+-->
+
+<details>
+<summary><b>FAQs for QA Members</b></summary>
+
+<br>
+  
+  <!--- Subsection 0.1: There are multiple tests in this issue... What should I test first? [DO NOT OMIT, DO NOT EDIT] -->
+
+  <details>
+  <summary><i>There are multiple tests in this issue... Which test should I do first?</i></summary> 
+  
+  Test in order! Test the first thing first, the second thing second, and so on.
+
+  </details>
+
+  <br>
+
+  <!--- Subsection 0.2: How should I format my issue? [DO NOT OMIT, DO NOT EDIT] -->
+
+  <details>
+  <summary><i>How should I format my issue?</i></summary>
+  
+  Here's a template for making issues:
+
+      <b>Test Device</b>
+
+      blah
+
+      <b>Operating System</b>
+
+      blah
+
+      <b>Browser</b>
+
+      blah
+
+      <b>Problem Description</b>
+
+      blah
+
+      <b>Steps to Reproduce</b>
+
+      blah
+
+      <b>Visuals</b>
+
+      blah
+
+      <details>
+      <summary><b>Troubleshooting Information</b></summary>
+
+      blah
+
+      </details>
+
+  </details>
+
+  <br>
+
+  <!--- Subsection 0.3: Who should I assign? [DO NOT OMIT, DO NOT EDIT] -->
+
+  <details>
+  <summary><i>Who should I assign?</i></summary>
+  
+  We typically assign the developer who opened the issue in the QA repository.
+
+  </details>
+  
+  <br>
+
+  <!--- Subsection 0.4: My question isn't in here... What should I do? [DO NOT OMIT, DO NOT EDIT] -->
+
+  <details>
+  <summary><i>My question isn't in here... What should I do?</i></summary>
+  
+  You should:
+
+  1. Consult the [QA Book](link).
+  2. Google it.
+  3. Ask Katie.
+  4. Ask a developer.
+  5. Google it again.
+  6. Cry.
+
+  </details>
+
+<br>
+
+<hr>
+
+</details>