From e16ff3cf3c015c7bc4fdf62a625f9ae42416215a Mon Sep 17 00:00:00 2001 From: Mateusz Zbyslaw <91673363+ZbyslawMateo@users.noreply.github.com> Date: Tue, 6 Jan 2026 16:48:21 +0100 Subject: [PATCH] docs: improve wording in Summary (Evidently AI description) --- pages/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/overview.md b/pages/overview.md index 54c4d7f5c..80064e6e7 100644 --- a/pages/overview.md +++ b/pages/overview.md @@ -43,6 +43,6 @@ a different stack of tools that better fits your needs. Regardless of the stack, | ![Run](../figures/icons/run.png){ width="50" } | For more complex deployments of our code we can use **Cloud run** that allows us to run our code in response to events through docker containers | | ![Locust](../figures/icons/locust.png){ width="50" } | For load testing our deployed model we can use **Locust** | | ![Monitor](../figures/icons/monitoring.png){ width="50" } | **Cloud monitoring** gives us the tools to keep track of important logs and errors from the other cloud services | -| ![Evidently](../figures/icons/evidentlyai.png){ width="50" } | For monitoring our deployed model is experiencing any drift we can use **Evidently AI** that provides a framework and dashboard for monitoring drift | +| ![Evidently](../figures/icons/evidentlyai.png){ width="50" } | To monitor whether our deployed model is experiencing any drift, we can use **Evidently AI**, which provides a framework and dashboard for drift monitoring | | ![Telemetry](../figures/icons/opentelemetry.png){ width="50" } | For monitoring the telemetry of our deployed model we can use **OpenTelemetry** that provides a standard for collecting and exporting telemetry data |