diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
index ea03447fed..489404af43 100644
--- a/.github/FUNDING.yml
+++ b/.github/FUNDING.yml
@@ -1,2 +1,2 @@
-github: CodeYourFuture
-custom: https://codeyourfuture.io/donate
+github: CodeYourFuture
+custom: https://codeyourfuture.io/donate
diff --git a/.github/workflows/validate-pr-metadata.yml b/.github/workflows/validate-pr-metadata.yml
index 10ef3c74ab..a4967039d4 100644
--- a/.github/workflows/validate-pr-metadata.yml
+++ b/.github/workflows/validate-pr-metadata.yml
@@ -1,18 +1,18 @@
-name: Validate PR Metadata
-on:
-  pull_request_target:
-    types:
-      - labeled
-      - unlabeled
-      - opened
-      - edited
-      - reopened
-
-jobs:
-  validate_pr_metadata:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: CodeYourFuture/actions/validate-pr-metadata@main
-        with:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+name: Validate PR Metadata
+on:
+  pull_request_target:
+    types:
+      - labeled
+      - unlabeled
+      - opened
+      - edited
+      - reopened
+
+jobs:
+  validate_pr_metadata:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: CodeYourFuture/actions/validate-pr-metadata@main
+        with:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.gitignore b/.gitignore
index bde36e5302..946c065ca3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,4 @@
-node_modules
-.DS_Store
-.vscode
+node_modules
+.DS_Store
+.vscode
 **/.DS_Store
\ No newline at end of file
diff --git a/.npmrc b/.npmrc
index 43c97e719a..094e38421d 100644
--- a/.npmrc
+++ b/.npmrc
@@ -1 +1 @@
-package-lock=false
+package-lock=false
diff --git a/.prettierrc b/.prettierrc
index 59bb3b44f1..b0985c1023 100644
--- a/.prettierrc
+++ b/.prettierrc
@@ -1,19 +1,19 @@
-{
-  "arrowParens": "always",
-  "bracketSpacing": true,
-  "embeddedLanguageFormatting": "auto",
-  "htmlWhitespaceSensitivity": "css",
-  "insertPragma": false,
-  "jsxBracketSameLine": false,
-  "jsxSingleQuote": false,
-  "printWidth": 80,
-  "proseWrap": "preserve",
-  "quoteProps": "as-needed",
-  "requirePragma": false,
-  "semi": true,
-  "singleQuote": false,
-  "tabWidth": 2,
-  "trailingComma": "es5",
-  "useTabs": false,
-  "vueIndentScriptAndStyle": false
-}
+{
+  "arrowParens": "always",
+  "bracketSpacing": true,
+  "embeddedLanguageFormatting": "auto",
+  "htmlWhitespaceSensitivity": "css",
+  "insertPragma": false,
+  "jsxBracketSameLine": false,
+  "jsxSingleQuote": false,
+  "printWidth": 80,
+  "proseWrap": "preserve",
+  "quoteProps": "as-needed",
+  "requirePragma": false,
+  "semi": true,
+  "singleQuote": false,
+  "tabWidth": 2,
+  "trailingComma": "es5",
+  "useTabs": false,
+  "vueIndentScriptAndStyle": false
+}
diff --git a/.vscode/extensions.json b/.vscode/extensions.json
index 2dd5a24324..58edcd0425 100644
--- a/.vscode/extensions.json
+++ b/.vscode/extensions.json
@@ -1,11 +1,11 @@
-{
-  "recommendations": [
-    "esbenp.prettier-vscode",
-    "dbaeumer.vscode-eslint",
-    "streetsidesoftware.code-spell-checker",
-    "eamodio.gitlens",
-    "ritwickdey.LiveServer",
-    "vsliveshare.vsliveshare",
-    "Orta.vscode-jest"
-  ]
-}
+{
+  "recommendations": [
+    "esbenp.prettier-vscode",
+    "dbaeumer.vscode-eslint",
+    "streetsidesoftware.code-spell-checker",
+    "eamodio.gitlens",
+    "ritwickdey.LiveServer",
+    "vsliveshare.vsliveshare",
+    "Orta.vscode-jest"
+  ]
+}
diff --git a/Sprint-1/1-key-exercises/2-initials.js b/Sprint-1/1-key-exercises/2-initials.js
index 47561f6175..f251f77d14 100644
--- a/Sprint-1/1-key-exercises/2-initials.js
+++ b/Sprint-1/1-key-exercises/2-initials.js
@@ -1,11 +1,13 @@
-let firstName = "Creola";
-let middleName = "Katherine";
-let lastName = "Johnson";
-
-// Declare a variable called initials that stores the first character of each string.
-// This should produce the string "CKJ", but you must not write the characters C, K, or J in the code of your solution.
-
-let initials = ``;
-
-// https://www.google.com/search?q=get+first+character+of+string+mdn
-
+let firstName = "Creola";
+let middleName = "Katherine";
+let lastName = "Johnson";
+
+// Declare a variable called initials that stores the first character of each string.
+// This should produce the string "CKJ", but you must not write the characters C, K, or J in the code of your solution.
+
+// let initials = ``;
+let initials = `${firstName.charAt(0)} ${middleName.charAt(0)} ${lastName.charAt(0)}`;
+
+console.log(initials);
+
+// https://www.google.com/search?q=get+first+character+of+string+mdn
diff --git a/Sprint-1/1-key-exercises/3-paths.js b/Sprint-1/1-key-exercises/3-paths.js
index ab90ebb28e..a4aeebcc54 100644
--- a/Sprint-1/1-key-exercises/3-paths.js
+++ b/Sprint-1/1-key-exercises/3-paths.js
@@ -1,23 +1,23 @@
-// The diagram below shows the different names for parts of a file path on a Unix operating system
-
-// ┌─────────────────────┬────────────┐
-// │          dir        │    base    │
-// ├──────┬              ├──────┬─────┤
-// │ root │              │ name │ ext │
-// "  /    home/user/dir / file  .txt "
-// └──────┴──────────────┴──────┴─────┘
-
-// (All spaces in the "" line should be ignored. They are purely for formatting.)
-
-const filePath = "/Users/mitch/cyf/Module-JS1/week-1/interpret/file.txt";
-const lastSlashIndex = filePath.lastIndexOf("/");
-const base = filePath.slice(lastSlashIndex + 1);
-console.log(`The base part of ${filePath} is ${base}`);
-
-// Create a variable to store the dir part of the filePath variable
-// Create a variable to store the ext part of the variable
-
-const dir = ;
-const ext = ;
-
+// The diagram below shows the different names for parts of a file path on a Unix operating system
+
+// ┌─────────────────────┬────────────┐
+// │          dir        │    base    │
+// ├──────┬              ├──────┬─────┤
+// │ root │              │ name │ ext │
+// "  /    home/user/dir / file  .txt "
+// └──────┴──────────────┴──────┴─────┘
+
+// (All spaces in the "" line should be ignored. They are purely for formatting.)
+
+const filePath = "/Users/mitch/cyf/Module-JS1/week-1/interpret/file.txt";
+const lastSlashIndex = filePath.lastIndexOf("/");
+const base = filePath.slice(lastSlashIndex + 1);
+console.log(`The base part of ${filePath} is ${base}`);
+
+// Create a variable to store the dir part of the filePath variable
+// Create a variable to store the ext part of the variable
+
+const dir = ;
+const ext = ;
+
 // https://www.google.com/search?q=slice+mdn
\ No newline at end of file
diff --git a/Sprint-1/1-key-exercises/4-random.js b/Sprint-1/1-key-exercises/4-random.js
index 292f83aabb..3cf4542b4e 100644
--- a/Sprint-1/1-key-exercises/4-random.js
+++ b/Sprint-1/1-key-exercises/4-random.js
@@ -1,9 +1,9 @@
-const minimum = 1;
-const maximum = 100;
-
-const num = Math.floor(Math.random() * (maximum - minimum + 1)) + minimum;
-
-// In this exercise, you will need to work out what num represents?
-// Try breaking down the expression and using documentation to explain what it means
-// It will help to think about the order in which expressions are evaluated
-// Try logging the value of num and running the program several times to build an idea of what the program is doing
+const minimum = 1;
+const maximum = 100;
+
+const num = Math.floor(Math.random() * (maximum - minimum + 1)) + minimum;
+
+// In this exercise, you will need to work out what num represents?
+// Try breaking down the expression and using documentation to explain what it means
+// It will help to think about the order in which expressions are evaluated
+// Try logging the value of num and running the program several times to build an idea of what the program is doing
diff --git a/Sprint-1/2-mandatory-errors/0.js b/Sprint-1/2-mandatory-errors/0.js
index cf6c5039f7..f1931b6ef1 100644
--- a/Sprint-1/2-mandatory-errors/0.js
+++ b/Sprint-1/2-mandatory-errors/0.js
@@ -1,2 +1,2 @@
-This is just an instruction for the first activity - but it is just for human consumption
+This is just an instruction for the first activity - but it is just for human consumption
 We don't want the computer to run these 2 lines - how can we solve this problem?
