diff --git a/docs/concepts/gardenlet.md b/docs/concepts/gardenlet.md
index 24af0fd6d1b..78eb41fdf97 100644
--- a/docs/concepts/gardenlet.md
+++ b/docs/concepts/gardenlet.md
@@ -402,11 +402,11 @@ This reconciler performs three "care" actions related to `Shoot`s.
 
 ##### Conditions
 
-It maintains five conditions and performs the following checks:
+It maintains the following conditions:
 
 - `APIServerAvailable`: The `/healthz` endpoint of the shoot's `kube-apiserver` is called and considered healthy when it responds with `200 OK`.
 - `ControlPlaneHealthy`: The control plane is considered healthy when the respective `Deployment`s (for example `kube-apiserver`,`kube-controller-manager`), and `Etcd`s (for example `etcd-main`) exist and are healthy.
-- `ObservabilityComponentsHealthy`: This condition is considered healthy when the respective `Deployment`s (for example `plutono`), `StatefulSet`s (for example `prometheus`,`vali`), exist and are healthy.
+- `ObservabilityComponentsHealthy`: This condition is considered healthy when the respective `Deployment`s (for example `plutono`) and `StatefulSet`s (for example `prometheus`,`vali`) exist and are healthy.
 - `EveryNodyReady`: The conditions of the worker nodes are checked (e.g., `Ready`, `MemoryPressure`). Also, it's checked whether the Kubernetes version of the installed `kubelet` matches the desired version specified in the `Shoot` resource.
 - `SystemComponentsHealthy`: The conditions of the `ManagedResource`s are checked (e.g., `ResourcesApplied`). Also, it is verified whether the VPN tunnel connection is established (which is required for the `kube-apiserver` to communicate with the worker nodes).
 
diff --git a/docs/concepts/operator.md b/docs/concepts/operator.md
index ff95d476193..7d768d0d848 100644
--- a/docs/concepts/operator.md
+++ b/docs/concepts/operator.md
@@ -268,11 +268,12 @@ The controller maintains the `.status.lastOperation` which indicates the status
 
 This reconciler performs four "care" actions related to `Garden`s.
 
-It maintains four conditions and performs the following checks:
+It maintains the following conditions:
 
 - `RuntimeComponentsHealthy`: The conditions of the `ManagedResource`s applied to the runtime cluster are checked (e.g., `ResourcesApplied`).
 - `VirtualComponentsHealthy`: The virtual components are considered healthy when the respective `Deployment`s (for example `virtual-garden-kube-apiserver`,`virtual-garden-kube-controller-manager`), and `Etcd`s (for example `virtual-garden-etcd-main`) exist and are healthy. Additionally, the conditions of the `ManagedResource`s applied to the virtual cluster are checked (e.g., `ResourcesApplied`).
 - `VirtualGardenAPIServerAvailable`: The `/healthz` endpoint of the garden's `virtual-garden-kube-apiserver` is called and considered healthy when it responds with `200 OK`.
+- `ObservabilityComponentsHealthy`: This condition is considered healthy when the respective `Deployment`s (for example `plutono`) and `StatefulSet`s (for example `prometheus`,`vali`) exist and are healthy. 
 
 If all checks for a certain condition are succeeded, then its `status` will be set to `True`.
 Otherwise, it will be set to `False` or `Progressing`.