From cf033f448dd91893553d77bdcdce89ced99bee5d Mon Sep 17 00:00:00 2001 From: Ryan Breen Date: Thu, 29 Jan 2015 17:14:19 -0500 Subject: [PATCH] No need to confine the example to a web app. --- website/source/docs/agent/checks.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/agent/checks.html.markdown b/website/source/docs/agent/checks.html.markdown index 85b48048a9..93bd783ba3 100644 --- a/website/source/docs/agent/checks.html.markdown +++ b/website/source/docs/agent/checks.html.markdown @@ -32,7 +32,7 @@ There are three different kinds of checks: The state of the check must be updated periodically over the HTTP interface. If an external system fails to update the status within a given TTL, the check is set to the failed state. This mechanism, conceptually similar to a dead man's switch, - relies on the application to directly report its health. For example, a healthy web app + relies on the application to directly report its health. For example, a healthy app can periodically `PUT` a status update to the HTTP endpoint; if the app fails, the TTL will expire and the health check enters a critical state.