chore: fix typo error

HyunmoAhn · Dec 19, 2024 · 0215d29 · 0215d29
1 parent 1cd0808
commit 0215d29
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/blog/2024-12-16-why-create-server-component-on-react.mdx b/blog/2024-12-16-why-create-server-component-on-react.mdx
@@ -14,7 +14,7 @@ tags: [server-component, server-side-rendering, react, suspense, web]
 
 ## Purpose
 
-[React 18](https://react.dev/blog/2022/03/29/react-v18)이 2022년에 출시되었고, [Nextjs App router](https://nextjs.org/blog/next-13-4)가 2023년에 출시되어 이미 캐캐묵은 조사이지만,
+[React 18](https://react.dev/blog/2022/03/29/react-v18)이 2022년에 출시되었고, [Nextjs App router](https://nextjs.org/blog/next-13-4)가 2023년에 출시되어 이미 케케묵은 조사이지만,
 nextjs page router와 app router를 쓰며 어떤 점이 달라졌고, 왜 달라졌는지 이유를 찾던 중 app router를 왜 사용하게 되었는지 이유를 찾게 된 글이 있다.
 그 글을 읽고 이해한 바를 정리하고자 한다.
 

diff --git a/i18n/en/docusaurus-plugin-content-blog/2021-10-23-deep-dive-to-immer.md b/i18n/en/docusaurus-plugin-content-blog/2021-10-23-deep-dive-to-immer.md
@@ -162,7 +162,7 @@ console.log(nonPrimitive)
 When comparing whether the data is the same, `shallow equality checking` doesn't check whether the inside of the data has changed,
 but rather determines that the reference of the data has changed. If it is the same, it has not changed.
 
-If using `deep eqaulity checking`, we suffer performance losses because all object have to be compared one by one.
+If using `deep equality checking`, we suffer performance losses because all object have to be compared one by one.
 So, when we changed the object, we used immutable data that guarantees that the reference is also changed, 
 and we use `immer` because it guarantees that the object is immutable with any changes.