From 85612d800506432dd588a6c1595b4f30201cc7e7 Mon Sep 17 00:00:00 2001 From: Matt Mazzola Date: Sun, 7 Nov 2021 09:57:03 -0800 Subject: [PATCH] style: fix typo in docs (layotus -> layouts) (#8255) --- docs/getting-started/concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/concepts.md b/docs/getting-started/concepts.md index 91910cd4c..c8fb846a5 100644 --- a/docs/getting-started/concepts.md +++ b/docs/getting-started/concepts.md @@ -662,7 +662,7 @@ And the resulting element tree rendered will be: ``` -The `PageLayout` route is admittedly weird. We call it a [layout route](#layout-route) because it doesn't participate in the matching at all (though its children do). It only exists to make wrapping multiple child routes in the same layout simpler. If we didn't allow this then you'd have to handle layotus in two different ways: sometimes your routes do it for you, sometimes you do it manually with lots of layout component repetition throughout your app: +The `PageLayout` route is admittedly weird. We call it a [layout route](#layout-route) because it doesn't participate in the matching at all (though its children do). It only exists to make wrapping multiple child routes in the same layout simpler. If we didn't allow this then you'd have to handle layouts in two different ways: sometimes your routes do it for you, sometimes you do it manually with lots of layout component repetition throughout your app: You can do it like this, but we recommend using a layout route