diff --git a/packages/forms/src/directives/radio_control_value_accessor.ts b/packages/forms/src/directives/radio_control_value_accessor.ts
index 728659bb2a502..217095156cbd0 100644
--- a/packages/forms/src/directives/radio_control_value_accessor.ts
+++ b/packages/forms/src/directives/radio_control_value_accessor.ts
@@ -207,7 +207,7 @@ export class RadioControlValueAccessor extends BuiltInControlValueAccessor imple
      * when an *enabled* control was attached. This bug was fixed in v15 in #47576.
      *
      * This had a side effect: previously, it was possible to instantiate a reactive form control
-     * with `[attr.disabled]=true`, even though the the corresponding control was enabled in the
+     * with `[attr.disabled]=true`, even though the corresponding control was enabled in the
      * model. This resulted in a mismatch between the model and the DOM. Now, because
      * `setDisabledState` is always called, the value in the DOM will be immediately overwritten
      * with the "correct" enabled value.
diff --git a/packages/router/src/router.ts b/packages/router/src/router.ts
index fdbe49e82cd81..1b9d4bb2fccd0 100644
--- a/packages/router/src/router.ts
+++ b/packages/router/src/router.ts
@@ -312,7 +312,7 @@ export class Router {
   private readonly location = inject(Location);
 
   /**
-   * Indicates whether the the application has opted in to binding Router data to component inputs.
+   * Indicates whether the application has opted in to binding Router data to component inputs.
    *
    * This option is enabled by the `withComponentInputBinding` feature of `provideRouter` or
    * `bindToComponentInputs` in the `ExtraOptions` of `RouterModule.forRoot`.