fix: address crowdin issues (#43021)

curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/introduction-to-html5-elements.md

@@ -47,7 +47,7 @@ assert(
 );
 ```
 
-Your `p` element should contain the first few words of the provided additional `kitty ipsum text`.
+Your `p` element should contain the first few words of the provided additional `kitty ipsum` text.
 
 ```js
 assert.isTrue(/Purr\s+jump\s+eat/gi.test($('p').text()));

curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/link-to-internal-sections-of-a-page-with-anchor-elements.md

@@ -51,7 +51,7 @@ The `a` tag should have an `href` attribute set to "#footer".
 assert($('a').eq(0).attr('href') == '#footer');
 ```
 
-The `a` tag should not have a `target` attribute
+The `a` tag should not have a `target` attribute.
 
 ```js
 assert(

curriculum/challenges/english/03-front-end-libraries/jquery/target-html-elements-with-selectors-using-jquery.md

@@ -10,7 +10,7 @@ dashedName: target-html-elements-with-selectors-using-jquery
 
 # --description--
 
-Now we have a `document ready function`.
+Now we have a `document ready` function.
 
 Now let's write our first jQuery statement. All jQuery functions start with a `$`, usually referred to as a dollar sign operator, or as bling.
 

docs/devops.md

@@ -209,7 +209,7 @@ You can identify the exact version deployed by visiting the build and deployment
 
 There are some known limitations and tradeoffs when using the beta version of the platform.
 
-- #### All data / personal progress on these beta platforms `will NOT be saved or carried over` to production.
+- #### All data / personal progress on these beta platforms will NOT be saved or carried over to production.
 
   **Users on the beta version will have a separate account from the production.** The beta version uses a physically separate database from production. This gives us the ability to prevent any accidental loss of data or modifications. The dev team may purge the database on this beta version as needed.
 

docs/how-to-work-on-practice-projects.md

@@ -85,7 +85,7 @@ part-6.md
 
 At some point you decide you need to delete `part-2.md`, because that step is no longer needed. Also, you decide to break down `part-4.md` into three steps instead of just one.
 
-To accomplish this restructure, you would need to delete `part-2.md` and then add a `part-4a.md` and a `part-5b.md`. The new folder structure would look like the following:
+To accomplish this restructure, you would need to delete `part-2.md` and then add a `part-4a.md` and a `part-4b.md`. The new folder structure would look like the following:
 
 ```bash
 part-001.md

docs/moderator-handbook.md

@@ -115,7 +115,7 @@ Sometimes there will be a Merge Conflict.
 
 This means that another pull request has made a change to that same part of that same file. GitHub has a tool for addressing these merge conflicts right on GitHub. You can try to address these conflicts. Just use your best judgment.
 
-The pull request's changes will be on top, and the Master branch's changes will be on the bottom. Sometimes there will be redundant information in there that can be deleted. Before you finish, be sure to delete the `<<<<<<`, `======`, and `>>>>>>` that Git adds to indicate areas of conflict.
+The pull request's changes will be on top, and the main branch's changes will be on the bottom. Sometimes there will be redundant information in there that can be deleted. Before you finish, be sure to delete the `<<<<<<`, `======`, and `>>>>>>` that Git adds to indicate areas of conflict.
 
 If you are uncertain, please ask one of the fellow moderators or the dev-team for assistance.
 
@@ -414,7 +414,7 @@ git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git
 
 git fetch upstream
 
-git pull upstream master
+git pull upstream main
 ```
 
 If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above.