Reorder synchronous test docs

docs/Troubleshooting.md

@@ -194,9 +194,7 @@ Make sure you are not using the `babel-plugin-istanbul` plugin. Jest wraps Istan
 
 ## Defining Tests
 
-Tests much be defined synchronously for Jest to be able to collect your tests.
-
-This means when you are using `test.each` you cannot set the table asynchronously within a `beforeEach` / `beforeAll`.
+Tests must be defined synchronously for Jest to be able to collect your tests.
 
 As an example to show why this is the case, imagine we wrote a test like so:
 
@@ -209,6 +207,8 @@ setTimeout(() => {
 
 When Jest runs your test to collect the `test`s it will not find any because we have set the definition to happen asynchronously on the next tick of the event loop.
 
+_Note:_ This means when you are using `test.each` you cannot set the table asynchronously within a `beforeEach` / `beforeAll`.
+
 ## Still unresolved?
 
 See [Help](/help.html).

website/versioned_docs/version-23.6/Troubleshooting.md

@@ -195,9 +195,7 @@ Make sure you are not using the `babel-plugin-istanbul` plugin. Jest wraps Istan
 
 ## Defining Tests
 
-Tests much be defined synchronously for Jest to be able to collect your tests.
-
-This means when you are using `test.each` you cannot set the table asynchronously within a `beforeEach` / `beforeAll`.
+Tests must be defined synchronously for Jest to be able to collect your tests.
 
 As an example to show why this is the case, imagine we wrote a test like so:
 
@@ -210,6 +208,10 @@ setTimeout(() => {
 
 When Jest runs your test to collect the `test`s it will not find any because we have set the definition to happen asynchronously on the next tick of the event loop.
 
+_Note:_ This means when you are using `test.each` you cannot set the table asynchronously within a `beforeEach` / `beforeAll`.
+
+When Jest runs your test to collect the `test`s it will not find any because we have set the definition to happen asynchronously on the next tick of the event loop.
+
 ## Still unresolved?
 
 See [Help](/help.html).