fix: link

Author: hg-pyun

src/content/blog/2025/10/01/react-19-2.md

@@ -96,7 +96,7 @@ function ChatRoom({ roomId, theme }) {
   // ...
 ```
 
-Similar to DOM events, Effect Events always “see” the latest props and state.
+Similar to DOM events, Effect Events always "see" the latest props and state.
 
 **Effect Events should _not_ be declared in the dependency array**. You'll need to upgrade to `eslint-plugin-react-hooks@latest` so that the linter doesn't try to insert them as dependencies. Note that Effect Events can only be declared in the same component or Hook as "their" Effect. These restrictions are verified by the linter.
 

src/content/learn/react-compiler/debugging.md

@@ -90,4 +90,4 @@ If you believe you've found a compiler bug:
 ## Next Steps {/*next-steps*/}
 
 - Review the [Rules of React](/reference/rules) to prevent issues
-- Check the [incremental adoption guide](/learn/react-compiler/incremental-adoption) for gradual rollout strategies
+- Check the [incremental adoption guide](/learn/react-compiler/incremental-adoption) for gradual rollout strategies

src/content/learn/react-compiler/incremental-adoption.md

@@ -222,4 +222,4 @@ If you encounter issues during adoption:
 
 - Read the [configuration guide](/reference/react-compiler/configuration) for more options
 - Learn about [debugging techniques](/learn/react-compiler/debugging)
-- Check the [API reference](/reference/react-compiler/configuration) for all compiler options
+- Check the [API reference](/reference/react-compiler/configuration) for all compiler options

src/content/reference/eslint-plugin-react-hooks/index.md

@@ -37,4 +37,4 @@ These rules are included in the `recommended` preset in `eslint-plugin-react-hoo
 * [`set-state-in-render`](/reference/eslint-plugin-react-hooks/lints/set-state-in-render) - Validates against setting state during render
 * [`static-components`](/reference/eslint-plugin-react-hooks/lints/static-components) - Validates that components are static, not recreated every render
 * [`unsupported-syntax`](/reference/eslint-plugin-react-hooks/lints/unsupported-syntax) - Validates against syntax that React Compiler does not support
-* [`use-memo`](/reference/eslint-plugin-react-hooks/lints/use-memo) - Validates usage of the `useMemo` hook without a return value
+* [`use-memo`](/reference/eslint-plugin-react-hooks/lints/use-memo) - Validates usage of the `useMemo` hook without a return value

src/content/reference/eslint-plugin-react-hooks/lints/error-boundaries.md

@@ -69,4 +69,5 @@ function App() {
     </ErrorBoundary>
   );
 }
-```
+
+```

src/content/reference/eslint-plugin-react-hooks/lints/immutability.md

@@ -158,4 +158,5 @@ function UserProfile() {
     });
   };
 }
-```
+
+```

src/content/reference/eslint-plugin-react-hooks/lints/preserve-manual-memoization.md

@@ -90,4 +90,4 @@ function Component({items, sortBy}) {
 
   return <List items={sorted} />;
 }
-```
+```

src/content/reference/eslint-plugin-react-hooks/lints/purity.md

@@ -80,4 +80,4 @@ function Clock() {
 
   return <div>Current time: {time}</div>;
 }
-```
+```

src/content/reference/eslint-plugin-react-hooks/lints/static-components.md

@@ -100,4 +100,4 @@ function Parent() {
 
 If you find yourself wanting to define components inside other components to access local variables, that's a sign you should be passing props instead. This makes components more reusable and testable.
 
-</Note>
+</Note>

src/content/reference/eslint-plugin-react-hooks/lints/unsupported-syntax.md

@@ -99,4 +99,4 @@ function Calculator({expression}) {
 
 Never use `eval` with user input - it's a security risk. Use dedicated parsing libraries for specific use cases like mathematical expressions, JSON parsing, or template evaluation.
 
-</Note>
+</Note>