diff --git a/content/post/self-hosted-voice-control.md b/content/post/self-hosted-voice-control.md
index 259fb40..3f49409 100644
--- a/content/post/self-hosted-voice-control.md
+++ b/content/post/self-hosted-voice-control.md
@@ -143,7 +143,7 @@ The next step is to actually configure Kalliope. The examples are a good startin
           cmd: /bin/sleep 0.2
 ```
 
-Using this configuration as a jumping-off point, you can add multiple other options, and including the various shell commands you can ensure that the LED ring shows the status of every task.
+Using this configuration as a jumping-off point, you can add multiple other options, and including the various shell commands you can ensure that the LED ring shows the status of every task. So far, the only downside I've found with Kalliope is that single-word triggers are generally unsupported; the device doesn't realize to stop listening, so try to keep them to two or more words.
 
 I use a custom Systemd unit to ensure everything is started correctly, including output buffering, and as mentioned above ensures the configuration repository is always up-to-date with the origin, making configuration updates on-the-fly to multiple devices quick and painless.