From ed9c1bcb7881319cf7da1f934c8d8d36f08ccf35 Mon Sep 17 00:00:00 2001 From: binwiederhier Date: Sun, 18 Jan 2026 19:46:14 -0500 Subject: [PATCH] Wording change --- docs/publish.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/publish.md b/docs/publish.md index 824f1bb8..21f85546 100644 --- a/docs/publish.md +++ b/docs/publish.md @@ -2402,12 +2402,10 @@ from the server and replaced with the new one. This is different from [updating after delivery, where both messages are kept in the cache. This is particularly useful for implementing a **watchdog that triggers when your script stops sending heartbeat messages**. -This mechanism is also called a [dead man's switch](https://en.wikipedia.org/wiki/Dead_man%27s_switch). The idea is to have -a mechanism that triggers an alert if it's not periodically reset. +This mechanism is also called a [dead man's switch](https://en.wikipedia.org/wiki/Dead_man%27s_switch). -For example, you could schedule a message to be -delivered in 5 minutes, but continuously update it every minute to push the delivery time further into the future. -If your script or system stops running, the message will eventually be delivered as an alert. +For example, you could schedule a message to be delivered in 5 minutes, but continuously update it every minute to push +the delivery time further into the future. If your script or system stops running, the message will eventually be delivered as an alert. Here's an example of a dead man's switch that sends an alert if the script stops running for more than 5 minutes: