From b0f265aa3fd323d6d1f7345150542bc08c0095c2 Mon Sep 17 00:00:00 2001 From: Ivan Shcheklein Date: Fri, 24 Jul 2020 11:53:29 -0700 Subject: [PATCH] Update data-registries.md --- content/docs/use-cases/data-registries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/use-cases/data-registries.md b/content/docs/use-cases/data-registries.md index fc14080937..3b014c7dab 100644 --- a/content/docs/use-cases/data-registries.md +++ b/content/docs/use-cases/data-registries.md @@ -8,7 +8,7 @@ with commands such as `dvc add`. With the aim to enable reusability of these depend on data from an external DVC repository, **similar to package management systems, but for data science projects**. -![DVC Data and Model Registry](/img/data-registry.png)_Data and models as code_ +![DVC Data and Model Registry](/img/data-registry.png) _Data and models as code_ Keeping this in mind, we could build a DVC project dedicated to tracking and versioning _datasets_ (or any large data, even ML models). This way