docs: fix incorrect infinite loop claim in set-state-in-render

justismailmemon · justismailmemon · commit d8c7fb6b7669 · 2026-04-17T17:48:35.000+05:00
diff --git a/src/content/reference/eslint-plugin-react-hooks/lints/set-state-in-render.md b/src/content/reference/eslint-plugin-react-hooks/lints/set-state-in-render.md
@@ -88,7 +88,7 @@ function Counter({max}) {
 }
 ```
 
-As soon as `count` exceeds `max`, an infinite loop is triggered.
+When `count` exceeds `max`, this schedules a state update during render. This is still an anti-pattern because rendering should stay pure, and state updates should happen in an event handler or effect instead.
 
 Instead, it's often better to move this logic to the event (the place where the state is first set). For example, you can enforce the maximum at the moment you update state:
 

Original file line number	Diff line number	Diff line change
`@@ -88,7 +88,7 @@ function Counter({max}) {`
`88`	`88`	`}`
`89`	`89`	```
`90`	`90`
`91`		-As soon as `count` exceeds `max`, an infinite loop is triggered.
	`91`	+When `count` exceeds `max`, this schedules a state update during render. This is still an anti-pattern because rendering should stay pure, and state updates should happen in an event handler or effect instead.
`92`	`92`
`93`	`93`	`Instead, it's often better to move this logic to the event (the place where the state is first set). For example, you can enforce the maximum at the moment you update state:`
`94`	`94`