[Term Entry] JavaScript DOM Manipulation: .querySelectorAll() #6239

[dejongbaba]

Description

Added a new entry on the .querySelectorAll() term under the DOM concept in JavaScript. Created a new file under content/javascript/concepts/dom-manipulation/terms/queryselectorall/queryselectorall.md. Added description, syntax and example on the .querySelectorAll() following the term entry template and style guide. This entry explains how to select multiple elements with a specific selector and manipulate each of them.

Issue Solved

Closes #6239

Type of Change

• Adding a new entry
• Editing an existing entry (fixing a typo, bug, issues, etc)
• Updating the documentation

Checklist

• All writings are my own.
• My entry follows the Codecademy Docs style guide.
• My changes generate no new warnings.
• I have performed a self-review of my own writing and code.
• I have checked my entry and corrected any misspellings.
• I have made corresponding changes to the documentation if needed.
• I have confirmed my changes are not being pushed from my forked main branch.
• I have confirmed that I'm pushing from a new branch named after the changes I'm making.
• I have linked any issues that are relevant to this PR in the Issues Solved section.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ mamtawardhani
✅ dakshdeepHERE
❌ dejongbaba
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dakshdeepHERE]

I have few comments for @dejongbaba you to work on :) Tag me once u are done with them

[dejongbaba]

I have few comments for @dejongbaba you to work on :) Tag me once u are done with them

Alright, thanks for the feedback

[dejongbaba]

@dakshdeepHERE I've updated the document as requested

[dakshdeepHERE]

LGTM

[mamtawardhani]

LGTM 🚀

[mamtawardhani]

Hey @dejongbaba @dakshdeepHERE, just noticed that this issue has already been taken care of by the author who was assigned to it, so we have an entry for this already. I'll have to close this PR.

@dejongbaba for future reference, please claim an issue first and once it has been assigned to you, then raise a PR. Thank you 😄