From 18aee608ec2e14a44d3bcb5573c311e0225c9f37 Mon Sep 17 00:00:00 2001 From: sventunus Date: Mon, 29 Jan 2018 02:10:04 +0100 Subject: [PATCH] Update code-splitting.md (#556) Fixed a typo: "A good place **is** to start is with routes" => "A good place to start is with routes" --- content/docs/code-splitting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/code-splitting.md b/content/docs/code-splitting.md index ce0569c5..e0fd0c4e 100644 --- a/content/docs/code-splitting.md +++ b/content/docs/code-splitting.md @@ -157,7 +157,7 @@ Deciding where in your app to introduce code splitting can be a bit tricky. You want to make sure you choose places that will split bundles evenly, but won't disrupt the user experience. -A good place is to start is with routes. Most people on the web are used to +A good place to start is with routes. Most people on the web are used to page transitions taking some amount of time to load. You also tend to be re-rendering the entire page at once so your users are unlikely to be interacting with other elements on the page at the same time.