I was doing this challenge and noticed that there wasn't a space after "transform:scale(2)" in the description which is inconsistent with the other challenges so I changed it to "transform: scale(2)"
<!-- Please follow this checklist and put an x in each of the boxes, like this: [x]. It will ensure that our team takes your pull request seriously. -->
- [x] I have read [freeCodeCamp's contribution guidelines](https://github.com/freeCodeCamp/freeCodeCamp/blob/master/CONTRIBUTING.md).
- [x] My pull request has a descriptive title (not a vague title like `Update index.md`)
- [x] My pull request targets the `master` branch of freeCodeCamp.
- [x] None of my changes are plagiarized from another source without proper attribution.
- [x] My article does not contain shortened URLs or affiliate links.
If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX
* added note about UpperCamelCase for ES6 classes
proposed note in issue #17864
* added note as a new heading
changed from note as a sentence to note as a heading plus the actual note
* added <code> around SpaceShuttle
* removed markdown and added <strong> tag
Modification in the sort function to implement the better practice of returning 0 for the same elements. Not implementing the practice can break the function in new browsers.
* fix: removed all ​ from tests verbiage
* fix: added single quote to start text string
* remove single quote from text line
* fix: removed the hidden chars in the testStrings
* fix: removed hidden chars from testString section
* fix: removed hidden chars form testString part
* fix: removed hidden chars from testString part
* fix: removed hidden chars from testString part
I did not understand the original lesson of "through" vs "to" upon first reading.
Later reading the code below it started to make sense... but I added a bit more to the explanation.
* Clarification of the declaration order overriding
Previous text was talking about an override but it may also confuse readers that the override was done in the order of the listing of class names inside the h1.
I also added an extra case to better clarify the situation.
* Small change mentioning the order of declaration
Missed an order of declaration emphasis on my previous commit, adding it on this one.
* feat: Update intro to currying
- Add solutions
- Add ES6 examples
* feat: Add solution to FP mutations
* feat: Add solution to function-programming map
- Add solutions, both vanilla and ES6 arrow functions
- Add JSON.stringify to console.log, makes it easier to see what the resulting output is rather than showing
e.g. [object, object, object]
* update: used the contributor's ES6 solution
Contributor originally had a non-ES6 solution and an ES6 solution. I removed the non-ES6 solution.
A test that featured nested arrays just happens to work, but nested arrays will not be removed if they’re duplicates by the current solution of this challenge. See issue #18265
* Fix type on OOP as requested on issue #18091
fix:
numLegs: 2 to numLegs: 4
on challenge:
Remember to Set the Constructor Property when Changing the Prototype
* Update remember-to-set-the-constructor-property-when-changing-the-prototype.english.md
