From 75186e543fc78ce89d0159e48cb22726fb1ed023 Mon Sep 17 00:00:00 2001 From: Jo Stichbury Date: Tue, 5 Nov 2024 13:01:07 +0000 Subject: [PATCH] Update vizro-ai/docs/pages/user-guides/add-generated-chart-usecase.md Co-authored-by: Lingyi Zhang --- vizro-ai/docs/pages/user-guides/add-generated-chart-usecase.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vizro-ai/docs/pages/user-guides/add-generated-chart-usecase.md b/vizro-ai/docs/pages/user-guides/add-generated-chart-usecase.md index ad909354e..fa87f16e1 100644 --- a/vizro-ai/docs/pages/user-guides/add-generated-chart-usecase.md +++ b/vizro-ai/docs/pages/user-guides/add-generated-chart-usecase.md @@ -121,7 +121,7 @@ This object must then be passed to the `figure` argument of the Vizro [Graph](ht We can also use Vizro-AI dynamically and assign the output of `plot()` directly to the fig variable, enabling its reuse in the `vm.Graph.figure` argument. This method offers streamlined efficiency, eliminating the need for code copying. -Note that each dashboard run triggers an API call to OpenAI, possibly escalating costs. This can be avoided if the `fig` object is stored and retrieved as needed, instead of making repeated calls to `plot()`. +Note that each dashboard run triggers an API call to the LLM, possibly escalating costs. This can be avoided if the `fig` object is stored and retrieved as needed, instead of making repeated calls to `plot()`. Executing the code below yields the identical dashboard as the example above.