Fix typos

Author: Ocunidee

docs/src/first-steps/README.md

@@ -226,7 +226,7 @@ This folder structure is best suited to simple projects with only one main featu
 ![Multi feature folder structure](../assets/folder-structure-multi-module.png)
 
 :::tip
-By default, the CLI will always generate in the `app` folder. You can tell it to generate in another folder by passing the path before the name of the element you want it to generate. For instance `ng generate component components/dashobard` will generate the `DashboardComponent` 4 files in `app/components/dashboard`. The `components` folder is created by the CLI if it doesn't already exist, as well as the `dashboard` folder.
+By default, the CLI will always generate in the `app` folder. You can tell it to generate in another folder by passing the path before the name of the element you want it to generate. For instance `ng generate component components/dashboard` will generate the `DashboardComponent` 4 files in `app/components/dashboard`. The `components` folder is created by the CLI if it doesn't already exist, as well as the `dashboard` folder.
 :::
 
 As the complexity of the folder structure of the application increases, it is a good practice to add aliases in the `tsconfig.json` file. Let's do it now to avoid a tedious refactoring later:

docs/src/fr/html/README.md

@@ -204,10 +204,11 @@ La directive `ngModel` vous permet de lier la valeur d'un champ de formulaire à
 
 ```ts
 import { Component } from '@angular/core'
+import { FormsModule } from '@angular/forms'
 
 @Component({
   selector: 'app-root',
-  imports: [],
+  imports: [FormsModule],
   templateUrl: './app.component.html',
   styleUrl: './app.component.scss'
 })
@@ -379,17 +380,17 @@ Un bloc optionnel `@empty` peut être inclus juste après le bloc `@for`. Le con
 À l'intérieur du bloc `@for`, plusieurs variables contextuelles implicites sont toujours disponibles : `$count`, `$index`, `$first`, `$last`, `$odd` et `$even`. Elles peuvent être renommées via un segment `let`, ce qui peut être utile en cas d'utilisation de boucles `@for` imbriquées où les noms des variables contextuelles pourraient entrer en collision.
 
 ```html
-@for (item of items) {
-  <div>{{$item}}/{{$count}}: {{item.name}}</div>
+@for (item of items; track item.id) {
+  <div>{{$index}}/{{$count}}: {{item.name}}</div>
 }
 
-<!-- Avec un alian pour $index -->
-@for (item of items; let i = $index) {
+<!-- Avec un alias pour $index -->
+@for (item of items; track item.id; let i = $index) {
   <div>{{i}}: {{item.name}}</div>
 }
 
 <!-- Avec un alias pour $even -->
-@for (item of items; let isEven = $even) {
+@for (item of items; track item.id; let isEven = $even) {
   <div>{{item.name}} is {{isEven ? 'even': 'odd'}}</div>
 }
 ```

docs/src/html/README.md

@@ -185,7 +185,7 @@ export class AppComponent {
 
 ## NgModel directive
 
-The ngModel directive allows you to bind the value of a form field to a component class variable. It is a two-way binding: the variable is updated when the content of the field changes (typically by the user) and vice versa. The syntax for two-way data binding is `[()]` (banana the box).
+The ngModel directive allows you to bind the value of a form field to a component class variable. It is a two-way binding: the variable is updated when the content of the field changes (typically by the user) and vice versa. The syntax for two-way data binding is `[()]` (banana in the box).
 
 <CodeGroup>
 <CodeGroupItem title="app.component.html">
@@ -203,10 +203,11 @@ The ngModel directive allows you to bind the value of a form field to a componen
 
 ```ts
 import { Component } from '@angular/core'
+import { FormsModule } from '@angular/forms'
 
 @Component({
   selector: 'app-root',
-  imports: [],
+  imports: [FormsModule],
   templateUrl: './app.component.html',
   styleUrl: './app.component.scss'
 })
@@ -377,17 +378,17 @@ An optional `@empty` block can be included right after the `@for` block. The con
 Inside the `@for` block, several implicit contextual variables are always available: `$count`, `$index`, `$first`, `$last`, `$odd` and `$even`. They can be aliased via a `let` segment which can be useful in case of using nested `@for` loops where contextual variable names could collide.
 
 ```html
-@for (item of items) {
-  <div>{{$item}}/{{$count}}: {{item.name}}</div>
+@for (item of items; track item.id) {
+  <div>{{$index}}/{{$count}}: {{item.name}}</div>
 }
 
 <!-- With an alias for $index -->
-@for (item of items; let i = $index) {
+@for (item of items; track item.id; let i = $index) {
   <div>{{i}}: {{item.name}}</div>
 }
 
 <!-- With an alias for $even -->
-@for (item of items; let isEven = $even) {
+@for (item of items; track item.id; let isEven = $even) {
   <div>{{item.name}} is {{isEven ? 'even': 'odd'}}</div>
 }
 ```