Merge branch 'master' of github.com:angular-checklist/angular-checkli…

…st into i18n-step1-content-multiple-languages

content/en-US/architecture/provide-shared-services-on-root-level.md

@@ -10,7 +10,7 @@ Working with a shared module is quite common and recommended. This module can be
 
 # Solution
 
-When creating a `SharedModule`, we want to import the components in all feature modules but only only provide the services in our root module, for instance `AppModule`. We can accomplish this by leveraging the `forRoot` convention. Here's what our `SharedModule` would look like this:
+When creating a `SharedModule`, we want to import the components in all feature modules but only provide the services in our root module, for instance `AppModule`. We can accomplish this by leveraging the `forRoot` convention. Here's what our `SharedModule` would look like this:
 
 ```ts
 @NgModule({

content/en-US/router/lazy-load-feature-modules.md

@@ -41,7 +41,10 @@ This means that the `UsersModule` will be added to the main bundle. The main bun
 // app.routing.ts
 const routes: Routes = [
   ...
-  {path: 'users', loadChildren: '../users/usersModule#UserModule'}
+  {
+    path: 'users',
+    loadChildren: () => import('../users/usersModule').then(m => m.UsersModule)
+  }
   ...
 ];
 
@@ -57,7 +60,8 @@ const routes: Routes = [
 export class AppModule {}
 ```
 
-We updated the `/users` route to use the `loadChildren` property. This points to the module file of the `UsersModule` and always has a fixed format: `${pathToModule}#${nameOfTheModule}`.
+We updated the `/users` route to use the `loadChildren` property. This uses the standard dynamic import syntax.
+Called as a function, the import returns a promise which loads the module.
 
 Also note that we no longer add the `UsersModule` to the imports of the `AppModule`. This is important because otherwise lazy loading wouldn't work as expected. If the `UsersModule` was referenced by the `AppModule` the code for that module would be added to the main bundle.