diff --git a/docs/platforms/javascript/common/troubleshooting/index.mdx b/docs/platforms/javascript/common/troubleshooting/index.mdx
index 316e6a60fc5ab5..e47edf6bbb5320 100644
--- a/docs/platforms/javascript/common/troubleshooting/index.mdx
+++ b/docs/platforms/javascript/common/troubleshooting/index.mdx
@@ -8,7 +8,7 @@ keywords:
   - blocked
   - tunnel
   - non-Error exception
-  - '404'
+  - "404"
 notSupported:
   - javascript.capacitor
 sidebar_order: 9000
@@ -524,7 +524,7 @@ When using pnpm, you might encounter errors related to packages that can't be ex
 While adding these packages as direct dependencies might remove the warning messages, it often doesn't resolve the underlying functionality issues:
 
 ```bash
-pnpm add import-in-the-middle require-in-the-middle
+pnpm add import-in-the-middle@1 require-in-the-middle@7
 ```
 
 As a workaround, create or modify `.npmrc` in your project root. First, try to specifically hoist the dependencies in question:
@@ -686,6 +686,7 @@ shamefully-hoist=true
     In case you are using Session Replay and experience performance issues with the client instrumentation hook, you can try lazy-loading session replay as described [here](/platforms/javascript/guides/nextjs/session-replay/#lazy-loading-replay).
 
     If you want to init the SDK itself at a later point, this will result in tracing data losing accuracy and errors could happen before the SDK is initialized. This should be a tradeoff you make based on your use case, although we recommend initializing the SDK as early as possible.
+
   </Expandable>
 </PlatformSection>