Fix links and dont show in browser

Author: Luca Forstner

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

@@ -77,19 +77,22 @@ Most community CDNs properly set an `Access-Control-Allow-Origin` header.
 
 If your application started to misbehave because of performing additional OPTIONS requests, it is most likely an issue with unwanted `sentry-trace` request headers, which can happen when you are using too generic a configuration for our Tracing Integration in the Browser SDK.
 
-To fix this, change the `tracePropagationTargets` option during SDK initialization. For more details, see [Automatic Instrumentation](/platforms/javascript/tracing/instrumentation/automatic-instrumentation/#tracePropagationTargets) in our Tracing documentation.
+To fix this, change the `tracePropagationTargets` option during SDK initialization. For more details, see <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/#tracePropagationTarget">Automatic Instrumentation</PlatformLink> in our Tracing documentation.
 
 </Expandable>
 </PlatformCategorySection>
 
+<PlatformCategorySection notSupported={['browser']}>
 <Expandable permalink title="Error: 'import-in-the-middle' failed to wrap">
  When using ESM, by default all packages are wrapped under the hood by
  [import-in-the-middle](https://www.npmjs.com/package/import-in-the-middle).
  `import-in-the-middle` has compatibility issues with some packages and
  can throw errors in these situations.
 
- Check out the [ESM troubleshooting section](/platforms/javascript/guides/node/install/esm/#troubleshooting-instrumentation) for more information.
+Check out the <PlatformLink to="/install/esm/#troubleshooting-instrumentation">ESM Troubleshooting Instrumentation</PlatformLink> section for more information.
+
 </Expandable>
+</PlatformCategorySection>
 
 <PlatformCategorySection supported={['browser']}>
 <Expandable permalink title="`instrument.js` Line Numbers for Console Log statements">