Update docs/platforms/javascript/common/troubleshooting/index.mdx

Co-authored-by: Alex Krawiec <[email protected]>

Author: chargome

docs/platforms/javascript/common/troubleshooting/index.mdx

@@ -550,7 +550,7 @@ shamefully-hoist=true
 
 <PlatformSection supported={['javascript.nextjs']}>
   <Expandable permalink title="Out of Memory (OOM) errors during build">
-    The problem is related to memory consumption during the build process, especially when generating source maps. Here are some potential solutions and workarounds:
+    The problem here is related to memory consumption during the build process, especially when generating source maps. Here are some potential solutions and workarounds:
     
     - Update your `@sentry/nextjs` package to the latest version.
     - Increase Node.js memory limit: You can try increasing the memory limit for Node.js during the build process. Add this to your build command: `NODE_OPTIONS="--max-old-space-size=8192" next build`. This flag will increase the memory available to the node process to 8 GB. We have found that Next.js consumes around 4 GB in most cases. Decrease the size depending on your memory availability.