Merge pull request #169 from alan2207/fix-docs-links

fix docs links

docs/error-handling.md

@@ -10,7 +10,7 @@ Implement an interceptor to manage errors effectively. This interceptor can be u
 
 Utilize error boundaries in React to handle errors within specific parts of your application. Instead of having only one error boundary for the entire app, consider placing multiple error boundaries in different areas. This way, if an error occurs, it can be contained and managed locally without disrupting the entire application's functionality, ensuring a smoother user experience.
 
-[Error Boundary Example Code](../src/features/discussions/routes/discussion.tsx)
+[Error Boundary Example Code](../src/app/routes/app/discussions/discussion.tsx)
 
 ### Error Tracking
 

docs/performance.md

@@ -6,7 +6,7 @@ Code splitting involves splitting production JavaScript into smaller files to op
 
 Ideally, code splitting should be implemented at the routes level, ensuring that only essential code is loaded initially, with additional parts fetched lazily as needed. It's important to avoid excessive code splitting, as this can lead to a performance decline due to the increased number of requests required to fetch all the code chunks. Strategic code splitting, focusing on critical parts of the application, helps balance performance optimization with efficient resource loading.
 
-[Code Splitting Example Code](../src/routes/index.tsx)
+[Code Splitting Example Code](../src/app/routes/index.tsx)
 
 ### Component and state optimizations
 

docs/state-management.md

@@ -24,7 +24,7 @@ Good Application State Solutions:
 - [jotai](https://github.com/pmndrs/jotai)
 - [xstate](https://xstate.js.org/)
 
-[Global State Example Code](../src/stores/notifications.ts)
+[Global State Example Code](../src/components/ui/notifications/notifications-store.ts)
 
 ## Server Cache State