Docs(suspense): fix awkward translation in <Suspense> #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
C17AN
changed the title
C17AN
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Problem
If no async dependencies were encountered during the initial render,
<Suspense>will directly go into a resolved state.해당 문장은 '
<Suspense>는 프라미스가 pending -> fulfilled 상태로 전환될 때까지 기다려야 하지만, 프라미스가 존재하지 않으면 곧바로resolved상태가 된다.' 는 맥락으로 작성되었을 것이라 생각합니다.따라서
will directly go into는 '직접 ~ 가 된다' 는 문장보다 '곧바로 ~가 된다' (또는 '즉시 ~가 된다') 는 번역이 적절할 것 같아 제안드립니다. 🙇♂️