diff --git a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx
index 1e198d189a1bb..5532da0544032 100644
--- a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx
+++ b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx
@@ -239,7 +239,11 @@ Sometimes build scripts and plugins produce pre-compressed minified files (for e
 
 If you're <PlatformLink to="/sourcemaps/uploading/hosting-publicly/">hosting your source maps publicly</PlatformLink>, make sure you have the "Enable JavaScript source fetching" option activated under **[Settings] > Projects > Select your project > General Settings**.
 
-## Verify workers are sharing the same volume as web (if running self-hosted Sentry via Docker)
+## (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally
+
+If you're running a self-hosted version of Sentry, you can verify that the `symbolicator` service/container is operating normally by checking the container's logs.
+
+## (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web
 
 Sentry does source map calculation in its workers. This means the workers need access to the files uploaded through the front end. Double check that the cron workers and web workers can read/write files from the same disk.
 
diff --git a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
index 0dea289bd824f..02e4c0f7d8b9d 100644
--- a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
+++ b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
@@ -73,8 +73,8 @@ export default defineConfig({
   ],
 });
 ```
-</PlatformSection>
 
+</PlatformSection>
 
 ## Uploading using Sentry Webpack Plugin Version 1.x
 
@@ -82,7 +82,6 @@ Assuming you have the `@sentry/webpack` package installed on version `1.x`, you
 
 Example:
 
-
 ```javascript {filename:webpack.config.js}
 const SentryWebpackPlugin = require("@sentry/webpack-plugin");
 
@@ -111,7 +110,6 @@ module.exports = {
 
 The Sentry webpack plugin will automatically inject a release value into the SDK so you must either omit the `release` option from `Sentry.init` or make sure `Sentry.init`'s `release` option matches the plugin's `release` option exactly:
 
-
 ```javascript
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
@@ -136,7 +134,6 @@ This applies when using the following packages on version `2.x` and above:
 
 Example of using the `release.uploadLegacySourcemaps` option:
 
-
 ```javascript {filename:webpack.config.js} {tabTitle:Webpack}
 const { sentryWebpackPlugin } = require("@sentry/webpack-plugin");
 
@@ -251,7 +248,6 @@ export default {
 
 The Sentry bundler plugins will automatically inject a release value into the SDK so you must either omit the `release` option from `Sentry.init` or make sure `Sentry.init`'s `release` option matches the plugin's `release.name` option exactly:
 
-
 ```javascript
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
@@ -506,7 +502,11 @@ If you are using `sentry-cli` to upload your artifacts, starting with version `2
 
 Sometimes build scripts and plugins produce pre-compressed minified files (for example, webpack's [compression plugin](https://github.com/webpack/compression-webpack-plugin)). In these cases, you'll need to disable such plugins and perform the compression **after** the generated source maps/source files have been uploaded to Sentry.
 
-### Verify workers are sharing the same volume as web (if running self-hosted Sentry via Docker)
+### (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally
+
+If you're running a self-hosted version of Sentry, you can verify that the `symbolicator` service/container is operating normally by checking the container's logs.
+
+### (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web
 
 Sentry does source map calculation in its workers. This means the workers need access to the files uploaded through the front end. Double check that the cron workers and web workers can read/write files from the same disk.
 
diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx
index 9e44e55413939..d3ea061c16359 100644
--- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx
+++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx
@@ -166,10 +166,14 @@ Sometimes build scripts and plugins produce pre-compressed minified files (for e
 ### Verify Source Fetching is Enabled
 
 If you're <PlatformLink to="/sourcemaps/uploading/hosting-publicly/">hosting your source maps publicly</PlatformLink>, make sure you have the "Enable JavaScript source fetching" option activated under **[Settings] > Projects > Select your project > General Settings**.
+
 </PlatformSection>
 
+### (Self-Hosted Sentry) Verify the `symbolicator` service is operating normally
+
+If you're running a self-hosted version of Sentry, you can verify that the `symbolicator` service/container is operating normally by checking the container's logs.
 
-### Verify Workers Are Sharing Same Volume as Web (if running self-hosted Sentry via Docker)
+### (Self-Hosted Sentry via Docker) Verify workers are sharing the same volume as web
 
 Sentry does source map calculation in its workers. This means the workers need access to the files uploaded through the front end. Double check that the cron workers and web workers can read/write files from the same disk.