From cbd9abfdc30e5e531bb8748f27131525dd275fd5 Mon Sep 17 00:00:00 2001 From: dotCooCoo Date: Sat, 7 Nov 2026 17:11:33 -0800 Subject: [PATCH] craft-update: say that the drop starts the helper only when the app drops the Updater --- crates/update/src/updater.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/crates/update/src/updater.rs b/crates/update/src/updater.rs index 0368cb86a..c31c8f240 100644 --- a/crates/update/src/updater.rs +++ b/crates/update/src/updater.rs @@ -44,9 +44,9 @@ pub enum Action { OpenUrl(String), /// Close the app through its normal close path (which asks about unsaved work): the update is /// installed and a helper restarts the app once it has exited. On Windows the helper, which - /// installs the update, starts when this is returned. When the app exits another way (the - /// window's close button, a quit with unsaved work, an OS shutdown), dropping the [`Updater`] - /// starts it. An app that ends the process in `on_exit` without dropping the `Updater` calls + /// installs the update, starts when this is returned. When the app exits another way, such as + /// the window's close button or a quit with unsaved work, and drops the [`Updater`] as it exits, + /// the drop starts it. An app that ends the process in `on_exit` without dropping the `Updater` calls /// [`Updater::start_pending_update`] there first. Close, }