diff --git a/challenges/02-javascript-algorithms-and-data-structures/debugging.json b/challenges/02-javascript-algorithms-and-data-structures/debugging.json
index addbd4f1d7..90259291db 100644
--- a/challenges/02-javascript-algorithms-and-data-structures/debugging.json
+++ b/challenges/02-javascript-algorithms-and-data-structures/debugging.json
@@ -54,7 +54,7 @@
         "You may have noticed that some freeCodeCamp JavaScript challenges include their own console.  This console behaves a little differently than the browser console you used in the last challenge.",
         "The following challenge is meant to highlight some of the differences between the freeCodeCamp console and the browser console.",
         "First, the browser console.  When you load and run an ordinary JavaScript file in your browser the <code>console.log()</code> statements will print exactly what you tell them to print to the browser console the exact number of times you requested. In your in-browser text editor the process is slightly different and can be confusing at first.",
-        "Values passed to <code>console.log()</code> in the text editor block run each set of tests as well as one more time for any function calls that you have in you code.",
+        "Values passed to <code>console.log()</code> in the text editor block run each set of tests as well as one more time for any function calls that you have in your code.",
         "This lends itself to some interesting behavior and might trip you up in the beginning, because a logged value that you expect to see only once may print out many more times depending on the number of tests and the values being passed to those tests.",
         "If you would like to see only your single output and not have to worry about running through the test cycles, you can use <code>console.clear()</code>.",
         "<hr>",