Update test.md

NoerGitKat · web-flow · commit 7ce55f80de35 · 2020-03-24T13:15:07.000+01:00
diff --git a/test.md b/test.md
@@ -37,14 +37,14 @@ Advice on how to optimally prepare:
 
 ## During the test
 Advise on how to make a test:
-- Look for low hanging fruit. Which of the assignments is easiest for you to do? Tackle that one first. 
-- When writing your code, write small chunks at a time, testing each time before continuing. Use temporary console.log statements to show intermediate results (remove when no longer needed). Don't continue until the code written sofar is working correctly. If you write a whole bunch of code without intermediate testing it becomes difficult to pinpoint where issues occur.
-- If you get stuck in an assignment, move on to the next one. You can always come back later if time permits.
-- When writing code for the browser, always open the Chrome Developer Tools. Watch out for error messages in the browser console. Inspect the network tab to examine the data returned from a remote API.
-- Don't over-deliver. If styling is not required by the assignment, skip it. If time permits, you can do it later. The same goes for handling fetch errors. Focus on delivering a minimum working version that meets the requirement. Ticking off a working version again reduces your stress level. Come back later, if time permits, to embellish your solutions.
-- Don't use Google as a replacement for common sense.
-- After finishing an assignment, read the question again to make sure you actually gave an answer to the question. 
-- Before handing in the test, read it all over again to pick out the small mistakes.
+- **Look for low hanging fruit**. Which of the assignments is easiest for you to do? Tackle that one first. 
+- **When writing your code, write small chunks at a time, testing each time before continuing**. Use temporary console.log statements to show intermediate results (remove when no longer needed). Don't continue until the code written sofar is working correctly. If you write a whole bunch of code without intermediate testing it becomes difficult to pinpoint where issues occur.
+- **If you get stuck in an assignment, move on** to the next one. You can always come back later if time permits.
+- When writing code for the browser, **always open the Chrome Developer Tools**. Watch out for error messages in the browser console. Inspect the network tab to examine the data returned from a remote API.
+- **Don't over-deliver**. If styling is not required by the assignment, skip it. If time permits, you can do it later. The same goes for handling fetch errors. Focus on delivering a minimum working version that meets the requirement. Ticking off a working version again reduces your stress level. Come back later, if time permits, to embellish your solutions.
+- **Don't use Google as a replacement for common sense.**
+- After finishing an assignment, read the question again to **make sure you actually gave an answer to the question.** 
+- Before handing in the test, read it all over again to **pick out the small mistakes.**
 
 ## Sample questions
 
@@ -53,6 +53,5 @@ Advise on how to make a test:
 2. Make an API call using the Fetch API or the regular XMLHttpRequest (whichever one you're more comfortable with). Use the following API: https://reqres.in/api/users
 Parse the response and then display the "first_name" and "last_name" of the first three users within the DOM (inside an unordered list)
 
-
 If there’s anything unclear please let us know. Also, if any of you need additional support, now is the moment to let us know as we could pair you up with someone to answer any questions you may have.
 
