Apply suggestions from Copilot code review

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: ebouchut

CODE_OF_CONDUCT.md

@@ -50,7 +50,7 @@ We agree to restrict the following behaviors in our community. Instances, threat
 
 Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
 
-When an incident does occur, it is important to report it promptly. To report a possible violation, **send an email to ebouchut@gmail.com .**
+When an incident does occur, it is important to report it promptly. To report a possible violation, **send an email to ebouchut@gmail.com.**
 
 Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
 

CONTRIBUTING.md

@@ -83,7 +83,7 @@ sequenceDiagram
 
     FE->>API: POST /auth/login<br/>{ email, password }
 
-    API->>API: Validate request body (Joi)
+    API->>API: Validate request body (server-side validation)
     alt Validation fails
         API-->>FE: 400 Bad Request<br/>{ message: [...errors] }
         FE-->>U: Show validation errors
@@ -115,20 +115,20 @@ We use a **monorepo**, that is a Git repository containing mainly both the **fro
 **Using a monorepo offers the following advantages:**
 
 - **Shared code and types:**  
-  The *frontend* and *backend* can share types from a single source of truth, avoiding duplication and keeping 
-- them in sync.
+  The *frontend* and *backend* can share types from a single source of truth, avoiding duplication and keeping them in sync.
 - **Atomic changes:**  
-  A single commit or PR can update the database schema, backend API, and frontend together, 
-- ensuring they stay compatible.
+  A single commit or PR can update the database schema, backend API, and frontend together, ensuring they stay compatible.
 - **Easier code reviews:**  
-  Reviewers can see the full picture of a change (database + backend + frontend) in a single PR 
-- rather than coordinating across multiple repositories.
+  Reviewers can see the full picture of a change (database + backend + frontend) in a single PR rather than coordinating across multiple repositories.
 - **Consistent tooling and configuration:**    
   Linting rules, formatting, CI/CD pipelines, and Git hooks are configured once and apply to all packages.
 
+
+
+
 #### Modules
 
-The project is composed of 2 `modules:
+The project is composed of 2 modules:
 
 - **`backend`**:  Spring Boot app (in `backend/`) 
 - **`frontend`**: React app (in `frontend`).  
@@ -397,7 +397,7 @@ The *learn-dev* platform uses a PostgreSQL relational database to persist entiti
 
 ##### Database Naming Conventions
 
-Here are the naming conventions for the **name** of our database **tables**:T
+Here are the naming conventions for the **name** of our database **tables**:
 
 - All lowercase
 - Plural
@@ -410,7 +410,7 @@ Do not use an underscore as the first character.
 ##### Database ERD Diagram
 
 The **Entity Relationships Diagram** (ERD) 
-is available as an [SVG image](https://raw.githubusercontent.com/ebouchut/learn)dev/dev/docs/ERD.svg)
+is available as an [SVG image](https://raw.githubusercontent.com/ebouchut/learn-dev/dev/docs/ERD.svg)
 
 > [!NOTE]
 > This diagram uses [Crows's foot notation](https://mermaid.js.org/syntax/entityRelationshipDiagram.html#relationship-syntax)
@@ -463,12 +463,12 @@ send requests to the backend API directly from [Postman](https://www.postman.com
 
 1. Open Postman.
 2. Click **`Collections`** / **`Import`**.
-3. Select `packages/backend/postman/learndev.collection.json`.
+3. Select `backend/postman/learndev.collection.json`.
 
 #### Import the Postman environment
 
 1. Click **`Environments`** / **`Import`**.
-2. Select `packages/backend/postman/learndev.environment.json`.
+2. Select `backend/postman/learndev.environment.json`.
 3. Select **learnDev – Local** as the active environment (top-right dropdown).
 
 #### Configure the Postman Collection
@@ -721,9 +721,9 @@ to the **frontend**:
 
 ```shell
 cd frontend
-# IMPORTANT: first off run npm
-# Run npm (one-shot) to install the existing project's dependencies
-npm   
+# IMPORTANT: first install dependencies with npm
+# Run npm install (one-shot) to install the existing project's dependencies
+npm install
 
 npm install react react-dom
 npm install -D @types/react

README.md

@@ -1,4 +1,4 @@
-# Learn-dev an Interactive Programming Learning Platform
+# Learn-dev: An Interactive Programming Learning Platform
 
 ## Presentation
 
@@ -28,8 +28,7 @@ and [React](https://react.dev/) frontend.
 ### Backend
 
 - Java 21 
-- [Spring Boot](https://spring.io/projects/spring-boot) 3.x: Java Framework used to build (Web) Applications.
-    and REST endpoints
+- [Spring Boot](https://spring.io/projects/spring-boot) 3.x: Java Framework used to build (Web) Applications and REST endpoints.
 - [Spring Security](https://spring.io/projects/spring-security): Authentication and authorization framework
 - [PostgreSQL](https://www.postgresql.org/about/) 15+: Database
 - [Maven](https://maven.apache.org/what-is-maven.html): Build and dependency management tool