docs: Fix element tree structure for layout route example (#9025)

* docs: Fix element tree structure * Update docs/getting-started/concepts.md Co-authored-by: Tim Dorr <timdorr@users.noreply.github.com>
remix-run · Jun 30, 2022 · a53f9a7 · a53f9a7
1 parent 3610756
commit a53f9a7
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 5 deletions.
diff --git a/contributors.yml b/contributors.yml
@@ -70,3 +70,4 @@
 - vijaypushkin
 - vikingviolinist
 - xcsnowcity
+- gowthamvbhat
diff --git a/docs/getting-started/concepts.md b/docs/getting-started/concepts.md
@@ -657,11 +657,9 @@ Here's a part of our route config we haven't matched yet: `/privacy`. Let's look
 And the resulting element tree rendered will be:
 
 ```jsx
-<App>
-  <PageLayout>
-    <Privacy />
-  </PageLayout>
-</App>
+<PageLayout>
+  <Privacy />
+</PageLayout>
 ```
 
 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: