diff --git a/errors/sharp-missing-in-production.mdx b/errors/sharp-missing-in-production.mdx
index 22b3e1a728..41de0bafce 100644
--- a/errors/sharp-missing-in-production.mdx
+++ b/errors/sharp-missing-in-production.mdx
@@ -36,7 +36,7 @@ bun add sharp
 
 Then, build your project with `next build`. Finally, restart the server with either `next start` for production mode or `node .next/standalone/server.js` for standalone mode.
 
-- If `sharp` is already installed but can't be resolved, set the `NEXT_SHARP_PATH` environment variable such as `export NEXT_SHARP_PATH=/tmp/node_modules/sharp`. Then, build your project with `next build`. Finally, restart the server with either `next start` for production mode or `node server.js` for standalone mode.
+- If `sharp` is already installed but can't be resolved, set the `NEXT_SHARP_PATH` environment variable such as `export NEXT_SHARP_PATH=/tmp/node_modules/sharp`. Then, build your project with `next build`. Finally, restart the server with either `next start` for production mode or `node .next/standalone/server.js` for standalone mode.
 
 > Note: This is not necessary for Vercel deployments, since `sharp` is installed automatically for you.