Update no-return-await.md

nzakas · web-flow · commit bea4c4f61abe · 2025-05-16T11:08:30.000-04:00
diff --git a/docs/src/rules/no-return-await.md b/docs/src/rules/no-return-await.md
@@ -14,17 +14,9 @@ It is NOT recommended to use the `no-return-await` rule anymore because:
 
 Historical context: When promises were first introduced, calling `return await` introduced an additional microtask, one for the `await` and one for the return value of the async function. Each extra microtask delays the computation of a result and so this rule was added to help avoid this performance trap. Later, [V8 changed the way](https://v8.dev/blog/fast-async) `return await` worked so it would create a single microtask, which means this rule is no longer necessary.
 
-***
-
-This rule warns on any usage of `return await`.
-
-Using `return await` inside an `async function` keeps the current function in the call stack until the Promise that is being awaited has resolved. `return await` can also be used in a try/catch statement to catch errors from another function that returns a Promise.
-
-You can avoid the extra microtask by not awaiting the return value, with the trade off of the function no longer being a part of the stack trace if an error is thrown asynchronously from the Promise being returned. This can make debugging more difficult.
-
 ## Rule Details
 
-This rule aims to prevent a likely common performance hazard due to a lack of understanding of the semantics of `async function`.
+This rule warns on any usage of `return await`.
 
 Examples of **incorrect** code for this rule:
 
@@ -74,8 +66,4 @@ async function foo4() {
 
 ## When Not To Use It
 
-There are a few reasons you might want to turn this rule off:
-
-* If you want to use `await` to denote a value that is a thenable
-* If you do not want the performance benefit of avoiding `return await`
-* If you want the functions to show up in stack traces (useful for debugging purposes)
+You should not use this rule. There is no reason to avoid `return await`.
