Clarify what fail means after destroy() or abort

Author: chrisdavidmills

files/en-us/web/api/languagedetector/create_static/index.md

@@ -32,7 +32,7 @@ LanguageDetector.create(options)
     - `signal` {{optional_inline}}
       - : An {{domxref("AbortSignal")}} object instance, which allows a `create()` operation to be aborted via the associated {{domxref("AbortController")}}. The exact effect is dependant on when {{domxref("AbortController.abort()")}} is called:
         - If `abort()` is called before the `create()` promise resolves, the `create()` operation is cancelled.
-        - If `abort()` is called after the `create()` promise fulfills, it has the same effect as calling {{domxref("LanguageDetector.destroy()")}}: The resources assigned to the resulting `LanguageDetector` instance are released, and any further language detection activity will fail.
+        - If `abort()` is called after the `create()` promise fulfills, it has the same effect as calling {{domxref("LanguageDetector.destroy()")}}: The resources assigned to the resulting `LanguageDetector` instance are released, and any ongoing and subsequent `LanguageDetector` method calls will reject with an `AbortError`.
 
 ### Return value
 

files/en-us/web/api/languagedetector/destroy/index.md

@@ -10,7 +10,7 @@ browser-compat: api.LanguageDetector.destroy
 
 {{APIRef("Translator and Language Detector APIs")}}{{SeeCompatTable}}{{securecontext_header}}
 
-The **`destroy()`** method of the {{domxref("LanguageDetector")}} interface releases the resources assigned to the `LanguageDetector` instance it is called on and stops any further activity on it.
+The **`destroy()`** method of the {{domxref("LanguageDetector")}} interface releases the resources assigned to the `LanguageDetector` instance it is called on and stops any further activity on it. This means that any ongoing and subsequent method calls made on the `LanguageDetector` will reject with an `AbortError`.
 
 It makes sense to destroy `LanguageDetector` objects if they are no longer being used, as they tie up significant resources in their handling.
 

files/en-us/web/api/summarizer/create_static/index.md

@@ -43,7 +43,7 @@ Summarizer.create(options)
     - `signal`
       - : An {{domxref("AbortSignal")}} object instance, which allows a `create()` operation to be aborted via the associated {{domxref("AbortController")}}. The exact effect is dependant on when {{domxref("AbortController.abort()")}} is called:
         - If `abort()` is called before the `create()` promise resolves, the `create()` operation is cancelled.
-        - If `abort()` is called after the `create()` promise fulfills, it has the same effect as calling {{domxref("Summarizer.destroy()")}}: The resources assigned to the resulting `Summarizer` instance are released, and any further summarizing activity will fail.
+        - If `abort()` is called after the `create()` promise fulfills, it has the same effect as calling {{domxref("Summarizer.destroy()")}}: The resources assigned to the resulting `Summarizer` instance are released, and any ongoing and subsequent `Summarizer` method calls will reject with an `AbortError`.
     - `type`
       - : An enumerated value specifying the {{domxref("Summarizer.type", "type")}} of summary you want this `Summarizer` to generate. Defaults to `key-points`.
 

files/en-us/web/api/summarizer/destroy/index.md

@@ -10,7 +10,7 @@ browser-compat: api.Summarizer.destroy
 
 {{APIRef("Summarizer API")}}{{SeeCompatTable}}{{securecontext_header}}
 
-The **`destroy()`** method of the {{domxref("Summarizer")}} interface releases the resources assigned to the `Summarizer` instance it is called on and stops any further activity on it.
+The **`destroy()`** method of the {{domxref("Summarizer")}} interface releases the resources assigned to the `Summarizer` instance it is called on and stops any further activity on it. This means that any ongoing and subsequent method calls made on the `Summarizer` will reject with an `AbortError`.
 
 It makes sense to destroy `Summarizer` objects if they are no longer being used, as they tie up significant resources in their handling.
 

files/en-us/web/api/translator/create_static/index.md

@@ -34,7 +34,7 @@ Translator.create(options)
     - `signal` {{optional_inline}}
       - : An {{domxref("AbortSignal")}} object instance, which allows a `create()` operation to be aborted via the associated {{domxref("AbortController")}}. The exact effect is dependant on when {{domxref("AbortController.abort()")}} is called:
         - If `abort()` is called before the `create()` promise resolves, the `create()` operation is cancelled.
-        - If `abort()` is called after the `create()` promise fulfills, it has the same effect as calling {{domxref("Translator.destroy()")}}: The resources assigned to the resulting `Translator` instance are released, and any further translation activity will fail.
+        - If `abort()` is called after the `create()` promise fulfills, it has the same effect as calling {{domxref("Translator.destroy()")}}: The resources assigned to the resulting `Translator` instance are released, and any ongoing and subsequent `Translator` method calls will reject with an `AbortError`.
 
 ### Return value
 

files/en-us/web/api/translator/destroy/index.md

@@ -10,7 +10,7 @@ browser-compat: api.Translator.destroy
 
 {{APIRef("Translator and Language Detector APIs")}}{{SeeCompatTable}} {{securecontext_header}}
 
-The **`destroy()`** method of the {{domxref("Translator")}} interface releases the resources assigned to the `Translator` instance it is called on and stops any further activity on it.
+The **`destroy()`** method of the {{domxref("Translator")}} interface releases the resources assigned to the `Translator` instance it is called on and stops any further activity on it. This means that any ongoing and subsequent method calls made on the `Translator` will reject with an `AbortError`.
 
 It makes sense to destroy `Translator` objects if they are no longer being used, as they tie up significant resources in their handling.