diff --git a/blog/2025-10-signal-forms-part1/README.md b/blog/2025-10-signal-forms-part1/README.md
index 9505540c..5a73f2da 100644
--- a/blog/2025-10-signal-forms-part1/README.md
+++ b/blog/2025-10-signal-forms-part1/README.md
@@ -3,7 +3,7 @@ title: "Angular Signal Forms Part 1: Getting Started with the Basics"
 author: Danny Koppenhagen and Ferdinand Malcher
 mail: dannyferdigravatar@fmalcher.de # Gravatar
 published: 2025-10-13
-lastModified: 2025-10-22
+lastModified: 2025-11-09
 keywords:
   - Angular
   - Signals
@@ -164,7 +164,7 @@ Notice, that we also use the form attribute `novalidate`: It disables the native
 We will handle validation later by using a form schema.
 
 ```html
-<form (submit)="submitForm($event)" novalidate>
+<form (submit)="submitForm()" novalidate>
   <div>
     <label for="username">Username</label>
     <input id="username" type="text" [field]="registrationForm.username" />
@@ -258,7 +258,8 @@ Signal Forms provide two approaches for handling form submission:
 Basic synchronous submission and the more powerful `submit()` function for asynchronous operations.
 
 All approaches start with a form submission event handler: In the template, we already used the `(submit)` event binding on the `<form>` element.
-It is always necessary to prevent the default form submission behavior by calling `e.preventDefault()` in our `submitForm()` handler method.
+It is necessary to prevent the default form submission behavior by synchronously returning `false` from our `submitForm()` handler method.
+Otherwise, the page will reload on form submission.
 
 ### Basic Synchronous Submission
 
@@ -268,12 +269,13 @@ For basic cases where you want to process form data synchronously, you can direc
 // ...
 export class RegistrationForm {
   // ...
-  protected submitForm(e: Event) {
-    e.preventDefault();
-
+  protected submitForm() {
     // Access current form data
     const formData = this.registrationModel();
     console.log('Form submitted:', formData);
+
+    // Prevent reloading (default browser behavior)
+    return false;
   }
 }
 ```
@@ -316,14 +318,14 @@ export class RegistrationForm {
   // ...
   readonly #registrationService = inject(RegistrationService);
   // ...
-  protected async submitForm(e: Event) {
-    e.preventDefault();
-
-    await submit(this.registrationForm, async (form) => {
+  protected submitForm() {
+    submit(this.registrationForm, async (form) => {
       await this.#registrationService.registerUser(form().value());
       console.log('Registration successful!');
       this.resetForm();
     });
+
+    return false;
   }
 
   protected resetForm() {
@@ -340,7 +342,7 @@ When submitting the form we can now see that the value of the `submitting()` sig
 After the asynchronous operation is complete, it switches back to `false`.
 
 ```html
-<form (submit)="submitForm($event)">
+<form (submit)="submitForm()">
   <!-- ... -->
 
   <button
diff --git a/blog/2025-10-signal-forms-part2/README.md b/blog/2025-10-signal-forms-part2/README.md
index e9f00b0d..f455bc7e 100644
--- a/blog/2025-10-signal-forms-part2/README.md
+++ b/blog/2025-10-signal-forms-part2/README.md
@@ -3,7 +3,7 @@ title: 'Angular Signal Forms Part 2: Advanced Validation and Schema Patterns'
 author: Danny Koppenhagen and Ferdinand Malcher
 mail: dannyferdigravatar@fmalcher.de # Gravatar
 published: 2025-10-15
-lastModified: 2025-10-30
+lastModified: 2025-11-09
 keywords:
   - Angular
   - Signals
@@ -451,17 +451,15 @@ While client-side validation catches most errors before submission, server-side
 Signal Forms provide an elegant way to handle these errors and display them to users with proper field-level feedback.
 When using the `submit()` function, we can return an array of validation errors from the submission callback to assign them to specific fields or to the form itself.
 
-The helper type `WithField` ensures that each error contains a reference to the field it belongs to.
+The type `ValidationErrorWithField` ensures that each error contains a reference to the field it belongs to.
 
 ```typescript
-import { /* ... */, WithField, ValidationErrorWithField } from '@angular/forms/signals';
+import { /* ... */, ValidationErrorWithField } from '@angular/forms/signals';
 
 export class RegistrationForm {
   // ...
-  protected async submitForm(e: Event) {
-    e.preventDefault();
-
-    await submit(this.registrationForm, async (form) => {
+  protected submitForm() {
+    submit(this.registrationForm, async (form) => {
       const errors: ValidationErrorWithField[] = [];
 
       try {
@@ -490,6 +488,8 @@ export class RegistrationForm {
 
       return errors;
     });
+
+    return false;
   }
 }
 ```
diff --git a/blog/2025-10-signal-forms-part3/README.md b/blog/2025-10-signal-forms-part3/README.md
index 8b0171e1..5a684b18 100644
--- a/blog/2025-10-signal-forms-part3/README.md
+++ b/blog/2025-10-signal-forms-part3/README.md
@@ -3,7 +3,7 @@ title: 'Angular Signal Forms Part 3: Child Forms and Custom UI Controls'
 author: Danny Koppenhagen and Ferdinand Malcher
 mail: dannyferdigravatar@fmalcher.de # Gravatar
 published: 2025-10-20
-lastModified: 2025-10-20
+lastModified: 2025-11-09
 keywords:
   - Angular
   - Signals
@@ -205,7 +205,7 @@ Finally, we integrate the `IdentityForm` component in our main form template.
 To make things work, we pass the `identity` field tree of our main form to the child component via property binding.
 
 ```html
-<form (submit)="submit($event)">
+<form (submit)="submit()">
   <!-- ... -->
   <app-identity-form [identity]="registrationForm.identity" />
   <!-- ... -->