* fix(learn): address escaped backticks
Addresses the instances of escaped backticks - where a backtick is
preceded by a backslash. In most cases, this was left over from the
old parser. In some cases, a backtick was intended to be wrapped in
code tags and has been adjusted accordingly.
This issue came to light due to a bug in the translation flow on
Crowdin.
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: EVEN MORE :( :( :(
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: backslash nightmares
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: When you wish upon a *******
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix(curriculum): md error introduced by formatter
* fix(curriculum): remove extra `s
* fix: restore quote symbol
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: Typo
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: apply review changes
Applying review feedback from call with @RandellDawson.
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fix: markdown does weird stuff sometimes
Can't stick backticks together - use code.
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: remove isHidden flag from frontmatter
* fix: add isUpcomingChange
Co-authored-by: Ahmad Abdolsaheb <ahmad.abdolsaheb@gmail.com>
* feat: hide blocks not challenges
Co-authored-by: Ahmad Abdolsaheb <ahmad.abdolsaheb@gmail.com>
Co-authored-by: Ahmad Abdolsaheb <ahmad.abdolsaheb@gmail.com>
* feat: update backend project links
Replace solution and remix Glitch links with equivalent Repl.it links in backend projects/challenges and intro pages.
* fix: link and Repl.it casing
* fix: update mention of glitch in testing challenge
* Apply suggestions from code review
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Mrugesh Mohapatra <1884376+raisedadead@users.noreply.github.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* add solution to a challenge
add solution to the challenge: add-a-description-to-your-package-json
* add comment to all backend challenges
The comment expllains that these challenges don't need a solution.
* Add link to boilerplate Glitch file
The boilerplate link is hard to see in the previous "introduction" page. I was using the old Glitch project link, and was confused.
When I googled for a solution, it was clear than others had also been quite confused. I believe this additional instruction will help many people.
* Direct people back to introduction page
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Remove unnecessary indentation
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* Remove spaces on empty line
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Remove spaces on empty line
Co-Authored-By: Randell Dawson <5313213+RandellDawson@users.noreply.github.com>
* Add empty line to fix markdown link
Markdown link needs a blank line to render correctly
* fix: add extra line to prevent linting error
* fix/remove-bullet-points
Co-authored-by: Randell Dawson <rdawson@onepathtech.com>
Co-authored-by: Tom <tmondloch01@gmail.com>
* fix: Improved grammar
Replaced 'middlewares' to 'middleware functions'. Middleware is an uncountable noun, just like 'software'. No such word as 'softwares'
* Update curriculum/challenges/english/05-apis-and-microservices/basic-node-and-express/serve-static-assets.english.md
Co-Authored-By: Parth Parth <34807532+thecodingaviator@users.noreply.github.com>
* fix: converted blockquotes
* fix: revert to blockquote
* fix: changed js to http
Co-Authored-By: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* fix: reverted back to blockquote
* fix: reverted back to blockquote
* fix: reverted back to blockquote
* Basic gramatical changes
Corrected a few typos to improve the wording
* commit suggested changes
Improve line 9 from "before" to "earlier"
Revert line 14
<!-- 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