[docs/korean] Update RecoilRoot docs more natively

[MeganMagic]

Hi, I'm a developer from Korea.
While reading the RecoilRoot documentation, I noticed some sentences in the Korean translation that, while not incorrect, feel slightly unnatural or too literal. These translations can make it harder for developers to intuitively understand the content.

I believe this could lead to confusion for other Korean developers using Recoil.
To address this, I’ve tried to rephrase some sentences to make them sound more natural and easier to understand.

Below, I’ll explain the specific points why the current translation feels unnatural and how I’ve revised them.
If you find my suggestions helpful, I’d be happy to apply similar corrections to other parts of the documentation as well.

Explanation of Changes

1. Plural Forms
   The use of plural forms differs slightly between Korean and English.
   In Korean, plural markers are typically used only in specific situations where emphasizing the plurality is necessary.

   For example, in English, 'I like apples' clearly shows that 'apples' is plural.
   But in Korean, we usually don’t add a plural marker in this context. Instead, we would just say '나는 사과를 좋아해,' using the singular form of 'apple.' From the context, we naturally understand whether it means one apple or many apples.

   Therefore, translating "values" in "Provides the context in which atoms have values" as "값들" (the plural form of "value" in Korean) feels unnatural. I adjusted such instances to better align with natural Korean usage.

2. Overtranslation
   Some commonly used technical terms, such as "atom" and "component", were translated into Korean as "원자" or "구성요소".

   While technically correct, these translations can make it harder for Korean developers to understand, as they are less familiar with these Korean equivalents.

   To address this, I replaced these overly translated terms with their original English counterparts, which are more commonly used and widely understood in the Korean developer community.

3. Sentence Endings
   I modified sentence endings to be more polite and suitable for a guide document.

   While some Recoil documentation already uses polite endings, there are still parts where the style feels rigid or overly literal. Ensuring that sentence endings are consistent and appropriate for the tone of the document makes it more comfortable and easier to read.

Additionally, I noticed that some sentences from the original documentation were missing in the Korean version, so I translated and added them.
I also made corrections to the spacing between words.

Examples of Change

• original sentence
  : 값들을 갖는 원자 컨텍스트를 제공한다. Recoil의 hooks를 사용하는 모든 구성 요소의 조상이어야 한다.
• changed sentence
  : 값을 가진 atom 컨텍스트를 제공합니다. Recoil의 hooks을 사용하는 모든 컴포넌트의 상위 단계(ancestor)로 설정해야 합니다.

Key changes:

• "값들" → "값" (Avoid overuse of plural forms in Korean)
• "원자" → "atom" (Preserve technical term for better understanding)
• Sentence endings adjusted to polite style ("한다" → "합니다")

---

I hope this translation helps Korean developers use Recoil more easily and comfortably.
I'm happy to contribute to improving the documentation for the community, and I’m open to any feedback or suggestions!