@tavus/widget 0.19.1 → 0.19.2

package/README.md

@@ -70,13 +70,13 @@ el.addEventListener("tavus:protocol-message", (e) => {}); // every protocol even
 
 Also `tavus:conversation-created`, `tavus:state-change` and `tavus:mode-change`. `tavus:chat-message` and `tavus:message` are in the type definitions for compatibility and never fire.
 
-Methods exist once `tavus:ready` has fired. The widget adds `open()` and `close()` for the popup; a start from the page also opens it, so a host button can be the only thing the visitor touches:
+Methods exist once `tavus:ready` has fired. The widget adds `open()` and `close()` for the popup. `close()` is the popup's own close path: it ends a call in progress and cancels a pending start before it collapses. A start from the page also opens the popup, so a host button can be the only thing the visitor touches:
 
 ```js
 el.open();
 el.close();
-el.startConversation(); // same path as the visitor pressing Start; never rejects. Most failures arrive as tavus:error;
-// the daily limit, a busy PAL and a bot check that cannot run arrive as tavus:mode-change with mode "unavailable"
+el.startConversation(); // same path as the visitor pressing Start; never rejects. Failures arrive as tavus:error;
+// the daily limit, a busy PAL and a bot check that cannot run also move the element to its unavailable screen (tavus:mode-change with mode "unavailable")
 await el.createConversation(); // create the room now so the next start joins without the wait
 el.endConversation();
 el.sendMessage({