diff --git a/files/en-us/web/api/window/reporterror/index.md b/files/en-us/web/api/window/reporterror/index.md
index ebf2e6e5370ea58..326b5af445db1f9 100644
--- a/files/en-us/web/api/window/reporterror/index.md
+++ b/files/en-us/web/api/window/reporterror/index.md
@@ -23,7 +23,7 @@ reportError(throwable)
 ### Parameters
 
 - `throwable`
-  - : An error object such as a {{jsxref("TypeError")}}.
+  - : Any JavaScript value, but preferably an error object such as a {{jsxref("TypeError")}}.
 
 ### Return value
 
@@ -36,6 +36,8 @@ None ({{jsxref("undefined")}}).
 
 ## Examples
 
+### Feature detection
+
 Feature test for the method using:
 
 ```js
@@ -44,27 +46,41 @@ if (typeof window.reportError === "function") {
 }
 ```
 
-The following code shows how you might create and report an error, and how it may be caught using either the `onerror` event handler property or by adding a listener for the `error` event.
-Note that the handler assigned to `onerror` must return `true` to stop the event propagating further.
+### Telemetry
 
-```js
-const newError = new Error("Some error message", "someFile.js", 11);
-window.reportError(newError);
+`reportError()` allows asynchronous errors to be reported just like built-in errors. Aggregating all errors at a single point makes it easier to collect telemetry about errors occurring in an application.
 
-window.onerror = (message, source, lineno, colno, error) => {
-  console.error(`message: ${error.message}, lineno: ${lineno}`);
-  return true;
-};
+For example, a web application might set up a global [`error`](/en-US/docs/Web/API/Window/error_event) event listener to collect all uncaught errors, and send them to a server for analysis, such as by using [Sentry](https://sentry.io/):
 
-window.addEventListener("error", (error) => {
-  console.error(error.filename);
+```js
+window.addEventListener("error", (event) => {
+  event.preventDefault(); // Prevent the default logging to console
+  Sentry.captureException(event.error);
+  console.error("Error encountered:", event.error);
+  showToastNotification("An error occurred. Our team has been notified.");
 });
+```
 
-// Output
-// > "message:Some error message, lineno: 11"
-// > "someFile.js"
+By default, this listener can listen for uncaught exceptions thrown in synchronous `<script>` execution, `setTimeout` callbacks, event handlers, asynchronous promise callbacks, and so on. Libraries and applications can use `reportError()` to deliver their own errors to this same listener, ensuring that all errors are captured in a consistent manner.
+
+```js
+function fetchUser(userId) {
+  return fetch(`/api/users?id=${encodeURIComponent(userId)}`)
+    .then((response) => {
+      if (!response.ok) {
+        throw new Error(`Failed to fetch user with ID ${userId}`);
+      }
+      return response.json();
+    })
+    .catch((error) => {
+      // Report the error to the global error handler
+      window.reportError(error);
+    });
+}
 ```
 
+By using `reportError()` instead of letting the error go uncaught, subsequent code execution is not interrupted, while still ensuring that the error is logged and can be analyzed. For example, this function can be called in a test runner without extra `try...catch` handling.
+
 ## Specifications
 
 {{Specifications}}
diff --git a/files/en-us/web/api/workerglobalscope/reporterror/index.md b/files/en-us/web/api/workerglobalscope/reporterror/index.md
index 6859340f440ffdc..04c1f418d7eab06 100644
--- a/files/en-us/web/api/workerglobalscope/reporterror/index.md
+++ b/files/en-us/web/api/workerglobalscope/reporterror/index.md
@@ -14,6 +14,8 @@ This feature is primarily intended for custom event-dispatching or callback-mani
 Libraries can use this feature to catch errors in callback code and re-throw them to the top level handler.
 This ensures that an exception in one callback will not prevent others from being handled, while at the same time ensuring that stack trace information is still readily available for debugging at the top level.
 
+See [`window.reportError()`](/en-US/docs/Web/API/Window/reportError) for more information.
+
 ## Syntax
 
 ```js-nolint
@@ -23,7 +25,7 @@ reportError(throwable)
 ### Parameters
 
 - `throwable`
-  - : An error object such as a {{jsxref("TypeError")}}.
+  - : Any JavaScript value, but preferably an error object such as a {{jsxref("TypeError")}}.
 
 ### Return value
 
@@ -34,37 +36,6 @@ None ({{jsxref("undefined")}}).
 - {{jsxref("TypeError")}}
   - : The method is called without an error argument.
 
-## Examples
-
-Feature test for the method using:
-
-```js
-if (typeof self.reportError === "function") {
-  // function is defined
-}
-```
-
-The following code shows how you might create and report an error, and how it may be caught using either the `onerror` event handler property or by adding a listener for the `error` event.
-Note that the handler assigned to `onerror` must return `true` to stop the event propagating further.
-
-```js
-const newError = new Error("Some error message", "someFile.js", 11);
-self.reportError(newError);
-
-self.onerror = (message, source, lineno, colno, error) => {
-  console.error(`message: ${error.message}, lineno: ${lineno}`);
-  return true;
-};
-
-self.addEventListener("error", (error) => {
-  console.error(error.filename);
-});
-
-// Output
-// > "message:Some error message, lineno: 11"
-// > "someFile.js"
-```
-
 ## Specifications
 
 {{Specifications}}