From 435e18e117e6639cc501692b131cba2bcd27c76d Mon Sep 17 00:00:00 2001 From: Sofie Van Landeghem Date: Fri, 1 Sep 2023 14:08:29 +0200 Subject: [PATCH] Apply suggestions from code review --- website/docs/api/large-language-models.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/docs/api/large-language-models.mdx b/website/docs/api/large-language-models.mdx index de43495a1..60f2714b8 100644 --- a/website/docs/api/large-language-models.mdx +++ b/website/docs/api/large-language-models.mdx @@ -27,11 +27,11 @@ options: | `save_io` | Whether to save prompts/responses within `Doc.user_data["llm_io"]`. ~~bool~~ | | `validate_types` | Whether to check if signatures of configured model and task are consistent. ~~bool~~ | -Beyond that, a `llm_TASKNAME` factory is available for each task - `llm_ner` for -a LLM component with the NER task, `llm_rel` for relationship extraction etc. +Beyond that, an `llm_TASKNAME` factory is available for each task - `llm_ner` for +an LLM component with the NER task, `llm_rel` for relationship extraction etc. These factories are equivalent to using the `llm` factory and defining the task -in the configuration. Note: tasks may require more configuration than the just -the task - compare with the tasks' description below. +in the configuration. Note: tasks may require more configuration than just +the task factory - compare with the tasks' description below. An `llm` component is defined by two main settings: