fix(curriculum): fix typo (#59137)

2026-05-28 18:26:54 +00:00 · 2025-03-05 12:37:55 +01:00
parent 54c0fbb22b
commit 2560a05a05
5 changed files with 8 additions and 8 deletions
@@ -78,11 +78,11 @@ Your `MoodBoardItem` component should render an `h3` element with a class of `mo

 ```js
 async () => {
-  const container = await __helpers.prepTestComponent(window.index.MoodBoardItem, { description: "Carribean" });
+  const container = await __helpers.prepTestComponent(window.index.MoodBoardItem, { description: "Caribbean" });
  const text = container.querySelector(".mood-board-text");
  assert.exists(text);
  assert.equal(text.tagName, "H3");
-  assert.equal(text.textContent, "Carribean");
+  assert.equal(text.textContent, "Caribbean");
 }
 ```

@@ -324,7 +324,7 @@ export function MoodBoard() {
        <MoodBoardItem
          color='#2da64f'
          image='https://cdn.freecodecamp.org/curriculum/labs/pathway.jpg'
-          description='Carribean'
+          description='Caribbean'
        />
        <MoodBoardItem
          color='#8e44ad'
@@ -54,7 +54,7 @@ function longFunction(argument1, argument2, argument3) {

 Both linters and formatters can be integrated into your development workflow in various ways. They can be included in your build process or added as plugins to your text editor or IDE providing real-time feedback as you code. Using linters and formatters together can significantly improve code quality and consistency. For example, you might use ESLint to catch potential errors and enforce certain coding practices, and then use Prettier to handle all formatting tasks. 

-Many developement teams set up these tools as part of their project configuration often with pre-commit hooks that run the linter and formatter before allowing code to be committed. This ensures that all code in the repository meets the teams standards for quality and style.
+Many development teams set up these tools as part of their project configuration often with pre-commit hooks that run the linter and formatter before allowing code to be committed. This ensures that all code in the repository meets the teams standards for quality and style.

 In summary, linters and formatters are powerful tools that help maintain code quality, catch potential errors early, and ensure consistency across codebases. By automating this aspects of code review they allow developers to focus more on solving problems and less on debating code style.

@@ -80,7 +80,7 @@ And confirm the result:

 That worked! Our replace call replaced all of the lowercase `freecodecamp` strings, and our `match()` method matched both of them.

-What's interesting here is that when you use the global modifier with `match()`, you lose the extra information about capture groups and string indicies that would come in the match array.
+What's interesting here is that when you use the global modifier with `match()`, you lose the extra information about capture groups and string indices that would come in the match array.

 Thankfully, 2019's ECMAScript update brought us two new methods: `matchAll()` and `replaceAll()`. Like their singular counterparts, these methods accept a string or regular expression, and `replaceAll()` also accepts a second argument as the string to replace with. 

@@ -1026,11 +1026,11 @@ Which of the following attributes is used to create a programmatic relationship

 ---

-`aria-controling`
+`aria-controlling`

 ---

-`aria-controled`
+`aria-controlled`

 #### --answer--

@@ -36,7 +36,7 @@ function pauseAudio() {
 The `Audio()` constructor has properties just as it has methods. Those properties include:

 - `currenttime`: for getting the current playback time of an audio
- `loop`: for making the audio play continously by automatically restarting when it reaches the end
+- `loop`: for making the audio play continuously by automatically restarting when it reaches the end
 - `muted`: for silencing the audio output of a media element regardless of volume setting

 ## Different Audio and Video Formats