docs(process-exit-as-throw): update wording (#323)

G-Rath · web-flow · commit e5e758ea0cd2 · 2024-08-05T17:22:42.000+01:00
diff --git a/docs/rules/process-exit-as-throw.md b/docs/rules/process-exit-as-throw.md
@@ -16,9 +16,9 @@ function foo(a) {
 }
 ```
 
-ESLint does not address `process.exit()` as stop in code path analysis, then [consistent-return] rule will warn the above code.
+ESLint does not mark code after `process.exit()` calls as unreachable like it does with `throw` and `return` expressions, meaning rules like [consistent-return] will still warn.
 
-If you turn this rule on, ESLint comes to address `process.exit()` as throw in code path analysis. So, above code will get expected code path.
+This rule overrides the default code path analyzer so that code after `process.exit()` calls are marked as unreachable, meaning code like the above will not trigger warnings.
 
 This rule itself never warn code.
 

Original file line number	Diff line number	Diff line change
`@@ -16,9 +16,9 @@ function foo(a) {`
`16`	`16`	`}`
`17`	`17`	```
`18`	`18`
`19`		-ESLint does not address `process.exit()` as stop in code path analysis, then [consistent-return] rule will warn the above code.
	`19`	+ESLint does not mark code after `process.exit()` calls as unreachable like it does with `throw` and `return` expressions, meaning rules like [consistent-return] will still warn.
`20`	`20`
`21`		-If you turn this rule on, ESLint comes to address `process.exit()` as throw in code path analysis. So, above code will get expected code path.
	`21`	+This rule overrides the default code path analyzer so that code after `process.exit()` calls are marked as unreachable, meaning code like the above will not trigger warnings.
`22`	`22`
`23`	`23`	`This rule itself never warn code.`
`24`	`24`