From 30b609461993b9277d6ea378631fed16445fde8a Mon Sep 17 00:00:00 2001
From: ysandler <ysandler@tzed.io>
Date: Tue, 8 Sep 2020 20:25:21 -0500
Subject: [PATCH] =?UTF-8?q?=F0=9F=93=95=20update=20readme=20config=20examp?=
 =?UTF-8?q?les?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 README.md | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 77fbe82..96abe9d 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ All that is required is a Git repo with a brightScreen.json configuration file t
       "documentationUrl": "https://brightScreen.io/courses/Test-Lesson/",
       "lessons": [
         {
-          "name": "Lesson 1",
+          "name": "Lesson One",
           "location": "lessonOne/indexTest.js",
           "description": "Test Description for Lesson 1",
           "executionPrefix": "node",
@@ -39,15 +39,17 @@ A course testing file will look something like this:
       const testedValue = codeFromUser(input)
 
       if (testedValue === expectedOutput) {
-        console.log({
+        const message = {
           didPass: true,
           message: 'Passed Test 1'
-        })
+        }
+        console.log(JSON.stringify(message))
       } else {
-        console.log({
+        const message = {
           didPass: false,
           message: 'Did not return expected value'
-        })
+        }
+        console.log(JSON.stringify(message))
       }
     }
 
@@ -59,11 +61,11 @@ In theory, any interpreted language can be used for a course as long as it can b
 
 Your tests are created as a child process. To interface vack with brightScreen, your tests should return a JSON object through the Standard Out of what every platform you are testing with.
 
-Example of Standard Iut from Tests
+Example of Standard Out from Tests
 
     {
-      didPass: false,
-      message: 'Value was not FizzBuzz'
+      "didPass": false,
+      "message": "Value was not FizzBuzz"
     }