docs: createContext 미세한 번역 추가 #1332
Merged
Conversation
This file contains hidden or 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
ryungom
requested review from
eomttt,
gnujoow,
hg-pyun and
lumirlumir
as code owners
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Size changes📦 Next.js Bundle Analysis for undefinedThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
이슈번호 : #1327
API > createContext 미세한 번역 추가
다음 세 부분의 번역부분을 손봤습니다. 번역 모범사례를 참고하여 그대로 번역하기보단 보다 자연스럽다고 생각되는 문장으로 의역했습니다. 예를들어 문제해결 파트의 'I can't find~' 부분을 찾을 수 없다라기 보단 모르겠다 등으로... 그리고 provider 소제목 같은 경우(50번째 줄) '.provider'가 사용되지 않는 맥락이더라도 미관상 전체 문장을 백틱으로 감싸는게 좋을것 같아서 소소하게 맺음백틱 위치를 수정했습니다.
필수 확인 사항
textlint가이드Textlint Guide선택 확인 사항