From ce1c15102754a703903bfc4bdc155a7b308dbee6 Mon Sep 17 00:00:00 2001 From: Mandavilli Nikitha Date: Sun, 23 Jun 2019 19:56:33 +0530 Subject: [PATCH] angular routing benefits (#30544) extra stuff about routing in angular --- guide/english/angular/routing/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/english/angular/routing/index.md b/guide/english/angular/routing/index.md index 46191c5cdd..afce60d9e1 100644 --- a/guide/english/angular/routing/index.md +++ b/guide/english/angular/routing/index.md @@ -6,7 +6,7 @@ title: Routing #### Motivation -Routing is essential. Many modern web applications host too much information for one page. Users should not have to scroll through an entire application’s worth of content either. An application needs to split itself into distinguishable sections. +Routing is essential. Many modern web applications host too much information for one page. Users should not have to scroll through an entire application’s worth of content either. An application needs to split itself into distinguishable sections.An Angular best practice is to load and configure the router in a separate, top-level module that is dedicated to routing and imported by the root AppModule. Users prioritize necessary information. Routing helps them find the application section with such information. Any other information useful to other users may exist on an entirely separate route. With routing, both users can find what they need quickly. Irrelevant details stay obscured behind irrelevant routes.