Add npm link to node-core

Author: andreiborza

docs/platforms/javascript/common/migration/v9-to-v10.mdx

@@ -29,7 +29,7 @@ Version 10 of the Sentry SDK has new compatibility ranges for runtimes and frame
 
 All OpenTelemetry dependencies have been bumped to `2.x.x` / `0.20x.x` respectively and all OpenTelemetry instrumentations have been upgraded to their latest version.
 
-If you cannot run with OpenTelmetry v2 versions, consider either staying on Version 9 of our SDKs or using `@sentry/node-core` instead, which ships with widened OpenTelemetry peer dependencies.
+If you cannot run with OpenTelmetry v2 versions, consider either staying on Version 9 of our SDKs or using [@sentry/node-core](https://www.npmjs.com/package/@sentry/node-core) instead, which ships with widened OpenTelemetry peer dependencies.
 
 ### AWS Lambda Layer Changes
 
@@ -49,9 +49,9 @@ Sentry now follows Google's lead by also removing it.
 
 The removal entails **no breaking API changes**. However, in rare cases, you might need to adjust some of your Sentry SDK and product setup:
 
-  - Remove any logic in `beforeSend` or other filtering/event processing logic that depends on FID or replace it with INP logic.
-  - If you set up Sentry Alerts that depend on FID, be aware that these could trigger once you upgrade the SDK, due to a lack of new values.
-    To replace them, adjust your alerts (or dashbaords) to use INP.
+- Remove any logic in `beforeSend` or other filtering/event processing logic that depends on FID or replace it with INP logic.
+- If you set up Sentry Alerts that depend on FID, be aware that these could trigger once you upgrade the SDK, due to a lack of new values.
+  To replace them, adjust your alerts (or dashbaords) to use INP.
 
 </PlatformCategorySection>