From 46641323e0251eb67ffd619b16e32c74c3dfb708 Mon Sep 17 00:00:00 2001 From: Udoh Jeremiah Date: Tue, 10 Sep 2024 12:39:48 +0100 Subject: [PATCH] docs(file-conventions/root): fix wording (#9947) --- contributors.yml | 1 + docs/file-conventions/root.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/contributors.yml b/contributors.yml index 5a88c93ed6d..2745f9e6715 100644 --- a/contributors.yml +++ b/contributors.yml @@ -655,6 +655,7 @@ - twhitbeck - tylerbrostrom - udasitharani +- udohjeremiah - uerkw - uhoh-itsmaciek - unhackit diff --git a/docs/file-conventions/root.md b/docs/file-conventions/root.md index 29d4fe3a003..60abeffd209 100644 --- a/docs/file-conventions/root.md +++ b/docs/file-conventions/root.md @@ -152,7 +152,7 @@ export function ErrorBoundary() { Because your `Layout` component is used in both success and error flows, this same restriction holds. If you need to fork logic in your `Layout` depending on if it was a successful request or not, you can use `useRouteLoaderData("root")` and `useRouteError()`. -Because your `` component is used for rendering the `ErrorBoundary`, you should be _very defensive_ to ensure that you can render your `ErrorBoundary` without encountering any render errors. If your `Layout` throws another error trying to render the boundary, then it can't can't be used and your UI will fall back to the very minimal built-in default `ErrorBoundary`. +Because your `` component is used for rendering the `ErrorBoundary`, you should be _very defensive_ to ensure that you can render your `ErrorBoundary` without encountering any render errors. If your `Layout` throws another error trying to render the boundary, then it can't be used and your UI will fall back to the very minimal built-in default `ErrorBoundary`. ```tsx filename="app/root.tsx" lines=[6-7,19-29,32-34] export function Layout({