docs: update nextjs documentation

Author: xiaoyu2er

apps/docs/content/en/docs/01-app/01-getting-started/14-deploying.mdx

@@ -43,6 +43,8 @@ Next.js can be deployed to any provider that supports [Docker](https://www.docke
 
 Docker deployments support all Next.js features. Learn how to [configure them](/docs/app/guides/self-hosting) for your infrastructure.
 
+> **Note for development:** While Docker is excellent for production deployments, consider using local development (`npm run dev`) instead of Docker during development on Mac and Windows for better performance. [Learn more about optimizing local development](/docs/app/guides/local-development).
+
 ### Templates
 
 - [Docker](https://github.com/vercel/next.js/tree/canary/examples/with-docker)

apps/docs/content/en/docs/01-app/02-guides/local-development.mdx

@@ -133,6 +133,20 @@ The experimental `serverComponentsHmrCache` option allows you to cache `fetch` r
 
 [Learn more about the experimental option](/docs/app/api-reference/config/next-config-js/serverComponentsHmrCache).
 
+### 8. Consider local development over Docker
+
+If you're using Docker for development on Mac or Windows, you may experience significantly slower performance compared to running Next.js locally.
+
+Docker's filesystem access on Mac and Windows can cause Hot Module Replacement (HMR) to take seconds or even minutes, while the same application runs with fast HMR when developed locally.
+
+This performance difference is due to how Docker handles filesystem operations outside of Linux environments. For the best development experience:
+
+- Use local development (`npm run dev` or `pnpm dev`) instead of Docker during development
+- Reserve Docker for production deployments and testing production builds
+- If you must use Docker for development, consider using Docker on a Linux machine or VM
+
+[Learn more about Docker deployment](/docs/app/getting-started/deploying#docker) for production use.
+
 ## Tools for finding problems
 
 ### Detailed fetch logging