From 7e5a36bce1f36dfc5d6a13525d712f484fae09c2 Mon Sep 17 00:00:00 2001 From: Krzysztof Warzecha Date: Thu, 4 Sep 2025 11:34:31 +0200 Subject: [PATCH] docs: fix typo in healthchecks section missing ) --- content/recipes/terminus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/recipes/terminus.md b/content/recipes/terminus.md index 1d8c49da9a..af18586ea2 100644 --- a/content/recipes/terminus.md +++ b/content/recipes/terminus.md @@ -2,7 +2,7 @@ Terminus integration provides you with **readiness/liveness** health checks. Healthchecks are crucial when it comes to complex backend setups. In a nutshell, a health check in the realm of web development usually consists of a special address, for example, `https://my-website.com/health/readiness`. -A service or a component of your infrastructure (e.g., [Kubernetes](https://kubernetes.io/) checks this address continuously. Depending on the HTTP status code returned from a `GET` request to this address the service will take action when it receives an "unhealthy" response. +A service or a component of your infrastructure (e.g., [Kubernetes](https://kubernetes.io/) checks this address continuously). Depending on the HTTP status code returned from a `GET` request to this address the service will take action when it receives an "unhealthy" response. Since the definition of "healthy" or "unhealthy" varies with the type of service you provide, the **Terminus** integration supports you with a set of **health indicators**.