From a249875e96a626f3af3a99d7e4a5344eb874d65f Mon Sep 17 00:00:00 2001 From: Sarthak khandelwal Date: Mon, 6 Jul 2020 10:35:12 +0530 Subject: [PATCH] Update content/docs/use-cases/versioning-data-and-model-files/tutorial.md Co-authored-by: Jorge Orpinel --- .../use-cases/versioning-data-and-model-files/tutorial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/use-cases/versioning-data-and-model-files/tutorial.md b/content/docs/use-cases/versioning-data-and-model-files/tutorial.md index 07589b8c10..1c60f0bba1 100644 --- a/content/docs/use-cases/versioning-data-and-model-files/tutorial.md +++ b/content/docs/use-cases/versioning-data-and-model-files/tutorial.md @@ -329,8 +329,8 @@ file. It tracks all outputs (`-o`) the same way as `dvc add` does. Unlike `dvc add`, `dvc run` also tracks dependencies (`-d`) and the command (`python train.py`) that was run to produce the result. -> At this point you could run `git add .` and `git commit` to save the updated -> stage and its changed outputs to the repository. +> At this point you could run `git add .` and `git commit` to save the `train` +> stage and its outputs to the repository. `dvc repro` will run `train` stage if any of its dependencies (`-d`) changed. For example, when we added new images to built the second version of our model,