Fix typo: "server-only" to "client-only" (#6164)

This commit is contained in:
Soichiro Miki
2023-07-25 09:57:55 +09:00
committed by GitHub
parent d86cfc4763
commit cf4ad1999a

View File

@@ -2513,7 +2513,7 @@ However, now imagine you're navigating between two different user profiles. In t
---
### Providing a fallback for server errors and server-only content {/*providing-a-fallback-for-server-errors-and-server-only-content*/}
### Providing a fallback for server errors and client-only content {/*providing-a-fallback-for-server-errors-and-client-only-content*/}
If you use one of the [streaming server rendering APIs](/reference/react-dom/server) (or a framework that relies on them), React will also use your `<Suspense>` boundaries to handle errors on the server. If a component throws an error on the server, React will not abort the server render. Instead, it will find the closest `<Suspense>` component above it and include its fallback (such as a spinner) into the generated server HTML. The user will see a spinner at first.