From da3db6c852422be429e889b654403b18601f0d05 Mon Sep 17 00:00:00 2001 From: sdiazlor Date: Fri, 21 Jun 2024 13:18:10 +0200 Subject: [PATCH] docs: fix minor warning --- argilla/docs/how_to_guides/migrate_from_legacy_datasets.md | 2 +- argilla/docs/reference/argilla/records/records.md | 2 +- docs/_source/getting_started/argilla.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/argilla/docs/how_to_guides/migrate_from_legacy_datasets.md b/argilla/docs/how_to_guides/migrate_from_legacy_datasets.md index 7179645bc2..ad8d513e62 100644 --- a/argilla/docs/how_to_guides/migrate_from_legacy_datasets.md +++ b/argilla/docs/how_to_guides/migrate_from_legacy_datasets.md @@ -10,7 +10,7 @@ This guide will help you migrate task specific datasets to Argilla V2. These do To follow this guide, you will need to have the following prerequisites: - An argilla 1.* server instance running with legacy datasets. -- An argilla >=1.29 server instance running. If you don't have one, you can create one by following the [Argilla installation guide](../../getting_started/installation.md). +- An argilla >=1.29 server instance running. If you don't have one, you can create one by following the [Argilla installation guide](../getting_started/installation.md). - The `argilla` sdk package installed in your environment. If your current legacy datasets are on a server with Argilla release after 1.29, you could chose to recreate your legacy datasets as new datasets on the same server. You could then upgrade the server to Argilla 2.0 and carry on working their. Your legacy datasets will not be visible on the new server, but they will remain in storage layers if you need to access them. diff --git a/argilla/docs/reference/argilla/records/records.md b/argilla/docs/reference/argilla/records/records.md index d4daee9966..f09a9573c2 100644 --- a/argilla/docs/reference/argilla/records/records.md +++ b/argilla/docs/reference/argilla/records/records.md @@ -47,7 +47,7 @@ for record in dataset.records(with_metadata=True): record.metadata = {"department": "toys"} ``` -For changes to take effect, the user must call the `update` method on the `Dataset` object, or pass the updated records to `Dataset.records.log`. All core record atttributes can be updated in this way. Check their respective documentation for more information: [Suggestions](suggestions.md), [Responses](responses.md), [Metadata](metadata.md), [Vectors](vectors/md). +For changes to take effect, the user must call the `update` method on the `Dataset` object, or pass the updated records to `Dataset.records.log`. All core record atttributes can be updated in this way. Check their respective documentation for more information: [Suggestions](suggestions.md), [Responses](responses.md), [Metadata](metadata.md), [Vectors](vectors.md). --- diff --git a/docs/_source/getting_started/argilla.md b/docs/_source/getting_started/argilla.md index a40eedfc04..3eb03bc634 100644 --- a/docs/_source/getting_started/argilla.md +++ b/docs/_source/getting_started/argilla.md @@ -5,7 +5,7 @@ ```{admonition} Argilla 2.x :class: danger We are announcing that Argilla 1.29 is the final minor release for Argilla 1.x. Although we will continue to release bug fixes for this version, we will neither be adding nor removing any functionalities. Instead, we will focus our efforts on Argilla 2.x. Argilla 1.29 will reach its end-of-life on June 20, 2025. -Looking for documentation for Argilla 2.x? Visit the docs [here](https://argilla-io.github.io/argilla/dev/)! +Looking for documentation for Argilla 2.x? Visit the docs [here](https://argilla-io.github.io/argilla/)! ```