feat: manage venv for all backends

1 files changed, 4 insertions, 2 deletions

diff --git a/docs/backend-qwen.md b/docs/backend-qwen.md
index 0c9dab0..028d6f3 100644
--- a/docs/backend-qwen.md
+++ b/docs/backend-qwen.md
@@ -1,8 +1,10 @@
 # Backend Option 2: Qwen3-TTS
 
-The TUI sets this up: run `python audiobook.py` → **Set up a backend… → qwen-tts**, or `python -m backends.qwen`. It pip-installs `qwen-tts` and configures the two ports and built-in speaker in `converter/config.py`, then prints the launch commands. Manual steps:
+The easiest way is to run `python audiobook.py` → **Set up a backend… → qwen-tts** (or `python -m backends.qwen`): the TUI pip-installs `qwen-tts` into its managed venv (`envs/tts`), configures the two ports and the built-in speaker in `converter/config.py`, and prints the launch commands. You can also start the server from the hub's **Server** menu, or let a conversion start it automatically.
 
-Install qwen-tts with pip:
+If you prefer to install the backend yourself (in your own environment, not the managed venv), the manual steps are below. Either way the hub detects a running server by its port, so a manually-installed backend works once its server is up.
+
+Install qwen-tts with pip into your environment:
 
 ```bash
 conda activate audiobook