Skip to content

Commit 47f1315

Browse files
docs: improve wording in Summary (Evidently AI description) (#483)
Co-authored-by: Nicki Skafte Detlefsen <skaftenicki@gmail.com>
1 parent ecf22e2 commit 47f1315

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

pages/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,6 @@ a different stack of tools that better fits your needs. Regardless of the stack,
4343
| ![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 |
4444
| ![Locust](../figures/icons/locust.png){ width="50" } | For load testing our deployed model we can use **Locust** |
4545
| ![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 |
46-
| ![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 |
46+
| ![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 |
4747
| ![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 |
4848
<!-- markdownlint-restore -->

0 commit comments

Comments
 (0)