Skip to content

Commit d6a231e

Browse files
authored
docs(start/concepts): fix warning (#10221)
1 parent d19c2c2 commit d6a231e

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

contributors.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -200,3 +200,4 @@
200200
- yionr
201201
- yuleicul
202202
- zheng-chuang
203+
- kno-raziel

docs/start/concepts.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -664,9 +664,7 @@ And the resulting element tree rendered will be:
664664
</PageLayout>
665665
```
666666

667-
<docs-warning>
668-
Don't forget to add an `<Outlet>` to your layout where you would like child route elements to be rendered. Using `children` will not work as expected.
669-
</docs-warning>
667+
<docs-warning>Don't forget to add an `<Outlet>` to your layout where you would like child route elements to be rendered. Using `{children}` will not work as expected.</docs-warning>
670668

671669
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:
672670

0 commit comments

Comments
 (0)