From 0418c594451e042dfb57ef4fa6ce0bcf38273b73 Mon Sep 17 00:00:00 2001 From: Oliver Eyton-Williams Date: Fri, 26 Nov 2021 15:06:22 +0100 Subject: [PATCH] docs: explain dynamic hints in more depth (#44290) --- docs/how-to-work-on-coding-challenges.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-work-on-coding-challenges.md b/docs/how-to-work-on-coding-challenges.md index f635f1e3b4..5292a7f90e 100644 --- a/docs/how-to-work-on-coding-challenges.md +++ b/docs/how-to-work-on-coding-challenges.md @@ -64,7 +64,7 @@ Tests to run against user code, in pairs of markdown text and code block test co Code for test one ``` -If you want dynamic output based on the user's code, --fcc-expected-- and --fcc-actual-- will be replaced with the expected and actual values of the test's assertion: +If you want dynamic output based on the user's code, --fcc-expected-- and --fcc-actual-- will be replaced with the expected and actual values of the test's assertion. Take care if you have multiple assertions since the first failing assertion will determine the values of --fcc-expected-- and --fcc-actual--. ```js assert.equal(