\ No newline at end of file
diff --git a/Sprint-1/2-mandatory-errors/1.js b/Sprint-1/2-mandatory-errors/1.js
index 7a43cbea76..26e8490abd 100644
--- a/Sprint-1/2-mandatory-errors/1.js
+++ b/Sprint-1/2-mandatory-errors/1.js
@@ -1,4 +1,4 @@
-// trying to create an age variable and then reassign the value by 1
-
-const age = 33;
-age = age + 1;
+// trying to create an age variable and then reassign the value by 1
+
+const age = 33;
+age = age + 1;
diff --git a/Sprint-1/2-mandatory-errors/2.js b/Sprint-1/2-mandatory-errors/2.js
index e09b89831d..5087483e76 100644
--- a/Sprint-1/2-mandatory-errors/2.js
+++ b/Sprint-1/2-mandatory-errors/2.js
@@ -1,5 +1,5 @@
-// Currently trying to print the string "I was born in Bolton" but it isn't working...
-// what's the error ?
-
-console.log(`I was born in ${cityOfBirth}`);
-const cityOfBirth = "Bolton";
+// Currently trying to print the string "I was born in Bolton" but it isn't working...
+// what's the error ?
+
+console.log(`I was born in ${cityOfBirth}`);
+const cityOfBirth = "Bolton";
diff --git a/Sprint-1/2-mandatory-errors/3.js b/Sprint-1/2-mandatory-errors/3.js
index ec101884db..463f57a4be 100644
--- a/Sprint-1/2-mandatory-errors/3.js
+++ b/Sprint-1/2-mandatory-errors/3.js
@@ -1,9 +1,9 @@
-const cardNumber = 4533787178994213;
-const last4Digits = cardNumber.slice(-4);
-
-// The last4Digits variable should store the last 4 digits of cardNumber
-// However, the code isn't working
-// Before running the code, make and explain a prediction about why the code won't work
-// Then run the code and see what error it gives.
-// Consider: Why does it give this error? Is this what I predicted? If not, what's different?
-// Then try updating the expression last4Digits is assigned to, in order to get the correct value
+const cardNumber = 4533787178994213;
+const last4Digits = cardNumber.slice(-4);
+
+// The last4Digits variable should store the last 4 digits of cardNumber
+// However, the code isn't working
+// Before running the code, make and explain a prediction about why the code won't work
+// Then run the code and see what error it gives.
+// Consider: Why does it give this error? Is this what I predicted? If not, what's different?
+// Then try updating the expression last4Digits is assigned to, in order to get the correct value
diff --git a/Sprint-1/2-mandatory-errors/4.js b/Sprint-1/2-mandatory-errors/4.js
index 5f86c730bc..461663dfc8 100644
--- a/Sprint-1/2-mandatory-errors/4.js
+++ b/Sprint-1/2-mandatory-errors/4.js
@@ -1,2 +1,2 @@
-const 12HourClockTime = "8:53pm";
-const 24hourClockTime = "20:53";
+const 12HourClockTime = "8:53pm";
+const 24hourClockTime = "20:53";
diff --git a/Sprint-1/3-mandatory-interpret/1-percentage-change.js b/Sprint-1/3-mandatory-interpret/1-percentage-change.js
index e24ecb8e18..7f12ffd9b8 100644
--- a/Sprint-1/3-mandatory-interpret/1-percentage-change.js
+++ b/Sprint-1/3-mandatory-interpret/1-percentage-change.js
@@ -1,22 +1,22 @@
-let carPrice = "10,000";
-let priceAfterOneYear = "8,543";
-
-carPrice = Number(carPrice.replaceAll(",", ""));
-priceAfterOneYear = Number(priceAfterOneYear.replaceAll("," ""));
-
-const priceDifference = carPrice - priceAfterOneYear;
-const percentageChange = (priceDifference / carPrice) * 100;
-
-console.log(`The percentage change is ${percentageChange}`);
-
-// Read the code and then answer the questions below
-
-// a) How many function calls are there in this file? Write down all the lines where a function call is made
-
-// b) Run the code and identify the line where the error is coming from - why is this error occurring? How can you fix this problem?
-
-// c) Identify all the lines that are variable reassignment statements
-
-// d) Identify all the lines that are variable declarations
-
-// e) Describe what the expression Number(carPrice.replaceAll(",","")) is doing - what is the purpose of this expression?
+let carPrice = "10,000";
+let priceAfterOneYear = "8,543";
+
+carPrice = Number(carPrice.replaceAll(",", ""));
+priceAfterOneYear = Number(priceAfterOneYear.replaceAll("," ""));
+
+const priceDifference = carPrice - priceAfterOneYear;
+const percentageChange = (priceDifference / carPrice) * 100;
+
+console.log(`The percentage change is ${percentageChange}`);
+
+// Read the code and then answer the questions below
+
+// a) How many function calls are there in this file? Write down all the lines where a function call is made
+
+// b) Run the code and identify the line where the error is coming from - why is this error occurring? How can you fix this problem?
+
+// c) Identify all the lines that are variable reassignment statements
+
+// d) Identify all the lines that are variable declarations
+
+// e) Describe what the expression Number(carPrice.replaceAll(",","")) is doing - what is the purpose of this expression?
diff --git a/Sprint-1/3-mandatory-interpret/2-time-format.js b/Sprint-1/3-mandatory-interpret/2-time-format.js
index 47d2395587..3fb0bb3aef 100644
--- a/Sprint-1/3-mandatory-interpret/2-time-format.js
+++ b/Sprint-1/3-mandatory-interpret/2-time-format.js
@@ -1,25 +1,25 @@
-const movieLength = 8784; // length of movie in seconds
-
-const remainingSeconds = movieLength % 60;
-const totalMinutes = (movieLength - remainingSeconds) / 60;
-
-const remainingMinutes = totalMinutes % 60;
-const totalHours = (totalMinutes - remainingMinutes) / 60;
-
-const result = `${totalHours}:${remainingMinutes}:${remainingSeconds}`;
-console.log(result);
-
-// For the piece of code above, read the code and then answer the following questions
-
-// a) How many variable declarations are there in this program?
-
-// b) How many function calls are there?
-
-// c) Using documentation, explain what the expression movieLength % 60 represents
-// https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Arithmetic_Operators
-
-// d) Interpret line 4, what does the expression assigned to totalMinutes mean?
-
-// e) What do you think the variable result represents? Can you think of a better name for this variable?
-
-// f) Try experimenting with different values of movieLength. Will this code work for all values of movieLength? Explain your answer
+const movieLength = 8784; // length of movie in seconds
+
+const remainingSeconds = movieLength % 60;
+const totalMinutes = (movieLength - remainingSeconds) / 60;
+
+const remainingMinutes = totalMinutes % 60;
+const totalHours = (totalMinutes - remainingMinutes) / 60;
+
+const result = `${totalHours}:${remainingMinutes}:${remainingSeconds}`;
+console.log(result);
+
+// For the piece of code above, read the code and then answer the following questions
+
+// a) How many variable declarations are there in this program?
+
+// b) How many function calls are there?
+
+// c) Using documentation, explain what the expression movieLength % 60 represents
+// https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Arithmetic_Operators
+
+// d) Interpret line 4, what does the expression assigned to totalMinutes mean?
+
+// e) What do you think the variable result represents? Can you think of a better name for this variable?
+
+// f) Try experimenting with different values of movieLength. Will this code work for all values of movieLength? Explain your answer
diff --git a/Sprint-1/4-stretch-explore/chrome.md b/Sprint-1/4-stretch-explore/chrome.md
index e7dd5feafe..8cdb0a6d2e 100644
--- a/Sprint-1/4-stretch-explore/chrome.md
+++ b/Sprint-1/4-stretch-explore/chrome.md
@@ -1,18 +1,18 @@
-Open a new window in Chrome,
-
-then locate the **Console** tab.
-
-Voila! You now have access to the [Chrome V8 Engine](https://www.cloudflare.com/en-gb/learning/serverless/glossary/what-is-chrome-v8/).
-Just like the Node REPL, you can input JavaScript code into the Console tab and the V8 engine will execute it.
-
-Let's try an example.
-
-In the Chrome console,
-invoke the function `alert` with an input string of `"Hello world!"`;
-
-What effect does calling the `alert` function have?
-
-Now try invoking the function `prompt` with a string input of `"What is your name?"` - store the return value of your call to `prompt` in an variable called `myName`.
-
-What effect does calling the `prompt` function have?
-What is the return value of `prompt`?
+Open a new window in Chrome,
+
+then locate the **Console** tab.
+
+Voila! You now have access to the [Chrome V8 Engine](https://www.cloudflare.com/en-gb/learning/serverless/glossary/what-is-chrome-v8/).
+Just like the Node REPL, you can input JavaScript code into the Console tab and the V8 engine will execute it.
+
+Let's try an example.
+
+In the Chrome console,
+invoke the function `alert` with an input string of `"Hello world!"`;
+
+What effect does calling the `alert` function have?
+
+Now try invoking the function `prompt` with a string input of `"What is your name?"` - store the return value of your call to `prompt` in an variable called `myName`.
+
+What effect does calling the `prompt` function have?
+What is the return value of `prompt`?
diff --git a/Sprint-1/4-stretch-explore/objects.md b/Sprint-1/4-stretch-explore/objects.md
index 0216dee56a..421809e5fe 100644
--- a/Sprint-1/4-stretch-explore/objects.md
+++ b/Sprint-1/4-stretch-explore/objects.md
@@ -1,16 +1,16 @@
-## Objects
-
-In this activity, we'll explore some additional concepts that you'll encounter in more depth later on in the course.
-
-Open the Chrome devtools Console, type in `console.log` and then hit enter
-
-What output do you get?
-
-Now enter just `console` in the Console, what output do you get back?
-
-Try also entering `typeof console`
-
-Answer the following questions:
-
-What does `console` store?
-What does the syntax `console.log` or `console.assert` mean? In particular, what does the `.` mean?
+## Objects
+
+In this activity, we'll explore some additional concepts that you'll encounter in more depth later on in the course.
+
+Open the Chrome devtools Console, type in `console.log` and then hit enter
+
+What output do you get?
+
+Now enter just `console` in the Console, what output do you get back?
+
+Try also entering `typeof console`
+
+Answer the following questions:
+
+What does `console` store?
+What does the syntax `console.log` or `console.assert` mean? In particular, what does the `.` mean?
diff --git a/Sprint-1/readme.md b/Sprint-1/readme.md
index 62d24c9580..7227cdeb1f 100644
--- a/Sprint-1/readme.md
+++ b/Sprint-1/readme.md
@@ -1,35 +1,35 @@
-# 🧭 Guide to Week 1 exercises
-
-> https://programming.codeyourfuture.io/structuring-data/sprints/1/prep/
-
-> [!TIP]
-> You should always do the prep work _before_ attempting the coursework.
-> The prep shows you _how_ to do the coursework.
-> There is often a step by step video you can code along with too.
-> Do the prep.
-
-This README will guide you through the different sections for this week.
-
-## 1 Exercises
-
-In this section, you'll have a short program and task. Some of the syntax may be unfamiliar - in this case, you'll need to look things up in documentation. 
-
-https://developer.mozilla.org/en-US/docs/Web/JavaScript
-
-## 2 Errors
-
-In this section, you'll need to go to each file in `errors` directory and run the file with node to check what the error is. Your task is to interpret the error message and explain why it occurs. The [errors documentation](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors) will help you figure out the solution.
-
-## 3 Interpret
-
-In these tasks, you have to interpret a slightly larger program with some syntax / operators / functions that may be unfamiliar.
-
-You must use documentation to make sense of anything unfamiliar - learning how to look things up this way is a fundamental part of being a developer!
-
-You can also use `console.log` to check the value of different variables in the code.
-
-https://developer.mozilla.org/en-US/docs/Web/JavaScript 
-
-## 4 Explore - Stretch 💪
-
-This stretch activity will get you to start exploring new concepts and environments by yourself. It will do so by prompting you to reflect on some questions.
+# 🧭 Guide to Week 1 exercises
+
+> https://programming.codeyourfuture.io/structuring-data/sprints/1/prep/
+
+> [!TIP]
+> You should always do the prep work _before_ attempting the coursework.
+> The prep shows you _how_ to do the coursework.
+> There is often a step by step video you can code along with too.
+> Do the prep.
+
+This README will guide you through the different sections for this week.
+
+## 1 Exercises
+
+In this section, you'll have a short program and task. Some of the syntax may be unfamiliar - in this case, you'll need to look things up in documentation. 
+
+https://developer.mozilla.org/en-US/docs/Web/JavaScript
+
+## 2 Errors
+
+In this section, you'll need to go to each file in `errors` directory and run the file with node to check what the error is. Your task is to interpret the error message and explain why it occurs. The [errors documentation](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors) will help you figure out the solution.
+
+## 3 Interpret
+
+In these tasks, you have to interpret a slightly larger program with some syntax / operators / functions that may be unfamiliar.
+
+You must use documentation to make sense of anything unfamiliar - learning how to look things up this way is a fundamental part of being a developer!
+
+You can also use `console.log` to check the value of different variables in the code.
+
+https://developer.mozilla.org/en-US/docs/Web/JavaScript 
+
+## 4 Explore - Stretch 💪
+
+This stretch activity will get you to start exploring new concepts and environments by yourself. It will do so by prompting you to reflect on some questions.
diff --git a/Sprint-3/1-implement-and-rewrite-tests/README.md b/Sprint-3/1-implement-and-rewrite-tests/README.md
index 4658c9423a..6df7faaee5 100644
--- a/Sprint-3/1-implement-and-rewrite-tests/README.md
+++ b/Sprint-3/1-implement-and-rewrite-tests/README.md
@@ -1,47 +1,47 @@
-# Implement solutions and rewrite tests with Jest
-
-Before writing any code, please read the [Testing Function Guide](testing-guide.md) to learn how
-to choose test values that thoroughly test a function.
-
-## 1 Implement solutions
-
-In the `implement` directory you've got a number of functions you'll need to implement.
-For each function, you also have a number of different cases you'll need to check for your function.
-
-Write your implementation and your tests to cover the cases the function should fulfil.
-
-Here is a recommended order:
-
-1. `1-get-angle-type.js`
-2. `2-is-proper-fraction.js`
-3. `3-get-card-value.js`
-
-## 2 Rewrite tests with Jest
-
-`console.log` is most often used as a debugging tool. We use to inspect the state of our program during runtime.
-
-We can use `console.assert` to write assertions: however, it is not very easy to use when writing large test suites. In the first section, Implement, we used a custom "helper function" to make our assertions more readable.
-
-Jest is a whole library of helper functions we can use to make our assertions more readable and easier to write.
-
-Your new task is to write the same tests as you wrote in the `implement` directory, but using Jest instead of `console.assert`.
-
-You shouldn't have to change the contents of `implement` to write these tests.
-
-There are files for your Jest tests in the `rewrite-tests-with-jest` directory. They will automatically use the functions you already implemented.
-
-You can run all the tests in this repo by running `npm test` in your terminal. However, VSCode has a built-in test runner that you can use to run the tests, and this should make it much easier to focus on building up your test cases one at a time.
-
-https://code.visualstudio.com/docs/editor/testing
-
-1. Go to rewrite-tests-with-jest/1-get-angle-type.test.js
-2. Click the green play button to run the test. It's on the left of the test function in the gutter.
-3. Read the output in the TEST_RESULTS tab at the bottom of the screen.
-4. Explore all the tests in this repo by opening the TEST EXPLORER tab. The logo is a beaker.
-
-![VSCode Test Runner](../../run-this-test.png)
-
-![Test Results](../../test-results-output.png)
-
-> [!TIP]
-> You can always run a single test file by running `npm test path/to/test-file.test.js`.
+# Implement solutions and rewrite tests with Jest
+
+Before writing any code, please read the [Testing Function Guide](testing-guide.md) to learn how
+to choose test values that thoroughly test a function.
+
+## 1 Implement solutions
+
+In the `implement` directory you've got a number of functions you'll need to implement.
+For each function, you also have a number of different cases you'll need to check for your function.
+
+Write your implementation and your tests to cover the cases the function should fulfil.
+
+Here is a recommended order:
+
+1. `1-get-angle-type.js`
+2. `2-is-proper-fraction.js`
+3. `3-get-card-value.js`
+
+## 2 Rewrite tests with Jest
+
+`console.log` is most often used as a debugging tool. We use to inspect the state of our program during runtime.
+
+We can use `console.assert` to write assertions: however, it is not very easy to use when writing large test suites. In the first section, Implement, we used a custom "helper function" to make our assertions more readable.
+
+Jest is a whole library of helper functions we can use to make our assertions more readable and easier to write.
+
+Your new task is to write the same tests as you wrote in the `implement` directory, but using Jest instead of `console.assert`.
+
+You shouldn't have to change the contents of `implement` to write these tests.
+
+There are files for your Jest tests in the `rewrite-tests-with-jest` directory. They will automatically use the functions you already implemented.
+
+You can run all the tests in this repo by running `npm test` in your terminal. However, VSCode has a built-in test runner that you can use to run the tests, and this should make it much easier to focus on building up your test cases one at a time.
+
+https://code.visualstudio.com/docs/editor/testing
+
+1. Go to rewrite-tests-with-jest/1-get-angle-type.test.js
+2. Click the green play button to run the test. It's on the left of the test function in the gutter.
+3. Read the output in the TEST_RESULTS tab at the bottom of the screen.
+4. Explore all the tests in this repo by opening the TEST EXPLORER tab. The logo is a beaker.
+
+![VSCode Test Runner](../../run-this-test.png)
+
+![Test Results](../../test-results-output.png)
+
+> [!TIP]
+> You can always run a single test file by running `npm test path/to/test-file.test.js`.
diff --git a/Sprint-3/1-implement-and-rewrite-tests/implement/1-get-angle-type.js b/Sprint-3/1-implement-and-rewrite-tests/implement/1-get-angle-type.js
index 9e05a871e2..89df26cf1a 100644
--- a/Sprint-3/1-implement-and-rewrite-tests/implement/1-get-angle-type.js
+++ b/Sprint-3/1-implement-and-rewrite-tests/implement/1-get-angle-type.js
@@ -1,37 +1,59 @@
-// Implement a function getAngleType
-//
-// When given an angle in degrees, it should return a string indicating the type of angle:
-// - "Acute angle" for angles greater than 0° and less than 90°
-// - "Right angle" for exactly 90°
-// - "Obtuse angle" for angles greater than 90° and less than 180°
-// - "Straight angle" for exactly 180°
-// - "Reflex angle" for angles greater than 180° and less than 360°
-// - "Invalid angle" for angles outside the valid range.
-
-// Assumption: The parameter is a valid number. (You do not need to handle non-numeric inputs.)
-
-// Acceptance criteria:
-// After you have implemented the function, write tests to cover all the cases, and
-// execute the code to ensure all tests pass.
-
-function getAngleType(angle) {
-  // TODO: Implement this function
-}
-
-// The line below allows us to load the getAngleType function into tests in other files.
-// This will be useful in the "rewrite tests with jest" step.
-module.exports = getAngleType;
-
-// This helper function is written to make our assertions easier to read.
-// If the actual output matches the target output, the test will pass
-function assertEquals(actualOutput, targetOutput) {
-  console.assert(
-    actualOutput === targetOutput,
-    `Expected ${actualOutput} to equal ${targetOutput}`
-  );
-}
-
-// TODO: Write tests to cover all cases, including boundary and invalid cases.
-// Example: Identify Right Angles
-const right = getAngleType(90);
-assertEquals(right, "Right angle");
+// Implement a function getAngleType
+//
+// When given an angle in degrees, it should return a string indicating the type of angle:
+// - "Acute angle" for angles greater than 0° and less than 90°
+// - "Right angle" for exactly 90°
+// - "Obtuse angle" for angles greater than 90° and less than 180°
+// - "Straight angle" for exactly 180°
+// - "Reflex angle" for angles greater than 180° and less than 360°
+// - "Invalid angle" for angles outside the valid range.
+
+// Assumption: The parameter is a valid number. (You do not need to handle non-numeric inputs.)
+
+// Acceptance criteria:
+// After you have implemented the function, write tests to cover all the cases, and
+// execute the code to ensure all tests pass.
+
+function getAngleType(angle) {
+  // TODO: Implement this function
+  if (angle < 90) {
+    return "Acute angle";
+  }
+  if (angle === 90) {
+    return "Right angle";
+  }
+  if (angle > 90 && angle < 180) {
+    return "Obtuse angle";
+  }
+  if (angle === 180) {
+    return "Straight angle";
+  }
+  if (angle > 180 && angle < 360) {
+    return "Reflex angle";
+  } else {
+    return "Invalid";
+  }
+}
+
+// The line below allows us to load the getAngleType function into tests in other files.
+// This will be useful in the "rewrite tests with jest" step.
+module.exports = getAngleType;
+
+// This helper function is written to make our assertions easier to read.
+// If the actual output matches the target output, the test will pass
+function assertEquals(actualOutput, targetOutput) {
+  console.assert(
+    actualOutput === targetOutput,
+    `Expected ${actualOutput} to equal ${targetOutput}`
+  );
+}
+
+// TODO: Write tests to cover all cases, including boundary and invalid cases.
+// Example: Identify Right Angles
+const right = getAngleType(90);
+assertEquals(right, "Right angle");
+assertEquals(getAngleType(45), "Acute angle");
+assertEquals(getAngleType(145), "Obtuse angle");
+assertEquals(getAngleType(180), "Straight angle");
+assertEquals(getAngleType(190), "Reflex angle");
+assertEquals(getAngleType(390), "Invalid");
diff --git a/Sprint-3/1-implement-and-rewrite-tests/implement/2-is-proper-fraction.js b/Sprint-3/1-implement-and-rewrite-tests/implement/2-is-proper-fraction.js
index 970cb9b641..705fa84c90 100644
--- a/Sprint-3/1-implement-and-rewrite-tests/implement/2-is-proper-fraction.js
+++ b/Sprint-3/1-implement-and-rewrite-tests/implement/2-is-proper-fraction.js
@@ -1,33 +1,38 @@
-// Implement a function isProperFraction,
-// when given two numbers, a numerator and a denominator, it should return true if
-// the given numbers form a proper fraction, and false otherwise.
-
-// Assumption: The parameters are valid numbers (not NaN or Infinity).
-
-// Note: If you are unfamiliar with proper fractions, please look up its mathematical definition.
-
-// Acceptance criteria:
-// After you have implemented the function, write tests to cover all the cases, and
-// execute the code to ensure all tests pass.
-
-function isProperFraction(numerator, denominator) {
-  // TODO: Implement this function
-}
-
-// The line below allows us to load the isProperFraction function into tests in other files.
-// This will be useful in the "rewrite tests with jest" step.
-module.exports = isProperFraction;
-
-// Here's our helper again
-function assertEquals(actualOutput, targetOutput) {
-  console.assert(
-    actualOutput === targetOutput,
-    `Expected ${actualOutput} to equal ${targetOutput}`
-  );
-}
-
-// TODO: Write tests to cover all cases.
-// What combinations of numerators and denominators should you test?
-
-// Example: 1/2 is a proper fraction
-assertEquals(isProperFraction(1, 2), true);
+// Implement a function isProperFraction,
+// when given two numbers, a numerator and a denominator, it should return true if
+// the given numbers form a proper fraction, and false otherwise.
+
+// Assumption: The parameters are valid numbers (not NaN or Infinity).
+
+// Note: If you are unfamiliar with proper fractions, please look up its mathematical definition.
+
+// Acceptance criteria:
+// After you have implemented the function, write tests to cover all the cases, and
+// execute the code to ensure all tests pass.
+
+function isProperFraction(numerator, denominator) {
+  // TODO: Implement this function
+  let fraction = Math.abs(numerator) < Math.abs(denominator);
+  return fraction;
+}
+
+// The line below allows us to load the isProperFraction function into tests in other files.
+// This will be useful in the "rewrite tests with jest" step.
+module.exports = isProperFraction;
+
+// Here's our helper again
+function assertEquals(actualOutput, targetOutput) {
+  console.assert(
+    actualOutput === targetOutput,
+    `Expected ${actualOutput} to equal ${targetOutput}`
+  );
+}
+
+// TODO: Write tests to cover all cases.
+// What combinations of numerators and denominators should you test?
+
+// Example: 1/2 is a proper fraction
+assertEquals(isProperFraction(1, 2), true);
+assertEquals(isProperFraction(5, 2), false);
+assertEquals(isProperFraction(7, 9), true);
+assertEquals(isProperFraction(3, -5), true);
diff --git a/Sprint-3/1-implement-and-rewrite-tests/implement/3-get-card-value.js b/Sprint-3/1-implement-and-rewrite-tests/implement/3-get-card-value.js
index ff5c532e1d..6ae3492ef6 100644
--- a/Sprint-3/1-implement-and-rewrite-tests/implement/3-get-card-value.js
+++ b/Sprint-3/1-implement-and-rewrite-tests/implement/3-get-card-value.js
@@ -1,54 +1,109 @@
-// This problem involves playing cards: https://en.wikipedia.org/wiki/Standard_52-card_deck
-
-// Implement a function getCardValue, when given a string representing a playing card,
-// should return the numerical value of the card.
-
-// A valid card string will contain a rank followed by the suit.
-// The rank can be one of the following strings:
-//   "A", "2", "3", "4", "5", "6", "7", "8", "9", "10", "J", "Q", "K"
-// The suit can be one of the following emojis:
-//   "♠", "♥", "♦", "♣"
-// For example: "A♠", "2♥", "10♥", "J♣", "Q♦", "K♦".
-
-// When the card is an ace ("A"), the function should return 11.
-// When the card is a face card ("J", "Q", "K"), the function should return 10.
-// When the card is a number card ("2" to "10"), the function should return its numeric value.
-
-// When the card string is invalid (not following the above format), the function should
-// throw an error.
-
-// Acceptance criteria:
-// After you have implemented the function, write tests to cover all the cases, and
-// execute the code to ensure all tests pass.
-
-function getCardValue(card) {
-  // TODO: Implement this function
-}
-
-// The line below allows us to load the getCardValue function into tests in other files.
-// This will be useful in the "rewrite tests with jest" step.
-module.exports = getCardValue;
-
-// Helper functions to make our assertions easier to read.
-function assertEquals(actualOutput, targetOutput) {
-  console.assert(
-    actualOutput === targetOutput,
-    `Expected ${actualOutput} to equal ${targetOutput}`
-  );
-}
-
-// TODO: Write tests to cover all outcomes, including throwing errors for invalid cards.
-// Examples:
-assertEquals(getCardValue("9♠"), 9);
-
-// Handling invalid cards
-try {
-  getCardValue("invalid");
-
-  // This line will not be reached if an error is thrown as expected
-  console.error("Error was not thrown for invalid card 😢");
-} catch (e) {
-  console.log("Error thrown for invalid card 🎉");
-}
-
-// What other invalid card cases can you think of?
+// This problem involves playing cards: https://en.wikipedia.org/wiki/Standard_52-card_deck
+
+// Implement a function getCardValue, when given a string representing a playing card,
+// should return the numerical value of the card.
+
+// A valid card string will contain a rank followed by the suit.
+// The rank can be one of the following strings:
+//   "A", "2", "3", "4", "5", "6", "7", "8", "9", "10", "J", "Q", "K"
+// The suit can be one of the following emojis:
+//   "♠", "♥", "♦", "♣"
+// For example: "A♠", "2♥", "10♥", "J♣", "Q♦", "K♦".
+
+// When the card is an ace ("A"), the function should return 11.
+// When the card is a face card ("J", "Q", "K"), the function should return 10.
+// When the card is a number card ("2" to "10"), the function should return its numeric value.
+
+// When the card string is invalid (not following the above format), the function should
+// throw an error.
+
+// Acceptance criteria:
+// After you have implemented the function, write tests to cover all the cases, and
+// execute the code to ensure all tests pass.
+
+function getCardValue(card) {
+  // TODO: Implement this function
+
+  const ranks = [
+    "A",
+    "2",
+    "3",
+    "4",
+    "5",
+    "6",
+    "7",
+    "8",
+    "9",
+    "10",
+    "J",
+    "Q",
+    "K",
+  ];
+  const suits = ["♠", "♥", "♦", "♣"];
+
+  const rank1 = card.slice(0, -1);
+  const suit1 = card.slice(-1);
+  const IsEqualCard = suits.includes(suit1) && ranks.includes(rank1);
+  if (!IsEqualCard) {
+    throw new Error("invalid card ");
+  }
+  if (rank1 === "A") {
+    return 11;
+  }
+  if (rank1 === "J" || rank1 === "Q" || rank1 === "K") {
+    return 10;
+  }
+  const numberRanks = Number(rank1);
+  if (numberRanks >= 2 && numberRanks <= 10) {
+    return numberRanks;
+  }
+}
+
+// The line below allows us to load the getCardValue function into tests in other files.
+// This will be useful in the "rewrite tests with jest" step.
+module.exports = getCardValue;
+
+// Helper functions to make our assertions easier to read.
+function assertEquals(actualOutput, targetOutput) {
+  console.assert(
+    actualOutput === targetOutput,
+    `Expected ${actualOutput} to equal ${targetOutput}`
+  );
+}
+
+// TODO: Write tests to cover all outcomes, including throwing errors for invalid cards.
+// Examples:
+assertEquals(getCardValue("9♠"), 9);
+assertEquals(getCardValue("10♦"), 10);
+assertEquals(getCardValue("7♠"), 7);
+assertEquals(getCardValue("8♥"), 8);
+assertEquals(getCardValue("A♥"), 11);
+assertEquals(getCardValue("J♥"), 10);
+assertEquals(getCardValue("Q♥"), 10);
+assertEquals(getCardValue("K♥"), 10);
+
+// Handling invalid cards
+try {
+  getCardValue("invalid");
+
+  // This line will not be reached if an error is thrown as expected
+  console.error("Error was not thrown for invalid card 😢");
+} catch (e) {
+  console.log("Error thrown for invalid card 🎉");
+}
+
+try {
+  getCardValue("1♠");
+  console.error("Error was not thrown 😢");
+} catch (e) {
+  console.log("Error thrown for invalid 🎉");
+}
+
+try {
+  getCardValue("error");
+  console.error("Error was not thrown 😢");
+} catch (e) {
+  console.log("Error thrown for invalid 🎉");
+}
+
+// What other invalid card cases can you think of?
diff --git a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/1-get-angle-type.test.js b/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/1-get-angle-type.test.js
index d777f348d3..5269484f79 100644
--- a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/1-get-angle-type.test.js
+++ b/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/1-get-angle-type.test.js
@@ -1,20 +1,46 @@
-// This statement loads the getAngleType function you wrote in the implement directory.
-// We will use the same function, but write tests for it using Jest in this file.
-const getAngleType = require("../implement/1-get-angle-type");
-
-// TODO: Write tests in Jest syntax to cover all cases/outcomes,
-// including boundary and invalid cases.
-
-// Case 1: Acute angles
-test(`should return "Acute angle" when (0 < angle < 90)`, () => {
-  // Test various acute angles, including boundary cases
-  expect(getAngleType(1)).toEqual("Acute angle");
-  expect(getAngleType(45)).toEqual("Acute angle");
-  expect(getAngleType(89)).toEqual("Acute angle");
-});
-
-// Case 2: Right angle
-// Case 3: Obtuse angles
-// Case 4: Straight angle
-// Case 5: Reflex angles
-// Case 6: Invalid angles
+// This statement loads the getAngleType function you wrote in the implement directory.
+// We will use the same function, but write tests for it using Jest in this file.
+const getAngleType = require("../implement/1-get-angle-type");
+
+// TODO: Write tests in Jest syntax to cover all cases/outcomes,
+// including boundary and invalid cases.
+
+// Case 1: Acute angles
+test(`should return "Acute angle" when ( angle > 0 and angle < 90)`, () => {
+  // Test various acute angles, including boundary cases
+  expect(getAngleType(1)).toEqual("Acute angle");
+  expect(getAngleType(45)).toEqual("Acute angle");
+  expect(getAngleType(89)).toEqual("Acute angle");
+});
+
+// Case 2: Right angle
+test(`should return "Right angle" when angle exactly equals 90`, () => {
+  expect(getAngleType(90)).toEqual("Right angle");
+});
+
+// Case 3: Obtuse angles
+describe(`should return "obtuse angle" when obtuse > 90 and obtuse < 180`, () => {
+  expect(getAngleType(95)).toEqual("Obtuse angle");
+  expect(getAngleType(99)).toEqual("Obtuse angle");
+  expect(getAngleType(105)).toEqual("Obtuse angle");
+});
+// Case 4: Straight angle
+
+test(`should return "straight angle" when straight is equals 180`, () => {
+  expect(getAngleType(180)).toEqual("Straight angle");
+});
+// Case 5: Reflex angles
+test(`should return "reflex angle" if angle is more than 180 and less than 360`, () => {
+  expect(getAngleType(181)).toEqual("Reflex angle");
+  expect(getAngleType(191)).toEqual("Reflex angle");
+  expect(getAngleType(211)).toEqual("Reflex angle");
+});
+
+// tes(`should return "reflex angle" when straight is  `);
+// Case 6: Invalid angles
+test(`should return "invalid angle" if any of them don't match`, () => {
+  expect(getAngleType(385)).toEqual("Invalid");
+  expect(getAngleType(380)).toEqual("Invalid");
+  expect(getAngleType(430)).toEqual("Invalid");
+  expect(getAngleType(390)).toEqual("Invalid");
+});
diff --git a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/2-is-proper-fraction.test.js b/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/2-is-proper-fraction.test.js
index 7f087b2ba1..98be5f25d8 100644
--- a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/2-is-proper-fraction.test.js
+++ b/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/2-is-proper-fraction.test.js
@@ -1,10 +1,25 @@
-// This statement loads the isProperFraction function you wrote in the implement directory.
-// We will use the same function, but write tests for it using Jest in this file.
-const isProperFraction = require("../implement/2-is-proper-fraction");
-
-// TODO: Write tests in Jest syntax to cover all combinations of positives, negatives, zeros, and other categories.
-
-// Special case: numerator is zero
-test(`should return false when denominator is zero`, () => {
-  expect(isProperFraction(1, 0)).toEqual(false);
-});
+// This statement loads the isProperFraction function you wrote in the implement directory.
+// We will use the same function, but write tests for it using Jest in this file.
+const isProperFraction = require("../implement/2-is-proper-fraction");
+
+// TODO: Write tests in Jest syntax to cover all combinations of positives, negatives, zeros, and other categories.
+
+// Special case: numerator is zero
+test(`should return false when denominator is zero`, () => {
+  expect(isProperFraction(1, 0)).toEqual(false);
+});
+test(`should  return true when denominator is 5`, () => {
+  expect(isProperFraction(2, 5)).toEqual(true);
+});
+
+test(`should return true when denominator is 10`, () => {
+  expect(isProperFraction(4, 10)).toEqual(true);
+});
+
+test(`should return false when denominator is -1`, () => {
+  expect(isProperFraction(3, -1)).toEqual(false);
+});
+
+test(`should return false when denominator is 0`, () => {
+  expect(isProperFraction(5, 0)).toEqual(false);
+});
diff --git a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/3-get-card-value.test.js b/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/3-get-card-value.test.js
index cf7f9dae2e..57bd088666 100644
--- a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/3-get-card-value.test.js
+++ b/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/3-get-card-value.test.js
@@ -1,20 +1,36 @@
-// This statement loads the getCardValue function you wrote in the implement directory.
-// We will use the same function, but write tests for it using Jest in this file.
-const getCardValue = require("../implement/3-get-card-value");
-
-// TODO: Write tests in Jest syntax to cover all possible outcomes.
-
-// Case 1: Ace (A)
-test(`Should return 11 when given an ace card`, () => {
-  expect(getCardValue("A♠")).toEqual(11);
-});
-
-// Suggestion: Group the remaining test data into these categories:
-//   Number Cards (2-10)
-//   Face Cards (J, Q, K)
-//   Invalid Cards
-
-// To learn how to test whether a function throws an error as expected in Jest,
-// please refer to the Jest documentation:
-// https://jestjs.io/docs/expect#tothrowerror
-
+// This statement loads the getCardValue function you wrote in the implement directory.
+// We will use the same function, but write tests for it using Jest in this file.
+const getCardValue = require("../implement/3-get-card-value");
+
+// TODO: Write tests in Jest syntax to cover all possible outcomes.
+
+// Case 1: Ace (A)
+test(`Should return 11 when given an ace card`, () => {
+  expect(getCardValue("A♠")).toEqual(11);
+});
+
+// Suggestion: Group the remaining test data into these categories:
+//   Number Cards (2-10)
+test(`Should return 9,6,4,2 when given a card number`, () => {
+  expect(getCardValue("9♠")).toEqual(9);
+  expect(getCardValue("6♠")).toEqual(6);
+  expect(getCardValue("4♠")).toEqual(4);
+  expect(getCardValue("2♠")).toEqual(2);
+});
+//   Face Cards (J, Q, K)
+
+test(`should return 10 when given face card `, () => {
+  expect(getCardValue("J♥")).toEqual(10);
+  expect(getCardValue("Q♥")).toEqual(10);
+  expect(getCardValue("K♥")).toEqual(10);
+});
+//   Invalid Cards
+test(`should return invalid when given a invalid input`, () => {
+  expect(() => {
+    getCardValue("invalid");
+  }).toThrow();
+});
+
+// To learn how to test whether a function throws an error as expected in Jest,
+// please refer to the Jest documentation:
+// https://jestjs.io/docs/expect#tothrowerror
diff --git a/Sprint-3/1-implement-and-rewrite-tests/testing-guide.md b/Sprint-3/1-implement-and-rewrite-tests/testing-guide.md
index 917194e7a9..1aaec7be08 100644
--- a/Sprint-3/1-implement-and-rewrite-tests/testing-guide.md
+++ b/Sprint-3/1-implement-and-rewrite-tests/testing-guide.md
@@ -1,92 +1,92 @@
-# A Beginner's Guide to Testing Functions
-
-## 1. What Is a Function?
-
-```
-Input  ──▶  Function  ──▶  Output
-```
-
-A function
-- Takes **input** (via **arguments**)
-- Does some work
-- Produces **one output** (via a **return value**)
- 
-Example:
-
-```
-sum(2, 3) → 5
-```
-
-Important idea: the same input should produce the same output.
-
-
-## 2. Testing Means Predicting
-
-Testing means: 
-> If I give this input, what output should I get?
-
-
-## 3. Choosing Good Test Values
-
-### Step 1: Determining the space of possible inputs
-Ask:
-- What type of value is expected?
-- What values make sense?
-  - If they are numbers:
-    - Are they integers or floating-point numbers?
-    - What is their range?
-  - If they are strings:
-    - What are their length and patterns?
-- What values would not make sense?
-
-### Step 2: Choosing Good Test Values 
-
-#### Normal Cases
-
-These confirm that the function works in normal use.
-
-- What does a typical, ordinary input look like?
-- Are there multiple ordinary groups of inputs? e.g. for an age checking function, maybe there are "adults" and "children" as expected ordinary groups of inputs.
-
-  
-#### Boundary Cases
-
-Test values exactly at, just inside, and just outside defined ranges. 
-These values are where logic breaks most often.
-
-#### Consider All Outcomes
-
-Every outcome must be reached by at least one test.
-
-- How many different results can this function produce?
-- Have I tested a value that leads to each one?
-
-#### Crossing the Edges and Invalid Values
-
-This tests how the function behaves when assumptions are violated.
-- What happens when input is outside of the expected range?
-- What happens when input is not of the expected type?
-- What happens when input is not in the expected format?
-
-## 4. How to Test
-
-### 1. Using `console.assert()`
-
-```javascript
-  // Report a failure only when the first argument is false
-  console.assert( sum(4, 6) === 10, "Expected 4 + 6 to equal 10" );
-```
-
-It is simpler than using `if-else` and requires no setup.
-  
-### 2. Jest Testing Framework
-
-```javascript
-  test("Should correctly return the sum of two positive numbers", () => {
-    expect( sum(4, 6) ).toEqual(10);
-    ... // Can test multiple samples 
-  });
-
-```
-
-Jest supports many useful functions for testing but requires additional setup.
+# A Beginner's Guide to Testing Functions
+
+## 1. What Is a Function?
+
+```
+Input  ──▶  Function  ──▶  Output
+```
+
+A function
+- Takes **input** (via **arguments**)
+- Does some work
+- Produces **one output** (via a **return value**)
+ 
+Example:
+
+```
+sum(2, 3) → 5
+```
+
+Important idea: the same input should produce the same output.
+
+
+## 2. Testing Means Predicting
+
+Testing means: 
+> If I give this input, what output should I get?
+
+
+## 3. Choosing Good Test Values
+
+### Step 1: Determining the space of possible inputs
+Ask:
+- What type of value is expected?
+- What values make sense?
+  - If they are numbers:
+    - Are they integers or floating-point numbers?
+    - What is their range?
+  - If they are strings:
+    - What are their length and patterns?
+- What values would not make sense?
+
+### Step 2: Choosing Good Test Values 
+
+#### Normal Cases
+
+These confirm that the function works in normal use.
+
+- What does a typical, ordinary input look like?
+- Are there multiple ordinary groups of inputs? e.g. for an age checking function, maybe there are "adults" and "children" as expected ordinary groups of inputs.
+
+  
+#### Boundary Cases
+
+Test values exactly at, just inside, and just outside defined ranges. 
+These values are where logic breaks most often.
+
+#### Consider All Outcomes
+
+Every outcome must be reached by at least one test.
+
+- How many different results can this function produce?
+- Have I tested a value that leads to each one?
+
+#### Crossing the Edges and Invalid Values
+
+This tests how the function behaves when assumptions are violated.
+- What happens when input is outside of the expected range?
+- What happens when input is not of the expected type?
+- What happens when input is not in the expected format?
+
+## 4. How to Test
+
+### 1. Using `console.assert()`
+
+```javascript
+  // Report a failure only when the first argument is false
+  console.assert( sum(4, 6) === 10, "Expected 4 + 6 to equal 10" );
+```
+
+It is simpler than using `if-else` and requires no setup.
+  
+### 2. Jest Testing Framework
+
+```javascript
+  test("Should correctly return the sum of two positive numbers", () => {
+    expect( sum(4, 6) ).toEqual(10);
+    ... // Can test multiple samples 
+  });
+
+```
+
+Jest supports many useful functions for testing but requires additional setup.
diff --git a/Sprint-3/2-practice-tdd/README.md b/Sprint-3/2-practice-tdd/README.md
index f7d82fe43d..d7a013069e 100644
--- a/Sprint-3/2-practice-tdd/README.md
+++ b/Sprint-3/2-practice-tdd/README.md
@@ -1,13 +1,13 @@
-# Practice TDD
-
-In this section you'll practice this key skill of building up your program test first.
-
-Use the Jest syntax and complete the provided files, meeting the acceptance criteria for each function. Use the VSCode test runner to run your tests and check your progress.
-
-Write the tests _before_ the code that will make them pass.
-
-Recommended order:
-
-1. `count.test.js`
-1. `repeat-str.test.js`
-1. `get-ordinal-number.test.js`
+# Practice TDD
+
+In this section you'll practice this key skill of building up your program test first.
+
+Use the Jest syntax and complete the provided files, meeting the acceptance criteria for each function. Use the VSCode test runner to run your tests and check your progress.
+
+Write the tests _before_ the code that will make them pass.
+
+Recommended order:
+
+1. `count.test.js`
+1. `repeat-str.test.js`
+1. `get-ordinal-number.test.js`
diff --git a/Sprint-3/2-practice-tdd/count.js b/Sprint-3/2-practice-tdd/count.js
index 95b6ebb7d4..8bbd6cdb3d 100644
--- a/Sprint-3/2-practice-tdd/count.js
+++ b/Sprint-3/2-practice-tdd/count.js
@@ -1,5 +1,5 @@
-function countChar(stringOfCharacters, findCharacter) {
-  return 5
-}
-
-module.exports = countChar;
+function countChar(stringOfCharacters, findCharacter) {
+  return 5
+}
+
+module.exports = countChar;
diff --git a/Sprint-3/2-practice-tdd/count.test.js b/Sprint-3/2-practice-tdd/count.test.js
index 179ea0ddf7..d9153335ed 100644
--- a/Sprint-3/2-practice-tdd/count.test.js
+++ b/Sprint-3/2-practice-tdd/count.test.js
@@ -1,24 +1,24 @@
-// implement a function countChar that counts the number of times a character occurs in a string
-const countChar = require("./count");
-// Given a string `str` and a single character `char` to search for,
-// When the countChar function is called with these inputs,
-// Then it should:
-
-// Scenario: Multiple Occurrences
-// Given the input string `str`,
-// And a character `char` that occurs one or more times in `str` (e.g., 'a' in 'aaaaa'),
-// When the function is called with these inputs,
-// Then it should correctly count occurrences of `char`.
-
-test("should count multiple occurrences of a character", () => {
-  const str = "aaaaa";
-  const char = "a";
-  const count = countChar(str, char);
-  expect(count).toEqual(5);
-});
-
-// Scenario: No Occurrences
-// Given the input string `str`,
-// And a character `char` that does not exist within `str`.
-// When the function is called with these inputs,
-// Then it should return 0, indicating that no occurrences of `char` were found.
+// implement a function countChar that counts the number of times a character occurs in a string
+const countChar = require("./count");
+// Given a string `str` and a single character `char` to search for,
+// When the countChar function is called with these inputs,
+// Then it should:
+
+// Scenario: Multiple Occurrences
+// Given the input string `str`,
+// And a character `char` that occurs one or more times in `str` (e.g., 'a' in 'aaaaa'),
+// When the function is called with these inputs,
+// Then it should correctly count occurrences of `char`.
+
+test("should count multiple occurrences of a character", () => {
+  const str = "aaaaa";
+  const char = "a";
+  const count = countChar(str, char);
+  expect(count).toEqual(5);
+});
+
+// Scenario: No Occurrences
+// Given the input string `str`,
+// And a character `char` that does not exist within `str`.
+// When the function is called with these inputs,
+// Then it should return 0, indicating that no occurrences of `char` were found.
diff --git a/Sprint-3/2-practice-tdd/get-ordinal-number.js b/Sprint-3/2-practice-tdd/get-ordinal-number.js
index f95d71db13..620d612216 100644
--- a/Sprint-3/2-practice-tdd/get-ordinal-number.js
+++ b/Sprint-3/2-practice-tdd/get-ordinal-number.js
@@ -1,5 +1,5 @@
-function getOrdinalNumber(num) {
-  return "1st";
-}
-
-module.exports = getOrdinalNumber;
+function getOrdinalNumber(num) {
+  return "1st";
+}
+
+module.exports = getOrdinalNumber;
diff --git a/Sprint-3/2-practice-tdd/get-ordinal-number.test.js b/Sprint-3/2-practice-tdd/get-ordinal-number.test.js
index adfa58560f..95a887f192 100644
--- a/Sprint-3/2-practice-tdd/get-ordinal-number.test.js
+++ b/Sprint-3/2-practice-tdd/get-ordinal-number.test.js
@@ -1,20 +1,20 @@
-const getOrdinalNumber = require("./get-ordinal-number");
-// In this week's prep, we started implementing getOrdinalNumber.
-
-// Continue testing and implementing getOrdinalNumber for additional cases.
-// Write your tests using Jest — remember to run your tests often for continual feedback.
-
-// To ensure thorough testing, we need broad scenarios that cover all possible cases.
-// Listing individual values, however, can quickly lead to an unmanageable number of test cases.
-// Instead of writing tests for individual numbers, consider grouping all possible input values
-// into meaningful categories. Then, select representative samples from each category to test.
-// This approach improves coverage and makes our tests easier to maintain.
-
-// Case 1: Numbers ending with 1 (but not 11)
-// When the number ends with 1, except those ending with 11,
-// Then the function should return a string by appending "st" to the number.
-test("should append 'st' for numbers ending with 1, except those ending with 11", () => {
-  expect(getOrdinalNumber(1)).toEqual("1st");
-  expect(getOrdinalNumber(21)).toEqual("21st");
-  expect(getOrdinalNumber(131)).toEqual("131st");
-});
+const getOrdinalNumber = require("./get-ordinal-number");
+// In this week's prep, we started implementing getOrdinalNumber.
+
+// Continue testing and implementing getOrdinalNumber for additional cases.
+// Write your tests using Jest — remember to run your tests often for continual feedback.
+
+// To ensure thorough testing, we need broad scenarios that cover all possible cases.
+// Listing individual values, however, can quickly lead to an unmanageable number of test cases.
+// Instead of writing tests for individual numbers, consider grouping all possible input values
+// into meaningful categories. Then, select representative samples from each category to test.
+// This approach improves coverage and makes our tests easier to maintain.
+
+// Case 1: Numbers ending with 1 (but not 11)
+// When the number ends with 1, except those ending with 11,
+// Then the function should return a string by appending "st" to the number.
+test("should append 'st' for numbers ending with 1, except those ending with 11", () => {
+  expect(getOrdinalNumber(1)).toEqual("1st");
+  expect(getOrdinalNumber(21)).toEqual("21st");
+  expect(getOrdinalNumber(131)).toEqual("131st");
+});
diff --git a/Sprint-3/2-practice-tdd/repeat-str.js b/Sprint-3/2-practice-tdd/repeat-str.js
index 2af0a2cea7..3edbfb7561 100644
--- a/Sprint-3/2-practice-tdd/repeat-str.js
+++ b/Sprint-3/2-practice-tdd/repeat-str.js
@@ -1,7 +1,7 @@
-function repeatStr() {
-  // Your implementation of this function must *not* call String.prototype.repeat (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/repeat).
-  // The goal is to re-implement that function, not to use it.
-  return "hellohellohello";
-}
-
-module.exports = repeatStr;
+function repeatStr() {
+  // Your implementation of this function must *not* call String.prototype.repeat (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/repeat).
+  // The goal is to re-implement that function, not to use it.
+  return "hellohellohello";
+}
+
+module.exports = repeatStr;
diff --git a/Sprint-3/2-practice-tdd/repeat-str.test.js b/Sprint-3/2-practice-tdd/repeat-str.test.js
index a3fc1196c4..126aa63af2 100644
--- a/Sprint-3/2-practice-tdd/repeat-str.test.js
+++ b/Sprint-3/2-practice-tdd/repeat-str.test.js
@@ -1,32 +1,32 @@
-// Implement a function repeatStr
-const repeatStr = require("./repeat-str");
-// Given a target string `str` and a positive integer `count`,
-// When the repeatStr function is called with these inputs,
-// Then it should:
-
-// Case: handle multiple repetitions:
-// Given a target string `str` and a positive integer `count` greater than 1,
-// When the repeatStr function is called with these inputs,
-// Then it should return a string that contains the original `str` repeated `count` times.
-
-test("should repeat the string count times", () => {
-  const str = "hello";
-  const count = 3;
-  const repeatedStr = repeatStr(str, count);
-  expect(repeatedStr).toEqual("hellohellohello");
-});
-
-// Case: handle count of 1:
-// Given a target string `str` and a `count` equal to 1,
-// When the repeatStr function is called with these inputs,
-// Then it should return the original `str` without repetition.
-
-// Case: Handle count of 0:
-// Given a target string `str` and a `count` equal to 0,
-// When the repeatStr function is called with these inputs,
-// Then it should return an empty string.
-
-// Case: Handle negative count:
-// Given a target string `str` and a negative integer `count`,
-// When the repeatStr function is called with these inputs,
-// Then it should throw an error, as negative counts are not valid.
+// Implement a function repeatStr
+const repeatStr = require("./repeat-str");
+// Given a target string `str` and a positive integer `count`,
+// When the repeatStr function is called with these inputs,
+// Then it should:
+
+// Case: handle multiple repetitions:
+// Given a target string `str` and a positive integer `count` greater than 1,
+// When the repeatStr function is called with these inputs,
+// Then it should return a string that contains the original `str` repeated `count` times.
+
+test("should repeat the string count times", () => {
+  const str = "hello";
+  const count = 3;
+  const repeatedStr = repeatStr(str, count);
+  expect(repeatedStr).toEqual("hellohellohello");
+});
+
+// Case: handle count of 1:
+// Given a target string `str` and a `count` equal to 1,
+// When the repeatStr function is called with these inputs,
+// Then it should return the original `str` without repetition.
+
+// Case: Handle count of 0:
+// Given a target string `str` and a `count` equal to 0,
+// When the repeatStr function is called with these inputs,
+// Then it should return an empty string.
+
+// Case: Handle negative count:
+// Given a target string `str` and a negative integer `count`,
+// When the repeatStr function is called with these inputs,
+// Then it should throw an error, as negative counts are not valid.
diff --git a/Sprint-3/3-dead-code/README.md b/Sprint-3/3-dead-code/README.md
index 2bfbfff819..18ccf15af6 100644
--- a/Sprint-3/3-dead-code/README.md
+++ b/Sprint-3/3-dead-code/README.md
@@ -1,9 +1,9 @@
-# Refactoring Dead Code
-
-Here are two example of code that has not been built efficiently. Both files have dead code in them. It's your job to go back through this existing code, identify the dead code, and remove it so the code is ready for production.
-
-## Instructions
-
-1. Work through each `exercise` file inside this directory.
-2. Delete the dead code.
-3. Commit your changes and make a PR when done.
+# Refactoring Dead Code
+
+Here are two example of code that has not been built efficiently. Both files have dead code in them. It's your job to go back through this existing code, identify the dead code, and remove it so the code is ready for production.
+
+## Instructions
+
+1. Work through each `exercise` file inside this directory.
+2. Delete the dead code.
+3. Commit your changes and make a PR when done.
diff --git a/Sprint-3/3-dead-code/exercise-1.js b/Sprint-3/3-dead-code/exercise-1.js
index 4d09f15fa9..f074fcd551 100644
--- a/Sprint-3/3-dead-code/exercise-1.js
+++ b/Sprint-3/3-dead-code/exercise-1.js
@@ -1,17 +1,17 @@
-// Find the instances of unreachable and redundant code - remove them!
-// The sayHello function should continue to work for any reasonable input it's given.
-
-let testName = "Jerry";
-const greeting = "hello";
-
-function sayHello(greeting, name) {
-  const greetingStr = greeting + ", " + name + "!";
-  return `${greeting}, ${name}!`;
-  console.log(greetingStr);
-}
-
-testName = "Aman";
-
-const greetingMessage = sayHello(greeting, testName);
-
-console.log(greetingMessage); // 'hello, Aman!'
+// Find the instances of unreachable and redundant code - remove them!
+// The sayHello function should continue to work for any reasonable input it's given.
+
+let testName = "Jerry";
+const greeting = "hello";
+
+function sayHello(greeting, name) {
+  const greetingStr = greeting + ", " + name + "!";
+  return `${greeting}, ${name}!`;
+  console.log(greetingStr);
+}
+
+testName = "Aman";
+
+const greetingMessage = sayHello(greeting, testName);
+
+console.log(greetingMessage); // 'hello, Aman!'
diff --git a/Sprint-3/3-dead-code/exercise-2.js b/Sprint-3/3-dead-code/exercise-2.js
index 56d7887c4c..20ab4d623f 100644
--- a/Sprint-3/3-dead-code/exercise-2.js
+++ b/Sprint-3/3-dead-code/exercise-2.js
@@ -1,28 +1,28 @@
-// Remove the unused code that does not contribute to the final console log
-// The countAndCapitalisePets function should continue to work for any reasonable input it's given, and you shouldn't modify the pets variable.
-
-const pets = ["parrot", "hamster", "horse", "dog", "hamster", "cat", "hamster"];
-const capitalisedPets = pets.map((pet) => pet.toUpperCase());
-const petsStartingWithH = pets.filter((pet) => pet[0] === "h");
-
-function logPets(petsArr) {
-  petsArr.forEach((pet) => console.log(pet));
-}
-
-function countAndCapitalisePets(petsArr) {
-  const petCount = {};
-
-  petsArr.forEach((pet) => {
-    const capitalisedPet = pet.toUpperCase();
-    if (petCount[capitalisedPet]) {
-      petCount[capitalisedPet] += 1;
-    } else {
-      petCount[capitalisedPet] = 1;
-    }
-  });
-  return petCount;
-}
-
-const countedPetsStartingWithH = countAndCapitalisePets(petsStartingWithH);
-
-console.log(countedPetsStartingWithH); // { 'HAMSTER': 3, 'HORSE': 1 } <- Final console log
+// Remove the unused code that does not contribute to the final console log
+// The countAndCapitalisePets function should continue to work for any reasonable input it's given, and you shouldn't modify the pets variable.
+
+const pets = ["parrot", "hamster", "horse", "dog", "hamster", "cat", "hamster"];
+const capitalisedPets = pets.map((pet) => pet.toUpperCase());
+const petsStartingWithH = pets.filter((pet) => pet[0] === "h");
+
+function logPets(petsArr) {
+  petsArr.forEach((pet) => console.log(pet));
+}
+
+function countAndCapitalisePets(petsArr) {
+  const petCount = {};
+
+  petsArr.forEach((pet) => {
+    const capitalisedPet = pet.toUpperCase();
+    if (petCount[capitalisedPet]) {
+      petCount[capitalisedPet] += 1;
+    } else {
+      petCount[capitalisedPet] = 1;
+    }
+  });
+  return petCount;
+}
+
+const countedPetsStartingWithH = countAndCapitalisePets(petsStartingWithH);
+
+console.log(countedPetsStartingWithH); // { 'HAMSTER': 3, 'HORSE': 1 } <- Final console log
diff --git a/Sprint-3/4-stretch/README.md b/Sprint-3/4-stretch/README.md
index 8f01227bf9..cb2533fdce 100644
--- a/Sprint-3/4-stretch/README.md
+++ b/Sprint-3/4-stretch/README.md
@@ -1,9 +1,9 @@
-# 🔍 Stretch
-
-These stretch activities are not mandatory, but we hope you will explore them after you have completed the mandatory work.
-
-In this exercise, you'll need to **play computer** with the function `find`. This function makes use of while loop statement. Your task will be to step through the code to figure out what is happening when the computer executes the code.
-
-Next, try implementing the functions specified in `password-validator.js`.
-
-Finally, set up your own script and test files for `card-validator.md`
+# 🔍 Stretch
+
+These stretch activities are not mandatory, but we hope you will explore them after you have completed the mandatory work.
+
+In this exercise, you'll need to **play computer** with the function `find`. This function makes use of while loop statement. Your task will be to step through the code to figure out what is happening when the computer executes the code.
+
+Next, try implementing the functions specified in `password-validator.js`.
+
+Finally, set up your own script and test files for `card-validator.md`
diff --git a/Sprint-3/4-stretch/card-validator.md b/Sprint-3/4-stretch/card-validator.md
index e39c6ace6e..26b72a00d0 100644
--- a/Sprint-3/4-stretch/card-validator.md
+++ b/Sprint-3/4-stretch/card-validator.md
@@ -1,35 +1,35 @@
-## **PROJECT: Credit Card Validator**
-
-In this project you'll write a script that validates whether or not a credit card number is valid.
-
-Here are the rules for a valid number:
-
-- Number must be 16 digits, all of them must be numbers.
-- You must have at least two different digits represented (all of the digits cannot be the same).
-- The final digit must be even.
-- The sum of all the digits must be greater than 16.
-
-For example, the following credit card numbers are valid:
-
-```markdown
-9999777788880000
-6666666666661666
-```
-
-And the following credit card numbers are invalid:
-
-```markdown
-a92332119c011112 (invalid characters)
-4444444444444444 (only one type of number)
-1111111111111110 (sum less than 16)
-6666666666666661 (odd final number)
-```
-
-These are the requirements your project needs to fulfill:
-
-- Make a JavaScript file with a name that describes its contents.
-- Create a function with a descriptive name which makes it clear what the function does. The function should take one argument, the credit card number to validate.
-- Write at least 2 comments that explain to others what a line of code is meant to do.
-- Return a boolean from the function to indicate whether the credit card number is valid.
-
-Good luck!
+## **PROJECT: Credit Card Validator**
+
+In this project you'll write a script that validates whether or not a credit card number is valid.
+
+Here are the rules for a valid number:
+
+- Number must be 16 digits, all of them must be numbers.
+- You must have at least two different digits represented (all of the digits cannot be the same).
+- The final digit must be even.
+- The sum of all the digits must be greater than 16.
+
+For example, the following credit card numbers are valid:
+
+```markdown
+9999777788880000
+6666666666661666
+```
+
+And the following credit card numbers are invalid:
+
+```markdown
+a92332119c011112 (invalid characters)
+4444444444444444 (only one type of number)
+1111111111111110 (sum less than 16)
+6666666666666661 (odd final number)
+```
+
+These are the requirements your project needs to fulfill:
+
+- Make a JavaScript file with a name that describes its contents.
+- Create a function with a descriptive name which makes it clear what the function does. The function should take one argument, the credit card number to validate.
+- Write at least 2 comments that explain to others what a line of code is meant to do.
+- Return a boolean from the function to indicate whether the credit card number is valid.
+
+Good luck!
diff --git a/Sprint-3/4-stretch/find.js b/Sprint-3/4-stretch/find.js
index c7e79a2f21..dd7f06a9a2 100644
--- a/Sprint-3/4-stretch/find.js
+++ b/Sprint-3/4-stretch/find.js
@@ -1,25 +1,25 @@
-function find(str, char) {
-  let index = 0;
-
-  while (index < str.length) {
-    if (str[index] === char) {
-      return index;
-    }
-    index++;
-  }
-  return -1;
-}
-
-console.log(find("code your future", "u"));
-console.log(find("code your future", "z"));
-
-// The while loop statement allows us to do iteration - the repetition of a certain number of tasks according to some condition
-// See the docs https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/while
-
-// Use the Python Visualiser to help you play computer with this example and observe how this code is executed
-// Pay particular attention to the following:
-
-// a) How the index variable updates during the call to find
-// b) What is the if statement used to check
-// c) Why is index++ being used?
-// d) What is the condition index < str.length used for?
+function find(str, char) {
+  let index = 0;
+
+  while (index < str.length) {
+    if (str[index] === char) {
+      return index;
+    }
+    index++;
+  }
+  return -1;
+}
+
+console.log(find("code your future", "u"));
+console.log(find("code your future", "z"));
+
+// The while loop statement allows us to do iteration - the repetition of a certain number of tasks according to some condition
+// See the docs https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/while
+
+// Use the Python Visualiser to help you play computer with this example and observe how this code is executed
+// Pay particular attention to the following:
+
+// a) How the index variable updates during the call to find
+// b) What is the if statement used to check
+// c) Why is index++ being used?
+// d) What is the condition index < str.length used for?
diff --git a/Sprint-3/4-stretch/password-validator.js b/Sprint-3/4-stretch/password-validator.js
index b55d527dba..1af3c41c55 100644
--- a/Sprint-3/4-stretch/password-validator.js
+++ b/Sprint-3/4-stretch/password-validator.js
@@ -1,6 +1,6 @@
-function passwordValidator(password) {
-    return password.length < 5 ? false : true
-}
-
-
+function passwordValidator(password) {
+    return password.length < 5 ? false : true
+}
+
+
 module.exports = passwordValidator;
\ No newline at end of file
diff --git a/Sprint-3/4-stretch/password-validator.test.js b/Sprint-3/4-stretch/password-validator.test.js
index 8fa3089d6b..ede1f1f3b8 100644
--- a/Sprint-3/4-stretch/password-validator.test.js
+++ b/Sprint-3/4-stretch/password-validator.test.js
@@ -1,26 +1,26 @@
-/* 
-Password Validation
-
-Write a program that should check if a password is valid
-and returns a boolean
-
-To be valid, a password must:
-- Have at least 5 characters.
-- Have at least one English uppercase letter (A-Z)
-- Have at least one English lowercase letter (a-z)
-- Have at least one number (0-9)
-- Have at least one of the following non-alphanumeric symbols: ("!", "#", "$", "%", ".", "*", "&")
-- Must not be any previous password in the passwords array. 
-
-You must breakdown this problem in order to solve it. Find one test case first and get that working
-*/
-const isValidPassword = require("./password-validator");
-test("password has at least 5 characters", () => {
-    // Arrange
-    const password = "12345";
-    // Act
-    const result = isValidPassword(password);
-    // Assert
-    expect(result).toEqual(true);
-}
+/* 
+Password Validation
+
+Write a program that should check if a password is valid
+and returns a boolean
+
+To be valid, a password must:
+- Have at least 5 characters.
+- Have at least one English uppercase letter (A-Z)
+- Have at least one English lowercase letter (a-z)
+- Have at least one number (0-9)
+- Have at least one of the following non-alphanumeric symbols: ("!", "#", "$", "%", ".", "*", "&")
+- Must not be any previous password in the passwords array. 
+
+You must breakdown this problem in order to solve it. Find one test case first and get that working
+*/
+const isValidPassword = require("./password-validator");
+test("password has at least 5 characters", () => {
+    // Arrange
+    const password = "12345";
+    // Act
+    const result = isValidPassword(password);
+    // Assert
+    expect(result).toEqual(true);
+}
 );
\ No newline at end of file
diff --git a/Sprint-3/readme.md b/Sprint-3/readme.md
index 028950b927..772c0c3865 100644
--- a/Sprint-3/readme.md
+++ b/Sprint-3/readme.md
@@ -1,18 +1,18 @@
-# 🧭 Guide to week 3 exercises
-
-> https://programming.codeyourfuture.io/structuring-data/sprints/3/prep/
-
-> [!TIP]
-> You should always do the prep work _before_ attempting the coursework.
-> The prep shows you how to do the coursework.
-> There is often a step by step video you can code along with too.
-> Do the prep.
-
-This sprint you are expected to produce multiple different pull requests:
-
-1. One pull request for the `1-implement-and-rewrite-tests` directory.
-2. One pull request for the `2-practice-tdd` directory.
-3. One pull request for the `3-dead-code` directory.
-4. Optionally, one pull request for the `4-stretch` directory.
-
-Each directory contains a README.md file with instructions for that directory.
+# 🧭 Guide to week 3 exercises
+
+> https://programming.codeyourfuture.io/structuring-data/sprints/3/prep/
+
+> [!TIP]
+> You should always do the prep work _before_ attempting the coursework.
+> The prep shows you how to do the coursework.
+> There is often a step by step video you can code along with too.
+> Do the prep.
+
+This sprint you are expected to produce multiple different pull requests:
+
+1. One pull request for the `1-implement-and-rewrite-tests` directory.
+2. One pull request for the `2-practice-tdd` directory.
+3. One pull request for the `3-dead-code` directory.
+4. Optionally, one pull request for the `4-stretch` directory.
+
+Each directory contains a README.md file with instructions for that directory.
diff --git a/contributing.md b/contributing.md
index 602c694383..ae6f43d270 100644
--- a/contributing.md
+++ b/contributing.md
@@ -1,19 +1,19 @@
-<!--
-Do not edit this file.
-Make a change to the template and then pull changes
-Repo: https://github.com/CodeYourFuture/Module-Template
--->
-
-# How To Submit Your Coursework
-
-Use Git & Github to submit your coursework as a pull request.
-
-[Creating a pull request](https://curriculum.codeyourfuture.io/guides/create-a-pull-request/)
-
-## Questions & Help
-
-Contributing to a remote codebase is a necessary skill for a professional developer. Opening PRs is mandatory at CYF. It is part of the coursework.
-
-If you cannot submit your coursework you **must** post on Slack to get unblocked.
-
-[How to get help](./HOW-TO-GET-HELP.md)
+<!--
+Do not edit this file.
+Make a change to the template and then pull changes
+Repo: https://github.com/CodeYourFuture/Module-Template
+-->
+
+# How To Submit Your Coursework
+
+Use Git & Github to submit your coursework as a pull request.
+
+[Creating a pull request](https://curriculum.codeyourfuture.io/guides/create-a-pull-request/)
+
+## Questions & Help
+
+Contributing to a remote codebase is a necessary skill for a professional developer. Opening PRs is mandatory at CYF. It is part of the coursework.
+
+If you cannot submit your coursework you **must** post on Slack to get unblocked.
+
+[How to get help](./HOW-TO-GET-HELP.md)
diff --git a/package.json b/package.json
index 0657e22dd8..29e7f537de 100644
--- a/package.json
+++ b/package.json
@@ -1,15 +1,15 @@
-{
-  "name": "module-structuring-and-testing-data",
-  "version": "1.0.0",
-  "description": "Like learning a musical instrument, programming requires daily practice.",
-  "main": "index.js",
-  "scripts": {
-    "test": "jest"
-  },
-  "keywords": [],
-  "author": "Code Your Future",
-  "license": "ISC",
-  "dependencies": {
-    "jest": "^29.7.0"
-  }
+{
+  "name": "module-structuring-and-testing-data",
+  "version": "1.0.0",
+  "description": "Like learning a musical instrument, programming requires daily practice.",
+  "main": "index.js",
+  "scripts": {
+    "test": "jest"
+  },
+  "keywords": [],
+  "author": "Code Your Future",
+  "license": "ISC",
+  "dependencies": {
+    "jest": "^29.7.0"
+  }
 }
\ No newline at end of file
diff --git a/readme.md b/readme.md
index 873178bda5..e6aa31e9da 100644
--- a/readme.md
+++ b/readme.md
@@ -1,29 +1,29 @@
-# Coursework
-
-> https://programming.codeyourfuture.io/structuring-data/
-
-> [!TIP]
-> You should always do the prep work _before_ attempting the coursework.
-> The prep shows you _how_ to do the coursework.
-> There is often a step by step video you can code along with too.
-> Do the prep.
-
-## Setting up your code editor
-
-There are some tools that will help you to write code. One of these, [Prettier](https://prettier.io/), formats your code, making it easier for you and others to read. Another tool, [Jest](https://jestjs.io/), is a test runner that will turn on Test Explorer in Visual Studio Code. 
-
-### 1. Using Prettier, Test Runner, and other recommended tools in Visual Studio Code
-
-- Open this repository in Visual Studio Code
-- Accept the prompt to install the recommended extensions
-
-### 2. Enable formatting on save
-
-- In Visual Studio open the settings file (see https://code.visualstudio.com/docs/getstarted/settings#_creating-user-and-workspace-settings)
-- Search for `editor format`
-- Set `editor.formatOnSave` and `editor.formatOnPaste` to true
-
-### 3. Install the packages for this coursework
-
-- Open the terminal in Visual Studio Code
-- Run `npm install` in the root of this repository
+# Coursework
+
+> https://programming.codeyourfuture.io/structuring-data/
+
+> [!TIP]
+> You should always do the prep work _before_ attempting the coursework.
+> The prep shows you _how_ to do the coursework.
+> There is often a step by step video you can code along with too.
+> Do the prep.
+
+## Setting up your code editor
+
+There are some tools that will help you to write code. One of these, [Prettier](https://prettier.io/), formats your code, making it easier for you and others to read. Another tool, [Jest](https://jestjs.io/), is a test runner that will turn on Test Explorer in Visual Studio Code. 
+
+### 1. Using Prettier, Test Runner, and other recommended tools in Visual Studio Code
+
+- Open this repository in Visual Studio Code
+- Accept the prompt to install the recommended extensions
+
+### 2. Enable formatting on save
+
+- In Visual Studio open the settings file (see https://code.visualstudio.com/docs/getstarted/settings#_creating-user-and-workspace-settings)
+- Search for `editor format`
+- Set `editor.formatOnSave` and `editor.formatOnPaste` to true
+
+### 3. Install the packages for this coursework
+
+- Open the terminal in Visual Studio Code
+- Run `npm install` in the root of this repository