From 665627e254396b052cd4a726729c47dbc3061086 Mon Sep 17 00:00:00 2001 From: Siddharth Ajmera Date: Wed, 17 Oct 2018 16:02:47 +0530 Subject: [PATCH] fix(aio): add relative to app level routes section (#26504) Added word *relative* to the **Routes at the app level** section description. This was not specified before. The routes in the *lazy-loading-ngmodules/src/app/app-routing.module.ts* also had `loadChildren` values starting with `app/...`. The code for `app-routing.module.ts` is already fixed in [this commit](https://github.com/angular/angular/commit/67ad9468d35fee9e0b0f829d18d01eafda251f1e) PR Close #26504 --- aio/content/guide/lazy-loading-ngmodules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/lazy-loading-ngmodules.md b/aio/content/guide/lazy-loading-ngmodules.md index 5ae596678c..cdd4b00d1c 100644 --- a/aio/content/guide/lazy-loading-ngmodules.md +++ b/aio/content/guide/lazy-loading-ngmodules.md @@ -143,7 +143,7 @@ In `AppRoutingModule`, update the `routes` array with the following: -The import statements stay the same. The first two paths are the routes to the `CustomersModule` and the `OrdersModule` respectively. Notice that the lazy loading syntax uses `loadChildren` followed by a string that is the path to the module, a hash mark or `#`, and the module’s class name. +The import statements stay the same. The first two paths are the routes to the `CustomersModule` and the `OrdersModule` respectively. Notice that the lazy loading syntax uses `loadChildren` followed by a string that is the relative path to the module, a hash mark or `#`, and the module’s class name. ### Inside the feature module