fix small bugs in the React course docs

react/modules/tasks/forms.md

@@ -185,7 +185,7 @@ In this task, you will implement form handling using two different approaches: u
   - Usage of _ts-ignore_: **-20 points per each**
   - Presence of _code-smells_ (God-object, chunks of duplicate code), commented code sections: **-10 points per each**
 
-- **2. Test Coverage**
+- **2. Test Coverage (one which applies)**
   - Testing statement coverage below 80% (≥70%): **-10 points**
   - Testing statement coverage below 70% (≥50%): **-30 points**
   - All coverage metrics below 50%: **-50 points**

react/modules/tasks/functional-routing.md

@@ -124,7 +124,7 @@ Focus on routing and functional components.
   - Usage of _ts-ignore_: **-20 points per each**
   - Presence of _code-smells_ (God-object, chunks of duplicate code), commented code sections: **-10 points per each**
 
-- **2. Test Coverage**
+- **2. Test Coverage (one which applies)**
   - Statement coverage below 80% (≥70%): **-10 points**
   - Statement coverage below 70% (≥50%): **-30 points**
   - All coverage metrics below 50%: **-50 points**

react/modules/tasks/performance/performance.md

@@ -19,7 +19,7 @@ In this task, you will optimize a intentionally unoptimized React application th
 - [Chrome](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi)
 - [Firefox](https://addons.mozilla.org/en-US/firefox/addon/react-devtools/)
 
-## Performance Optimization Workflow
+## Performance Optimization Workflow (max 100 points)
 
 For detailed step-by-step instructions on how to profile the application, see the [Profiling Workflow Guide](./profiling-workflow-guide.md).
 

react/modules/tasks/queries.md

@@ -121,7 +121,7 @@ This task is a continuation of the state management task. In this task, you will
   - Usage of _ts-ignore_: **-20 points per each**
   - Presence of _code-smells_ (God-object, chunks of duplicate code), commented code sections: **-10 points per each**
 
-- **2. Test Coverage**
+- **2. Test Coverage (one which applies)**
   - Statement coverage below 80% (≥70%): **-10 points**
   - Statement coverage below 70% (≥50%): **-30 points**
   - All coverage metrics below 50%: **-50 points**

react/modules/tasks/state-management.md

@@ -133,7 +133,7 @@
   - Presence of _code-smells_ (God-object, chunks of duplicate code), commented code sections: **-10 points per each**
   - ESLint or similar static analysis violations (errors, not warnings): **-5 points per violation**
 
-- **2. Test Coverage**
+- **2. Test Coverage (one which applies)**
   - Statement coverage below 80% (≥70%): **-10 points**
   - Statement coverage below 70% (≥50%): **-30 points**
   - All coverage metrics below 50%: **-50 points**

react/modules/tasks/tests.md

@@ -110,6 +110,22 @@ You must use **Jest** or **Vitest** as the test runner and **React Testing Libra
 
 ### Feature 6: User Interactions (**14 points**)
 
+**As a** developer
+**I want** to test all user interactions
+**So that** my components respond correctly
+
+**Scenario:** Test interactions
+
+- **Given** a component with user input
+- **When** the user interacts (clicks, submits, changes input)
+- **Then** the interaction is tested
+
+**Acceptance Criteria:**
+
+- All user interactions (clicks, input changes, form submissions, etc.) are covered by tests.
+- Tests verify that components respond correctly to user actions (e.g., updating state, calling callbacks, rendering changes).
+- Edge cases and invalid inputs are tested to ensure robust handling of user interactions.
+
 ### Feature 7: LocalStorage Functionality Testing (**16 points**)
 
 **As a** developer
@@ -129,22 +145,6 @@ You must use **Jest** or **Vitest** as the test runner and **React Testing Libra
 - Tests cover cases where localStorage is empty, contains a value, or is updated.
 - Tests ensure that localStorage integration does not break component behavior.
 
-**As a** developer
-**I want** to test all user interactions
-**So that** my components respond correctly
-
-**Scenario:** Test interactions
-
-- **Given** a component with user input
-- **When** the user interacts (clicks, submits, changes input)
-- **Then** the interaction is tested
-
-**Acceptance Criteria:**
-
-- All user interactions (clicks, input changes, form submissions, etc.) are covered by tests.
-- Tests verify that components respond correctly to user actions (e.g., updating state, calling callbacks, rendering changes).
-- Edge cases and invalid inputs are tested to ensure robust handling of user interactions.
-
 ## Technical Requirements
 
 1. **Branch Management**: Create a separate branch from "class-components". Branch name: **"unit-testing"**
@@ -188,7 +188,7 @@ You must use **Jest** or **Vitest** as the test runner and **React Testing Libra
 
 ### Penalties
 
-- **Absence of required features from the previous task (`class-components`) results in a penalty equal to the original feature's points:**
+- **0. Absence of required features from the previous task (`class-components`) results in a penalty equal to the original feature's points:**
   - Application Layout Structure: **-5 points**
   - Search Functionality with Local Storage: **-15 points**
   - Search Results Display: **-10 points**
@@ -204,7 +204,7 @@ You must use **Jest** or **Vitest** as the test runner and **React Testing Libra
   - Usage of _ts-ignore_: **-20 points per each**
   - Presence of _code-smells_ (God-object, chunks of duplicate code), commented code sections: **-10 points per each**
 
-- **2. Test Coverage**
+- **2. Test Coverage (one which applies)**
   - Statement coverage below 80% (≥70%): **-10 points**
   - Statement coverage below 70% (≥50%): **-30 points**
   - All coverage metrics below 50%: **-50 points**