fix: resolve weekly spelling check findings (#44906)

* fix: resolve weekly spelling check findings

* Fix more

* Fix more stuff

---------

Co-authored-by: Sida Chen <sidachen2003@gmail.com>

Author: BHUVANSH855

.vscode/dictionaries/code-entities.txt

@@ -41,6 +41,7 @@ android-safetynet
 animalfound
 anims
 anonid
+anyref
 apacheconf
 apachectl
 appcache
@@ -55,6 +56,7 @@ armeabi
 armn
 armnlow
 armv81
+arrayref
 arrowpanel
 assetlinks
 associationlist
@@ -141,6 +143,7 @@ contentaccessible
 contentdelete
 contentoccluded
 contentvisibilityautostatechange
+contextoverflow
 controlslist
 cookiechange
 cpanel-dcv
@@ -169,6 +172,7 @@ currentscreenchange
 cwrap
 daala
 dangi
+dataidx
 deviceproximity
 devtools.aboutdebugging
 devtools.errorconsole
@@ -217,6 +221,7 @@ ehtml
 EISU
 elementname
 elementtiming
+elemidx
 elems
 emailtracking
 emcc
@@ -229,6 +234,7 @@ enable-tracejit
 enableiOES
 endstreaming
 enterpictureinpicture
+eqref
 equalsize
 EquationiOES
 ethi
@@ -528,6 +534,9 @@ nsIURL
 nsIXSLT
 nsPIDOMWindow
 nsresult
+nullexternref
+nullfuncref
+nullref
 nums
 OEM_CUSEL
 OEM_ENLW
@@ -544,6 +553,7 @@ oncanmakepayment
 oncharacterboundsupdate
 onclipboardchange
 oncontentvisibilityautostatechange
+oncontextoverflow
 oncurrententrychange
 oncurrentscreenchange
 ondequeue
@@ -779,6 +789,7 @@ svgref
 svgz
 tabbox
 tabbrowser
+tableidx
 tabs-closebutton
 tabular-nums
 tagidx

.vscode/dictionaries/ignore-list.txt

@@ -75,6 +75,7 @@ cbbabbbbcdebc
 cdbBdbsbz
 CHANGEME
 chatserver
+cheesemakers
 Clampin
 clita
 cmFuZG9tQ2hhbGxlbmdl
@@ -334,6 +335,7 @@ Wookie
 XYZD
 xyzzy
 Y3JlZGVudGlhbElk
+Yarrrr
 YOUREXT
 YsAIAAAA-QG4G6kCMAMBAAAAAAAoK
 YSDEgCDwkICAIOaWhyDwn6aE

.vscode/dictionaries/non-english.txt

@@ -7,6 +7,7 @@ Aéro
 bezje
 canadien
 Ceci
+chaussures
 Clima
 communiqué
 Congrès
@@ -26,6 +27,7 @@ erkennst
 español
 Esta
 Februar
+fenêtre
 Fernstraßenbauprivatfinanzierungsgesetz
 fers
 Finden
@@ -87,6 +89,7 @@ réservé
 s'écrase
 saucisse
 saucisses
+saus
 schon
 Schonheit
 schön
@@ -96,6 +99,7 @@ semana
 será
 setembro
 shān
+sont
 Speisekarte
 studiorum
 SUIS

.vscode/dictionaries/proper-names.txt

@@ -64,6 +64,7 @@ Bitwarden
 Bixa
 Blackman
 Blackmoon
+Blacktooth
 Blankers
 Bloggs
 Bobtown
@@ -192,6 +193,7 @@ Elchi
 Elfie
 Elliotte
 Elly
+Elrond
 Emscripten
 Endtest
 Ensatina
@@ -212,6 +214,7 @@ Fairchild
 FDCP
 Firefogg
 Firesheep
+Firestore
 Firmata
 Firtman
 Flagfox
@@ -521,12 +524,14 @@ Rapp
 Rauschmayer
 Realtek
 Recep
+Redbeard
 Reis
 Rekapi
 Remy
 Resian
 Resig
 Rigby
+Rivendell
 Robison
 Rocher
 Rohini

.vscode/dictionaries/terms-abbreviations.txt

@@ -101,6 +101,7 @@ CCPA
 CCPL
 CELP
 CGATS
+chatbots
 cheatsheet
 checkboard
 checkedness
@@ -793,6 +794,7 @@ Tanuki
 targetable
 taskbars
 taskboard
+tealish
 teleporting
 telepresence
 texels

files/en-us/glossary/fork/index.md

@@ -14,7 +14,7 @@ Forks are often seen in free and open source software development. This is now a
 ## See also
 
 - [Fork](<https://en.wikipedia.org/wiki/Fork_(software_development)>) on Wikipedia
-- [How to fork a GitHub repo](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) (fork as in a Git context)
+- [How to fork a GitHub repo](https://docs.github.com/en/pull-requests/how-tos/work-with-forks/fork-a-repo) (fork as in a Git context)
 - Various "well-known" forks
   - [Linux distributions](https://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Distribution_Timeline.svg)
   - [Node.js and io.js (which have been merged together back)](https://nodejs.org/en/blog/announcements/foundation-v4-announce/)

files/en-us/learn_web_development/about/index.md

@@ -78,7 +78,7 @@ The topics presented are covered in differing levels of detail.
 There are also several areas that we explicitly don't cover in this curriculum, namely:
 
 - Exhaustive coverage of back-end languages/platforms. We do provide a brief introduction in [Node.js (Express)](/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs) and [Python (Django)](/en-US/docs/Learn_web_development/Extensions/Server-side/Django) as it is useful to every web developer to understand how HTTP and server-side technologies work. However, we don't provide exhaustive coverage across multiple platforms; that would be out of scope for MDN.
-- In-depth coverage of traditional relational databases (for example, [MySQL](https://dev.mysql.com/doc/) or [Postgres](https://www.postgresql.org/)) and other server-side datastores (for example, cloud databases such as [MongoDB](https://www.mongodb.com/) or [Google Cloud Datastore](https://cloud.google.com/products/datastore)). We provide a brief introduction to such technologies in our [Server-side website programming](/en-US/docs/Learn_web_development/Extensions/Server-side) modules.
+- In-depth coverage of traditional relational databases (for example, [MySQL](https://dev.mysql.com/doc/) or [Postgres](https://www.postgresql.org/)) and other server-side datastores (for example, cloud databases such as [MongoDB](https://www.mongodb.com/) or [Firestore](https://cloud.google.com/products/firestore)). We provide a brief introduction to such technologies in our [Server-side website programming](/en-US/docs/Learn_web_development/Extensions/Server-side) modules.
 - Deep-dive DevOps topics such as cloud platforms for provisioning and automation (for example, [Amazon AWS](https://aws.amazon.com/), [Google Cloud Platform](https://console.cloud.google.com/), and [Microsoft Azure](https://azure.microsoft.com/)) and containerization tools (for example, [Kubernetes](https://kubernetes.io/) and [Docker](https://www.docker.com/)). We lightly touch upon some tools that are considered to be in the DevOps space — like GitHub and automated testing tools — but these have distinct crossover into the front-end developer space.
 - Graphic design beyond the basic knowledge outlined in [Design for developers](/en-US/docs/Learn_web_development/Core/Design_for_developers).
 - Skills related to roles such as product and program management (for example, organization, research, and planning).

files/en-us/learn_web_development/core/version_control/index.md

@@ -23,15 +23,15 @@ This module takes you through the essentials of version control using Git and Gi
 
 ## Guides
 
-- [About GitHub and Git (from GitHub)](https://docs.github.com/en/get-started/start-your-journey/about-github-and-git)
+- [What is GitHub? (from GitHub)](https://docs.github.com/en/get-started/start-your-journey/what-is-github)
   - : This covers what Git and GitHub are, how they work together, and how to get started.
-- [Hello, World (from GitHub)](https://docs.github.com/en/get-started/start-your-journey/hello-world)
+- [Hello, World (from GitHub)](https://docs.github.com/en/get-started/using-github/hello-world)
   - : This practical guide jumps right into using GitHub, teaching the basics of Git such as creating repositories and branches, making commits, and opening and merging pull requests.
 - [Using Git (from GitHub)](https://docs.github.com/en/get-started/using-git)
   - : The Git Handbook goes into a little more depth, explaining what a version control tool is, what a repository is, how the basic GitHub model works, Git commands and examples, and more.
 - [Contributing to a project (from GitHub)](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project)
   - : Forking projects is essential when you want to contribute to someone else's code. This guide explains how.
-- [About Pull Requests (from GitHub)](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
+- [About Pull Requests (from GitHub)](https://docs.github.com/en/pull-requests/reference/pull-requests)
   - : A useful guide to managing pull requests. These requests are how you propose code changes to someone else's repository so they can review and potentially merge them into the main codebase.
 - [About issues (from GitHub)](https://docs.github.com/en/issues/tracking-your-work-with-issues/learning-about-issues/about-issues)
   - : Issues are like a forum for your GitHub project, where people can ask questions and report problems, and you can manage updates (for example assigning people to fix issues, clarifying the issue, letting people know things are fixed). This article tells you what you need to know about issues.
@@ -46,7 +46,7 @@ This module takes you through the essentials of version control using Git and Gi
 
 - Other useful topics covered in GitHub Docs include:
   - [Understanding the GitHub flow](https://docs.github.com/en/get-started/using-github/github-flow)
-  - [Addressing merge conflicts](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts)
+  - [Addressing merge conflicts](https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests)
   - [Ignoring files with .gitignore](https://docs.github.com/en/get-started/git-basics/ignoring-files)
   - [Authentication to GitHub](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-authentication-to-github)
   - [Mastering markdown](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) (the text format you write in on PR, issue comments, and `.md` files).

files/en-us/mdn/community/getting_started/index.md

@@ -38,7 +38,7 @@ We also recommend reading the following learning material:
 
 - [Basic etiquette for open source projects](/en-US/docs/MDN/Community/Open_source_etiquette): If you've never contributed to an open source project before, we encourage you to read this document.
 - [Learn web development](/en-US/docs/Learn_web_development): If you are new to HTML, CSS, JavaScript, we have some great content to help you get started.
-- [Deep dive into collaborating with pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests)
+- [Deep dive into collaborating with pull requests](https://docs.github.com/en/pull-requests)
 
 Some writing-specific contribution opportunities will require a reasonable understanding of the English language.
 That said, don't worry if your grammar isn't perfect: we have a team of people who will review your writing and help improve it.

files/en-us/mdn/community/pull_requests/index.md

@@ -77,7 +77,7 @@ When you're ready to open a pull request, follow these guidelines:
   If you don't know how to resolve the underlying issues, ask for help.
 - **Resolve merge conflicts** with the main branch; you are responsible for resolving these.
   You can do this by merging the `mdn/main` branch into your branch.
-  For more information, see the GitHub documentation on [keeping your branch up to date](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch#about-keeping-your-pull-request-in-sync).
+  For more information, see the GitHub documentation on [keeping your branch up to date](https://docs.github.com/en/pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch#about-keeping-your-pull-request-in-sync).
 - **Be responsive to feedback.**
   This means being prepared to make changes to the pull request based on the review.
   If a review happens and the changes are not made, the pull request may be closed.
@@ -88,7 +88,7 @@ When you're ready to open a pull request, follow these guidelines:
 
 ## Pull request review process
 
-Reviewer(s) are automatically assigned when you open a pull request based on a `CODEOWNERS` file, but if there is a specific person you want to request review from, you can [request a review](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) manually.
+Reviewer(s) are automatically assigned when you open a pull request based on a `CODEOWNERS` file, but if there is a specific person you want to request review from, you can [request a review](https://docs.github.com/en/pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) manually.
 We also use auto-labeling on pull requests to help us triage them.
 Maintainers can further triage pull requests and add any additional labels, such as `needs-info` or `on-hold`, if needed based on context.
 
@@ -136,8 +136,8 @@ When you are reviewing a pull request, you should:
   If you are not sure how to fix the failing tests, [ask for help](/en-US/docs/MDN/Community/Communication_channels) or assign the pull request to someone else.
 
 If a pull request looks good apart from small typos or other minor issues, you may want to fix the problem directly.
-You can do this provided the pull request [has been set up to allow changes](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork).
-It's recommended to use [comments with suggestions](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request) for fixing minor issues, as they can be batched and committed in one go.
+You can do this provided the pull request [has been set up to allow changes](https://docs.github.com/en/pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork).
+It's recommended to use [comments with suggestions](https://docs.github.com/en/pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request) for fixing minor issues, as they can be batched and committed in one go.
 
 When submitting your review you have three options, **approve**, **comment**, or **request changes**.
 The following sections explain when to use each option.