Address PR feedback for .thvignore documentation

- Fix global config path to be cross-platform compatible (Linux/macOS/Windows)
- Remove redundant Requirements section
- Change section heading to 'Create an ignore file'
- Update file creation description to be more specific
- Replace 'fetch' with 'filesystem' in command examples (better example)
- Update troubleshooting section to use collapsible details format
- Convert recommendation text to use tip admonition format
- Improve global patterns description text
- Add clarification about pattern matching limitations (no full glob syntax)

Author: JAORMX

docs/toolhive/guides-cli/thvignore.md

@@ -25,16 +25,10 @@ the container:
 The rest of the files remain bind-mounted from your host, so edits are visible
 in the container immediately.
 
-## Requirements
+## Create an ignore file
 
-- ToolHive CLI
-- A mount source directory that contains a `.thvignore` file with patterns to
-  exclude
-
-## Create a .thvignore
-
-Create a `.thvignore` file at the root of the directory you intend to mount. Use
-simple, gitignore-like patterns:
+Create a file named `.thvignore` at the root of the directory you intend to
+mount. Use simple, gitignore-like patterns:
 
 ```text
 # secrets
@@ -61,60 +55,78 @@ Guidelines:
 - `*.ext` matches any file with that extension directly under the mount source
 - Lines starting with `#` are comments; blank lines are ignored
 
+:::info[Pattern matching]
+
+ToolHive uses simple gitignore-like patterns. Advanced gitignore glob syntax
+like `**/*.env` (to match files in any subdirectory) is not currently supported.
+Patterns only match files and directories directly under the mount source.
+
+:::
+
 ## Run a server with .thvignore
 
 Mount your project directory as usual. ToolHive automatically reads `.thvignore`
 if present:
 
 ```bash
-thv run --volume ./my-project:/app fetch
+thv run --volume ./my-project:/projects filesystem
 ```
 
 To print resolved overlay targets for debugging:
 
 ```bash
-thv run --volume ./my-project:/app \
+thv run --volume ./my-project:/projects \
   --print-resolved-overlays \
-  fetch
+  filesystem
 ```
 
 The resolved overlays are logged to the workload's log file. For a complete list
 of options, see the [`thv run` command reference](../reference/cli/thv_run.md).
 
 ## Global ignore patterns
 
-You can define global ignore patterns at:
-
-```text
-~/.config/toolhive/thvignore
-```
+You can define global ignore patterns in a platform-specific location:
 
-These patterns are loaded in addition to your project's local `.thvignore`.
+- **Linux**: `~/.config/toolhive/thvignore`
+- **macOS**: `~/Library/Application Support/toolhive/thvignore`
+- **Windows**: `%LOCALAPPDATA%\toolhive\thvignore`
 
-- Enabled by default
-- Disable for a single run:
+Patterns contained in the global configuration are loaded in addition to a local
+`.thvignore` file. To disable global patterns for a specific workload, use the
+`--ignore-globally=false` option:
 
 ```bash
-thv run --ignore-globally=false --volume ./my-project:/app fetch
+thv run --ignore-globally=false --volume ./my-project:/projects filesystem
 ```
 
-Recommendation: Store machine-wide patterns (for example, `.aws/`, `.gcp/`,
-`.ssh/`, `*.pem`, `.docker/config.json`) in the global file, and keep
-app-specific patterns (for example, `.env*`, build artifacts) in your project's
-local `.thvignore`.
+:::tip[Recommendation]
+
+Set machine-wide patterns (for example, `.aws/`, `.gcp/`, `.ssh/`, `*.pem`,
+`.docker/config.json`) in the global file, and keep app-specific patterns (for
+example, `.env*`, build artifacts) in your project's local `.thvignore`.
+
+:::
 
 ## Troubleshooting
 
-- Overlays didn't apply
-  - Ensure `.thvignore` exists in the mount source directory (not elsewhere)
-  - Confirm patterns match actual names relative to the mount source
-  - Run with `--print-resolved-overlays` and check the workload's log file path
-    displayed by `thv run`
+<details>
+<summary>Overlays didn't apply</summary>
+
+- Ensure `.thvignore` exists in the mount source directory (not elsewhere)
+- Confirm patterns match actual names relative to the mount source
+- Run with `--print-resolved-overlays` and check the workload's log file path
+  displayed by `thv run`
+
+</details>
+
+<details>
+<summary>Can't list a parent directory</summary>
+
+- On SELinux systems, listing a parent directory may fail even though specific
+  files are accessible. Probe individual paths instead (for example, `stat` or
+  `cat`).
 
-- Can’t list a parent directory
-  - On SELinux systems, listing a parent directory may fail even though specific
-    files are accessible. Probe individual paths instead (for example, `stat` or
-    `cat`).
+</details>
 
 ## Related information