Change styling of notes for avoiding PRs and error messages

JoshDevHub · JoshDevHub · commit 6f9080c3db39 · 2024-05-04T13:06:04.000-07:00
diff --git a/README.md b/README.md
@@ -26,9 +26,12 @@ If you have a suggestion to improve an exercise, an idea for a new exercise, or
 1. Once you successfully finish an exercise, check the `solutions` directory within each exercise to compare it with yours.
    - You should not be checking the solution for an exercise until you finish it!
    - If your solution differs wildly from TOP's solution (and still passes the exercise's requirements), that is completely fine. Feel free to ask about it in our Discord if there are parts you do not understand.
-1. Do not submit your solutions to this repo, as any PRs that do so will be closed without merging.
 
-**Note**: Due to the way Jest handles failed tests, it may return an exit code of 1 if any tests fail. NPM will interpret this as an error and you may see some `npm ERR!` messages after Jest runs. You can ignore these, or run your test with `npm test exerciseName.spec.js --silent` to supress the errors.
+> [!IMPORTANT]
+> Do not submit your solutions to this repo, as any PRs that do so will be closed without merging.
+
+> [!NOTE]
+> Due to the way Jest handles failed tests, it may return an exit code of 1 if any tests fail. NPM will interpret this as an error and you may see some `npm ERR!` messages after Jest runs. You can ignore these, or run your test with `npm test exerciseName.spec.js --silent` to supress the errors.
 
 The first exercise, `helloWorld`, will walk you through the process in-depth.
 
