diff --git a/Sprint-2/1-key-errors/0.js b/Sprint-2/1-key-errors/0.js
deleted file mode 100644
index 653d6f5a0..000000000
--- a/Sprint-2/1-key-errors/0.js
+++ /dev/null
@@ -1,13 +0,0 @@
-// Predict and explain first...
-//  =============> write your prediction here
-
-// call the function capitalise with a string input
-// interpret the error message and figure out why an error is occurring
-
-function capitalise(str) {
-  let str = `${str[0].toUpperCase()}${str.slice(1)}`;
-  return str;
-}
-
-// =============> write your explanation here
-// =============> write your new code here
diff --git a/Sprint-2/1-key-errors/1.js b/Sprint-2/1-key-errors/1.js
deleted file mode 100644
index f2d56151f..000000000
--- a/Sprint-2/1-key-errors/1.js
+++ /dev/null
@@ -1,20 +0,0 @@
-// Predict and explain first...
-
-// Why will an error occur when this program runs?
-// =============> write your prediction here
-
-// Try playing computer with the example to work out what is going on
-
-function convertToPercentage(decimalNumber) {
-  const decimalNumber = 0.5;
-  const percentage = `${decimalNumber * 100}%`;
-
-  return percentage;
-}
-
-console.log(decimalNumber);
-
-// =============> write your explanation here
-
-// Finally, correct the code to fix the problem
-// =============> write your new code here
diff --git a/Sprint-2/1-key-errors/2.js b/Sprint-2/1-key-errors/2.js
deleted file mode 100644
index aad57f7cf..000000000
--- a/Sprint-2/1-key-errors/2.js
+++ /dev/null
@@ -1,20 +0,0 @@
-
-// Predict and explain first BEFORE you run any code...
-
-// this function should square any number but instead we're going to get an error
-
-// =============> write your prediction of the error here
-
-function square(3) {
-    return num * num;
-}
-
-// =============> write the error message here
-
-// =============> explain this error message here
-
-// Finally, correct the code to fix the problem
-
-// =============> write your new code here
-
-
diff --git a/Sprint-2/2-mandatory-debug/0.js b/Sprint-2/2-mandatory-debug/0.js
deleted file mode 100644
index b27511b41..000000000
--- a/Sprint-2/2-mandatory-debug/0.js
+++ /dev/null
@@ -1,14 +0,0 @@
-// Predict and explain first...
-
-// =============> write your prediction here
-
-function multiply(a, b) {
-  console.log(a * b);
-}
-
-console.log(`The result of multiplying 10 and 32 is ${multiply(10, 32)}`);
-
-// =============> write your explanation here
-
-// Finally, correct the code to fix the problem
-//  =============> write your new code here
diff --git a/Sprint-2/2-mandatory-debug/1.js b/Sprint-2/2-mandatory-debug/1.js
deleted file mode 100644
index 37cedfbcf..000000000
--- a/Sprint-2/2-mandatory-debug/1.js
+++ /dev/null
@@ -1,13 +0,0 @@
-// Predict and explain first...
-//  =============> write your prediction here
-
-function sum(a, b) {
-  return;
-  a + b;
-}
-
-console.log(`The sum of 10 and 32 is ${sum(10, 32)}`);
-
-// =============> write your explanation here
-// Finally, correct the code to fix the problem
-//  =============> write your new code here
diff --git a/Sprint-2/2-mandatory-debug/2.js b/Sprint-2/2-mandatory-debug/2.js
deleted file mode 100644
index 57d3f5dc3..000000000
--- a/Sprint-2/2-mandatory-debug/2.js
+++ /dev/null
@@ -1,24 +0,0 @@
-// Predict and explain first...
-
-// Predict the output of the following code:
-// =============> Write your prediction here
-
-const num = 103;
-
-function getLastDigit() {
-  return num.toString().slice(-1);
-}
-
-console.log(`The last digit of 42 is ${getLastDigit(42)}`);
-console.log(`The last digit of 105 is ${getLastDigit(105)}`);
-console.log(`The last digit of 806 is ${getLastDigit(806)}`);
-
-// Now run the code and compare the output to your prediction
-// =============> write the output here
-// Explain why the output is the way it is
-// =============> write your explanation here
-// Finally, correct the code to fix the problem
-// =============> write your new code here
-
-// This program should tell the user the last digit of each number.
-// Explain why getLastDigit is not working properly - correct the problem
diff --git a/Sprint-2/3-mandatory-implement/1-bmi.js b/Sprint-2/3-mandatory-implement/1-bmi.js
deleted file mode 100644
index 17b1cbde1..000000000
--- a/Sprint-2/3-mandatory-implement/1-bmi.js
+++ /dev/null
@@ -1,19 +0,0 @@
-// Below are the steps for how BMI is calculated
-
-// The BMI calculation divides an adult's weight in kilograms (kg) by their height in metres (m) squared.
-
-// For example, if you weigh 70kg (around 11 stone) and are 1.73m (around 5 feet 8 inches) tall, you work out your BMI by:
-
-// squaring your height: 1.73 x 1.73 = 2.99
-// dividing 70 by 2.99 = 23.41
-// Your result will be displayed to 1 decimal place, for example 23.4.
-
-// You will need to implement a function that calculates the BMI of someone based off their weight and height
-
-// Given someone's weight in kg and height in metres
-// Then when we call this function with the weight and height
-// It should return their Body Mass Index to 1 decimal place
-
-function calculateBMI(weight, height) {
-    // return the BMI of someone based off their weight and height
-}
\ No newline at end of file
diff --git a/Sprint-2/3-mandatory-implement/2-cases.js b/Sprint-2/3-mandatory-implement/2-cases.js
deleted file mode 100644
index 5b0ef77ad..000000000
--- a/Sprint-2/3-mandatory-implement/2-cases.js
+++ /dev/null
@@ -1,16 +0,0 @@
-// A set of words can be grouped together in different cases.
-
-// For example, "hello there" in snake case would be written "hello_there"
-// UPPER_SNAKE_CASE means taking a string and writing it in all caps with underscores instead of spaces.
-
-// Implement a function that:
-
-// Given a string input like "hello there"
-// When we call this function with the input string
-// it returns the string in UPPER_SNAKE_CASE, so "HELLO_THERE"
-
-// Another example: "lord of the rings" should be "LORD_OF_THE_RINGS"
-
-// You will need to come up with an appropriate name for the function
-// Use the MDN string documentation to help you find a solution
-// This might help https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/toUpperCase
diff --git a/Sprint-2/3-mandatory-implement/3-to-pounds.js b/Sprint-2/3-mandatory-implement/3-to-pounds.js
deleted file mode 100644
index 6265a1a70..000000000
--- a/Sprint-2/3-mandatory-implement/3-to-pounds.js
+++ /dev/null
@@ -1,6 +0,0 @@
-// In Sprint-1, there is a program written in interpret/to-pounds.js
-
-// You will need to take this code and turn it into a reusable block of code.
-// You will need to declare a function called toPounds with an appropriately named parameter.
-
-// You should call this function a number of times to check it works for different inputs
diff --git a/Sprint-2/4-mandatory-interpret/time-format.js b/Sprint-2/4-mandatory-interpret/time-format.js
deleted file mode 100644
index 7c98eb0e8..000000000
--- a/Sprint-2/4-mandatory-interpret/time-format.js
+++ /dev/null
@@ -1,34 +0,0 @@
-function pad(num) {
-  return num.toString().padStart(2, "0");
-}
-
-function formatTimeDisplay(seconds) {
-  const remainingSeconds = seconds % 60;
-  const totalMinutes = (seconds - remainingSeconds) / 60;
-  const remainingMinutes = totalMinutes % 60;
-  const totalHours = (totalMinutes - remainingMinutes) / 60;
-
-  return `${pad(totalHours)}:${pad(remainingMinutes)}:${pad(remainingSeconds)}`;
-}
-
-// You will need to play computer with this example - use the Python Visualiser https://pythontutor.com/visualize.html#mode=edit
-// to help you answer these questions
-
-// Questions
-
-// a) When formatTimeDisplay is called how many times will pad be called?
-// =============> write your answer here
-
-// Call formatTimeDisplay with an input of 61, now answer the following:
-
-// b) What is the value assigned to num when pad is called for the first time?
-// =============> write your answer here
-
-// c) What is the return value of pad is called for the first time?
-// =============> write your answer here
-
-// d) What is the value assigned to num when pad is called for the last time in this program?  Explain your answer
-// =============> write your answer here
-
-// e) What is the return value assigned to num when pad is called for the last time in this program?  Explain your answer
-// =============> write your answer here
diff --git a/Sprint-2/5-stretch-extend/format-time.js b/Sprint-2/5-stretch-extend/format-time.js
deleted file mode 100644
index 32a32e66b..000000000
--- a/Sprint-2/5-stretch-extend/format-time.js
+++ /dev/null
@@ -1,25 +0,0 @@
-// This is the latest solution to the problem from the prep.
-// Make sure to do the prep before you do the coursework
-// Your task is to write tests for as many different groups of input data or edge cases as you can, and fix any bugs you find.
-
-function formatAs12HourClock(time) {
-  const hours = Number(time.slice(0, 2));
-  if (hours > 12) {
-    return `${hours - 12}:00 pm`;
-  }
-  return `${time} am`;
-}
-
-const currentOutput = formatAs12HourClock("08:00");
-const targetOutput = "08:00 am";
-console.assert(
-  currentOutput === targetOutput,
-  `current output: ${currentOutput}, target output: ${targetOutput}`
-);
-
-const currentOutput2 = formatAs12HourClock("23:00");
-const targetOutput2 = "11:00 pm";
-console.assert(
-  currentOutput2 === targetOutput2,
-  `current output: ${currentOutput2}, target output: ${targetOutput2}`
-);
diff --git a/Sprint-2/readme.md b/Sprint-2/readme.md
deleted file mode 100644
index 44c118e33..000000000
--- a/Sprint-2/readme.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# 🧭 Guide to week 2 exercises
-
-> https://programming.codeyourfuture.io/structuring-data/sprints/2/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.
-
-## 1 Errors
-
-In this section, you need to go to each file in `errors` directory. Read the file and predict what error will happen. Then 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.
-
-## 2 Debug
-
-In this section, you need to go to each file in `debug` to **explain and predict** why the program isn't behaving as intended. Then you'll need to run the program with node to check your prediction. You will also need to correct the code too.
-
-## 3 Implement
-
-In this section, you will have a short set of requirements about a function. You will need to implement a function based off this set of requirements. Make sure you check your function works for a number of different inputs.
-
-Here is a recommended order:
-
-1. `1-bmi.js`
-1. `2-cases.js`
-1. `3-to-pounds.js`
-
-## 4 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.
-
-## 5 Extend
-
-In the prep for this sprint, we developed a function to convert 24 hour clock times to 12 hour clock times.
-
-Your task is to write tests for as many different groups of input data or edge cases as you can, and fix any bugs you find. This section is not mandatory, but it will also help you solve some similar kata in Codewars.
diff --git a/Sprint-3/1-implement-and-rewrite-tests/README.md b/Sprint-3/1-implement-and-rewrite-tests/README.md
deleted file mode 100644
index a65bd2077..000000000
--- a/Sprint-3/1-implement-and-rewrite-tests/README.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# 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 assertions and build up your program case by case. Don't rush to a solution. The point of these assignments is to learn how to write assertions and build up a program step by step.
-
-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
deleted file mode 100644
index 9e05a871e..000000000
--- a/Sprint-3/1-implement-and-rewrite-tests/implement/1-get-angle-type.js
+++ /dev/null
@@ -1,37 +0,0 @@
-// 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");
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
deleted file mode 100644
index 970cb9b64..000000000
--- a/Sprint-3/1-implement-and-rewrite-tests/implement/2-is-proper-fraction.js
+++ /dev/null
@@ -1,33 +0,0 @@
-// 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);
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
deleted file mode 100644
index c7559e787..000000000
--- a/Sprint-3/1-implement-and-rewrite-tests/implement/3-get-card-value.js
+++ /dev/null
@@ -1,52 +0,0 @@
-// 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) {}
-
-// 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
deleted file mode 100644
index d777f348d..000000000
--- a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/1-get-angle-type.test.js
+++ /dev/null
@@ -1,20 +0,0 @@
-// 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
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
deleted file mode 100644
index 7f087b2ba..000000000
--- a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/2-is-proper-fraction.test.js
+++ /dev/null
@@ -1,10 +0,0 @@
-// 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);
-});
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
deleted file mode 100644
index cf7f9dae2..000000000
--- a/Sprint-3/1-implement-and-rewrite-tests/rewrite-tests-with-jest/3-get-card-value.test.js
+++ /dev/null
@@ -1,20 +0,0 @@
-// 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
-
diff --git a/Sprint-3/1-implement-and-rewrite-tests/testing-guide.md b/Sprint-3/1-implement-and-rewrite-tests/testing-guide.md
deleted file mode 100644
index 917194e7a..000000000
--- a/Sprint-3/1-implement-and-rewrite-tests/testing-guide.md
+++ /dev/null
@@ -1,92 +0,0 @@
-# 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
deleted file mode 100644
index f7d82fe43..000000000
--- a/Sprint-3/2-practice-tdd/README.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# 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
deleted file mode 100644
index 95b6ebb7d..000000000
--- a/Sprint-3/2-practice-tdd/count.js
+++ /dev/null
@@ -1,5 +0,0 @@
-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
deleted file mode 100644
index 179ea0ddf..000000000
--- a/Sprint-3/2-practice-tdd/count.test.js
+++ /dev/null
@@ -1,24 +0,0 @@
-// 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
deleted file mode 100644
index f95d71db1..000000000
--- a/Sprint-3/2-practice-tdd/get-ordinal-number.js
+++ /dev/null
@@ -1,5 +0,0 @@
-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
deleted file mode 100644
index adfa58560..000000000
--- a/Sprint-3/2-practice-tdd/get-ordinal-number.test.js
+++ /dev/null
@@ -1,20 +0,0 @@
-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
deleted file mode 100644
index 3838c7b00..000000000
--- a/Sprint-3/2-practice-tdd/repeat-str.js
+++ /dev/null
@@ -1,5 +0,0 @@
-function repeatStr() {
-  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
deleted file mode 100644
index a3fc1196c..000000000
--- a/Sprint-3/2-practice-tdd/repeat-str.test.js
+++ /dev/null
@@ -1,32 +0,0 @@
-// 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
deleted file mode 100644
index 2bfbfff81..000000000
--- a/Sprint-3/3-dead-code/README.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# 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
deleted file mode 100644
index 4d09f15fa..000000000
--- a/Sprint-3/3-dead-code/exercise-1.js
+++ /dev/null
@@ -1,17 +0,0 @@
-// 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
deleted file mode 100644
index 56d7887c4..000000000
--- a/Sprint-3/3-dead-code/exercise-2.js
+++ /dev/null
@@ -1,28 +0,0 @@
-// 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
deleted file mode 100644
index 8f01227bf..000000000
--- a/Sprint-3/4-stretch/README.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# 🔍 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
deleted file mode 100644
index e39c6ace6..000000000
--- a/Sprint-3/4-stretch/card-validator.md
+++ /dev/null
@@ -1,35 +0,0 @@
-## **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
deleted file mode 100644
index c7e79a2f2..000000000
--- a/Sprint-3/4-stretch/find.js
+++ /dev/null
@@ -1,25 +0,0 @@
-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
deleted file mode 100644
index b55d527db..000000000
--- a/Sprint-3/4-stretch/password-validator.js
+++ /dev/null
@@ -1,6 +0,0 @@
-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
deleted file mode 100644
index 8fa3089d6..000000000
--- a/Sprint-3/4-stretch/password-validator.test.js
+++ /dev/null
@@ -1,26 +0,0 @@
-/* 
-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
deleted file mode 100644
index 028950b92..000000000
--- a/Sprint-3/readme.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# 🧭 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.