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

@@ -15,7 +15,7 @@ Stack traces are essential to debug errors, but stack traces that come from gene
 
 To ensure Sentry (and other tools) can provide stack traces that are both readable and useful, you'll want to generate and use [source maps](https://firefox-source-docs.mozilla.org/devtools-user/debugger/how_to/use_a_source_map/index.html). Source maps are additional pieces information (often stored as files) that map the transformed JavaScript back to the original code. This allows Sentry to associate the error with your original source, which means you’ll get stack traces that look like the code you wrote, not the code you generated.
 
-To connect source maps to a JavaScript file, we relied on filenames, but these often were unreliable. For example, a new deploy of a source map with the same filename would mean the source mapping gets incorrectly applied.
+To connect source maps to a JavaScript file, we relied on filenames, but these often were unreliable. For example, when you changed the subpath of where your javascript files are served it would mean that the filenames no longer match and the corresponding sourcemap would not be able to be found by Sentry.
 
 `//# source mappingURL=http://example.com/path/to/your/source-map.js.map`