Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The challenges prior to this method use the match() method to determine regex tests, in this there is a sudden use of the test method. There should be a small description to be provided to the user so that he/she can understand the difference between the two, also the challenge requires the use of the test method in place of match, so a beginner might be replacing the test with match only to be thrown with an error. Alternatively, the guide can provide the description necessary. I can open a PR and do the modifications. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Not Browser Specific Browser Version: Not Browser Specific Operating System: Not OS Specific If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): <img width="1160" alt="screenshot 2019-02-08 at 1 32 33 am" src="https://user-"<img width="623" alt="screenshot 2019-02-08 at 1 32 47 am" src="https://user-"
Really that requirement is just to make sure you don't change any line besides the one that says .
Yes but then again, in the next challenge, a user maybe inclined to try the test method as well. Causes a bit of ambiguity.
I specifically remember being confused by '.test()' because FCC just threw it in there without an explanation, so I think 's concerns are valid.
On checking through some stack overflow, i have observed that method will return a boolean true or false on whether a regex matches a string or not, whereas a method will return the matching strings or a . So it would be worthwhile to add a note to explain the use of test in contrast to match in this particular challenge. any thoughts ?
The first challenge in the Regular Expressions section introduces the method, so they've definitely had a chance to learn about it. That said, the instructions do talk about while the tests require you to use , so it is a little muddled. It wouldn't hurt to remind someone that exists, so I think using it as part of the challenge is perfectly fine. In light of that, all I would change is the description. If you're still interested in working on this, I'd recommend modifying the description (the examples in particular) to use .
I have never modified a challenge before, but I have been looking into it and would love to try to help out. I am working on it right now, if that's alright.

Discussion:
<section id='description'> Sometimes you won't (or don't need to) know the exact characters in your patterns. Thinking of all words that match, say, a misspelling would take a long time. Luckily, you can save time using the wildcard character: <code>.</code> The wildcard character <code>.</code> will match any one character. The wildcard is also called <code>dot</code> and <code>period</code>. You can use the wildcard character just like any other character in the regex. For example, if you wanted to match <code>"hug"</code>, <code>"huh"</code>, <code>"hut"</code>, and <code>"hum"</code>, you can use the regex <code>/hu./</code> to match all four words. <del> <blockquote>let humStr = "I'll hum a song";<br>let hugStr = "Bear hug";<br>let huRegex = /hu./;<br>humStr.match(huRegex); // Returns ["hum"]<br>hugStr.match(huRegex); // Returns ["hug"]</blockquote> </del> <ins> <blockquote>let humStr = "I'll hum a song";<br>let hugStr = "Bear hug";<br>let huRegex = /hu./;<br>humStr.test(huRegex); // Returns true<br>hugStr.test(huRegex); // Returns true</blockquote> </ins> </section> ## Instructions