Skip to content

fix(curriculum): clarify DOM element node wording#67330

Merged
majestic-owl448 merged 1 commit into
freeCodeCamp:mainfrom
MukundaKatta:codex/fix-dom-node-wording
May 12, 2026
Merged

fix(curriculum): clarify DOM element node wording#67330
majestic-owl448 merged 1 commit into
freeCodeCamp:mainfrom
MukundaKatta:codex/fix-dom-node-wording

Conversation

@MukundaKatta
Copy link
Copy Markdown
Contributor

@MukundaKatta MukundaKatta commented May 11, 2026

Checklist:

Closes #67300

This updates the DOM lesson wording from "Each node represents an HTML element" to "Each element node represents an HTML element". That keeps the beginner-friendly explanation intact while avoiding the inaccurate implication that every DOM node is an HTML element.

Verification:

  • Ran git diff --check.

@MukundaKatta MukundaKatta requested review from a team as code owners May 11, 2026 21:01
@github-actions github-actions Bot added deprioritized PR reviews are deprioritized; lacks productive input and ignores codebase best practices. scope: curriculum Lessons, Challenges, Projects and other Curricular Content in curriculum directory. and removed deprioritized PR reviews are deprioritized; lacks productive input and ignores codebase best practices. labels May 11, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Hi there,

Thanks for opening this pull request.

The automated checks found some issues:

Checklist: The PR description is missing the required checklist or some of its items are not completed:

  1. The Checklist: heading is present in the PR description.
  2. The checkbox items are ticked (changed from [ ] to [x]).
  3. You have actually completed the items in the checklist.

Please edit your PR description to include the following template with the checklist items completed.

Checklist:

<!-- 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. -->

- [ ] I have read and followed the [contribution guidelines](https://contribute.freecodecamp.org).
- [ ] I have read and followed the [how to open a pull request guide](https://contribute.freecodecamp.org/how-to-open-a-pull-request/).
- [ ] My pull request targets the `main` branch of freeCodeCamp.
- [ ] I have tested these changes either locally on my machine, or GitHub Codespaces.

<!--If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.-->

Closes #XXXXX

<!-- Feel free to add any additional description of changes below this line -->

Join us in our chat room or our forum if you have any questions or need help with contributing.

@majestic-owl448 majestic-owl448 added the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label May 12, 2026
Copy link
Copy Markdown
Contributor

@majestic-owl448 majestic-owl448 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @MukundaKatta. Congrats on your first pull request (PR)! 🎉

Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝

@majestic-owl448 majestic-owl448 enabled auto-merge (squash) May 12, 2026 07:47
@majestic-owl448 majestic-owl448 removed the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label May 12, 2026
@majestic-owl448 majestic-owl448 merged commit cbda4cf into freeCodeCamp:main May 12, 2026
20 of 21 checks passed
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators May 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

scope: curriculum Lessons, Challenges, Projects and other Curricular Content in curriculum directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect statement about DOM nodes in the “What Is the DOM, and How Do You Access Elements?” lesson

2 participants