diff --git a/adev/src/content/guide/ngmodules/bootstrapping.md b/adev/src/content/guide/ngmodules/bootstrapping.md
index 8e046926090..88ec24ecd01 100644
--- a/adev/src/content/guide/ngmodules/bootstrapping.md
+++ b/adev/src/content/guide/ngmodules/bootstrapping.md
@@ -42,7 +42,7 @@ The module's `declarations` array tells Angular which components belong to that
 As you create more components, add them to `declarations`.
 
 The `declarations` array only takes declarables.
-Declarables are [components](/components), [directives](/directives), and [pipes](/guide/pipes).
+Declarables are [components](/guide/components), [directives](/guide/directives), and [pipes](/guide/pipes).
 All of a module's declarables must be in the `declarations` array.
 Declarables must belong to exactly one module.
 The compiler returns an error if declare the same class in multiple modules.
@@ -103,7 +103,7 @@ And in the same file, add it to the `@NgModule` `declarations` array:
 Now you can use `ItemDirective` in a component.
 This example uses `AppModule`, but you would follow the same steps for a feature module.
 For more about directives, see [Attribute Directives](/guide/directives/attribute-directives) and [Structural Directives](/guide/directives/structural-directives).
-You'd also use the same technique for [pipes](/guide/pipes) and [components](/components).
+You'd also use the same technique for [pipes](/guide/pipes) and [components](/guide/components).
 
 Remember, components, directives, and pipes belong to one module only.
 You only need to declare them once in your application because you share them by importing the necessary modules.
diff --git a/adev/src/content/guide/templates/two-way-binding.md b/adev/src/content/guide/templates/two-way-binding.md
index fd6007c3a59..eb65379a379 100644
--- a/adev/src/content/guide/templates/two-way-binding.md
+++ b/adev/src/content/guide/templates/two-way-binding.md
@@ -59,6 +59,6 @@ Angular assigns the `$event` value to the `AppComponent.fontSizePx` when the use
 <docs-callout title="Two-way binding in forms">
 
 Because no built-in HTML element follows the `x` value and `xChange` event pattern, two-way binding with form elements requires `NgModel`.
-For more information on how to use two-way binding in forms, see Angular [NgModel](guide/directives#ngModel).
+For more information on how to use two-way binding in forms, see Angular [NgModel](guide/directives#displaying-and-updating-properties-with-ngmodel).
 
 </docs-callout>