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

@@ -17,7 +17,7 @@ To ensure Sentry (and other tools) can provide stack traces that are both readab
 
 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.
 
-`//# source mappingURL=http://example.com/path/to/your/source map.map`
+`//# source mappingURL=http://example.com/path/to/your/source-map.js.map`
 
 Given the url-based filename approach was unreliable, we came up with [Debug IDs](/platforms/javascript/sourcemaps/debug-ids#what-is-a-debug-id).