Soften backend claim for Auto availability; rewrap comments

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

HOW-TO-USE.md

@@ -484,8 +484,9 @@ the way they did: one that had Full Permissions on becomes **Bypass**, one that
 **Auto** sits between Accept Edits and Bypass: Claude Code's own classifier reviews each action,
 lets routine work through and blocks things that look risky (such as destructive or
 exfiltrating commands) — no prompts either way. Whether it is available depends on your Claude
-Code account, model and backend (local and OpenAI-compatible backends won't qualify). When it
-isn't available, Claude Code quietly starts in its normal prompting mode instead.
+Code account, model and backend (local and OpenAI-compatible backends usually won't
+qualify). When it isn't available, Claude Code quietly starts in its normal prompting mode
+instead.
 
 ### When a change takes effect
 
@@ -1359,7 +1360,8 @@ with `--dangerously-skip-permissions`. Because the mode travels into the contain
 environment variable, **stop and start the project** after changing it for the scheduler to see the
 change. Remember that a headless run cannot answer a permission prompt, so in any mode other than
 **Auto** or **Bypass** a task may stop early when Claude Code asks for approval (in Auto, blocked
-actions are denied instead, unless Auto is unavailable and Claude Code falls back to prompting); the run log records the mode
+actions are denied instead, unless Auto is unavailable and Claude Code falls back to
+prompting); the run log records the mode
 that was used.
 
 ### Creating Tasks