Update docs/platforms/javascript/common/sourcemaps/troubleshooting_js/debug-ids/index.mdx

Co-authored-by: Luca Forstner <[email protected]>

Author: priscilawebdev

docs/platforms/javascript/common/sourcemaps/troubleshooting_js/debug-ids/index.mdx

@@ -51,7 +51,7 @@ To use Debug IDs, you need **version 7.47** or higher of one of our [JavaScript
 
 ### Why use Debug IDs to uniminify your code?
 
-Unminifying your code is essential for effective debugging. While there are other [legacy ways](https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/legacy-uploading-methods/) to achieve this at Sentry, using **Debug IDs are recommended by Sentry** as it is the most reliable and deterministic method. By unminifying your code, you get much clearer stack traces when errors occur. Instead of seeing obfuscated code, you'll see the exact code you originally wrote, making it far easier to understand and resolve issues. Below are examples that demonstrates the difference:
+Unminifying your code is essential for effective debugging. While there are other [legacy ways](https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/legacy-uploading-methods/) to achieve this at Sentry, using **Debug IDs are recommended by Sentry** as it is the most reliable method. By unminifying your code, you get much clearer stack traces when errors occur. Instead of seeing obfuscated code, you'll see the exact code you originally wrote, making it far easier to understand and resolve issues. Below are examples that demonstrates the difference:
 
 #### Bad Stack Trace
 ![bad stack trace example](./img/bad-stack-trace.png)