docs(js): Update stale images on Debug IDs page

includes/debug-ids/index.mdx

@@ -70,7 +70,7 @@ When you upload source maps, Sentry's bundler plugins or Sentry CLI prepare the
 ### Why use Debug IDs to uniminify your code?
 
 <PlatformSection notSupported={["react-native"]}>
-Unminifying your code is essential for effective debugging. While there are other [legacy ways](/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:
+Unminifying your code is essential for effective debugging. While there are other [legacy ways](/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.
 </PlatformSection>
 <PlatformSection supported={["react-native"]}>
 Unminifying your code is essential for effective debugging. While there are other [legacy ways](/platforms/react-native/sourcemaps/troubleshooting/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: