From 13e43bf2ebc2dd687ad73e0fbbdca58bc0bbfb45 Mon Sep 17 00:00:00 2001 From: Paulin Todev Date: Wed, 11 Dec 2024 12:03:06 +0000 Subject: [PATCH] Reword docs --- docs/sources/reference/http/_index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/sources/reference/http/_index.md b/docs/sources/reference/http/_index.md index 374e0e0386..f2f433e7b2 100644 --- a/docs/sources/reference/http/_index.md +++ b/docs/sources/reference/http/_index.md @@ -1,7 +1,7 @@ --- canonical: https://grafana.com/docs/alloy/latest/reference/http/ description: Learn about HTTP endpoints exposed by Grafana Alloy -title: Grafana Alloy HTTP endpoints +title: The Grafana Alloy HTTP endpoints menuTitle: HTTP endpoints weight: 700 --- @@ -44,12 +44,12 @@ unhealthy components: math.add ``` {{< admonition type="note" >}} -The `/-/healthy` endpoint is not suitable for a [Kubernetes liveness probe][k8s-liveness]. +The `/-/healthy` endpoint isn't suitable for a [Kubernetes liveness probe][k8s-liveness]. -An Alloy instance which reports as unhealthy should not necessarily be restarted. -For example, a component may be unhealthy due to invalid configuration or due to an unavailable external resource. +An {{< param "PRODUCT_NAME" >}} instance that reports as unhealthy should not necessarily be restarted. +For example, a component may be unhealthy due to an invalid configuration or an unavailable external resource. In this case, restarting {{< param "PRODUCT_NAME" >}} would not fix the problem. -A restart may even make it worse, because it would could stop the flow of telemetry in healthy pipelines. +A restart may make it worse, because it would could stop the flow of telemetry in healthy pipelines. [k8s-liveness]: https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/ {{< /admonition >}}