Clarify activation/set-password/redirection behavior

See #734 + craftcms/cms#17522!

Author: AugustMiller

docs/5.x/reference/controller-actions.md

@@ -311,8 +311,8 @@ For <badge vertical="baseline" type="verb">POST</badge> requests:
 
 State | `text/html` | `application/json`
 ----- | ----------- | ------------------
-<check-mark label="Success" /> | [Standard behavior][success-after-post]; redirection depends on the <config5:autoLoginAfterAccountActivation> and <config5:setPasswordSuccessPath> config settings, and whether the user has access to the control panel. | [Standard behavior][success-after-post]; additional `csrfTokenName` key will be available in the response object.
-<x-mark label="Failure" /> | [Standard behavior][failure-during-post]; `errors` , `code`, `id`, and `newUser` variables will be passed to the resulting template. | [Standard behavior][failure-during-post].
+<check-mark label="Success" /> | [Standard behavior][success-after-post]; redirection depends on the user’s [status](../system/user-management.md#statuses), the <config5:autoLoginAfterAccountActivation> and <config5:setPasswordSuccessPath> config settings, and whether the user has access to the control panel. | [Standard behavior][success-after-post]; additional `csrfTokenName` key will be available in the response object.
+<x-mark label="Failure" /> | [Standard behavior][failure-during-post]; `errors`, `code`, `id`, and `newUser` variables will be passed to the resulting template. | [Standard behavior][failure-during-post].
 
 </span>
 

docs/5.x/system/user-management.md

@@ -519,7 +519,7 @@ Fine-grained control over registration and sign-in workflows are possible with t
   - <config5:verifyEmailSuccessPath> — Similar to `setPasswordSuccessPath`, but for redirection after a user verifies their email address (either upon creating an account, or changing its email address).
   - <config5:useEmailAsUsername> — Simplifies record-keeping and authentication by eliminating discrete usernames.
 - Security and timing…
-  - <config5:autoLoginAfterAccountActivation> — Control whether users are immediately logged in after setting a password. (Default: `false`)
+  - <config5:autoLoginAfterAccountActivation> — Control whether users are immediately logged in after completing registration (typically when a [pending](#statuses) user clicking an email confirmation link or setting a password). (Default: `false`)
   - <config5:purgePendingUsersDuration> — How long Craft waits before deleting pending, non-activated users. (Default: `0`, or _disabled_)
   - <config5:purgeStaleUserSessionDuration> — How long Craft waits before dropping stale sessions from the `sessions` database table. This may (Default: 90 days)
   - <config5:invalidUserTokenPath> — Where users are redirected if the token or code in an activation or verification link is invalid or has expired.