docs: fix salvaged PR #980 troubleshooting details

Correct the PowerShell UTF-8 snippet in the new Windows encoding tip
and soften the Docker CLI wording to match Hermes' actual lookup
behavior.

website/docs/guides/tips.md

@@ -192,13 +192,13 @@ with open("results.txt", "w", encoding="utf-8") as f:
     f.write("✓ All good\n")
 ```
 
-- In PowerShell, you can also set UTF-8 as the default output encoding for your session:
+- In PowerShell, you can also switch the current session to UTF-8 for console and native command output:
 
 ```powershell
-$PSStyle.OutputEncoding = [Console]::OutputEncoding = [Text.UTF8Encoding]::new($false)
+$OutputEncoding = [Console]::OutputEncoding = [Text.UTF8Encoding]::new($false)
 ```
 
-This matches how the CI environment behaves and helps avoid Windows-only failures.
+This keeps PowerShell and child processes on UTF-8 and helps avoid Windows-only failures.
 
 ### Review Before Choosing "Always"
 

website/docs/user-guide/configuration.md

@@ -445,7 +445,7 @@ If terminal commands fail immediately or the terminal tool is reported as disabl
 
 - **Docker backend**
   - Ensure Docker Desktop (or the Docker daemon) is installed and running.
-  - The `docker` CLI must be available in your `$PATH`. Run:
+  - Hermes needs to be able to find the `docker` CLI. It checks your `$PATH` first and also probes common Docker Desktop install locations on macOS. Run:
     ```bash
     docker version
     ```