regular updates and fixes (early September)

static/docs/commands-reference/import-url.md

@@ -326,7 +326,7 @@ Saving information to 'data.xml.dvc'.
 
 DVC has noticed the "external" data source has changed, and updated the import
 stage (reproduced it). In this case it's also necessary to run `dvc repro` so
-that the rest of the pipeline is also run again. We can confirm so with:
+that the rest of the pipeline is also regenerated. We can confirm so with:
 
 ```dvc
 $ dvc status
@@ -348,6 +348,6 @@ $ dvc status
 Data and pipelines are up to date.
 ```
 
-`dvc repro` runs again the given stage `prepare.dvc`, noticing that its
+`dvc repro` regenerates the given `prepare.dvc` stage, noticing that its
 dependency `data/data.xml` has changed. `dvc status` should report "Nothing to
 reproduce." after this.

static/docs/commands-reference/install.md

@@ -285,6 +285,6 @@ Data and pipelines are up to date.
 
 After reproducing this pipeline up to the "evaluate" stage, the data files are
 in sync with the code/config files, but we must now commit the changes to the
-Git repository. Looking closely we see that `dvc status` is run again, informing
-us that the data files are synchronized with the `Pipelines are up to date.`
-message.
+Git repository. Looking closely we see that `dvc status` is used again,
+informing us that the data files are synchronized with the
+`Pipelines are up to date.` message.

static/docs/commands-reference/repro.md

@@ -1,9 +1,9 @@
 # repro
 
-Run again commands recorded in the [stages](/doc/commands-reference/run) of one
-or more [pipelines](/doc/commands-reference/pipeline), in the correct order. The
-commands to be run are determined by recursively analyzing target stages and
-changes in their dependencies.
+Regenerate [stages](/doc/commands-reference/run) of one or more
+[pipelines](/doc/commands-reference/pipeline) by executing commands recorded in
+them again, in the correct order. The commands to be executed are determined by
+recursively analyzing target stages and changes in their dependencies.
 
 ## Synopsis
 
@@ -24,7 +24,7 @@ positional arguments:
 <abbr>project</abbr>. (A pipeline is typically defined using the `dvc run`
 command, while data input nodes are defined by the `dvc add` command.)
 
-There's a few ways to restrict the stages that will be run again by this
+There's a few ways to restrict the stages that will be regenerated by this
 command: by specifying stage file `targets`, or by using the `--single-item`,
 `--cwd`, or other options.
 
@@ -92,13 +92,13 @@ specified), and updates stage files with the new checksum information.
   `requirements.txt`, we can specify it only once in `A`, omitting it in `B` and
   `C`. To be precise , it reproduces all descendants of a changed stage or the
   stages following the changed stage, even if their direct dependencies did not
-  change. Like with the same option on `dvc run`, this is a way to force stages
-  without changes to run again. This can also be useful for pipelines containing
-  stages that produce nondeterministic (semi-random) outputs. For
+  change. Like with the same option on `dvc run`, this is a way to force
+  regenerating stages without changes. This can also be useful for pipelines
+  containing stages that produce nondeterministic (semi-random) outputs. For
   nondeterministic stages the outputs can vary on each execution, meaning the
   cache cannot be trusted for such stages.
 
-- `--downstream` - only run again the stages after the given `targets` in their
+- `--downstream` - only regenerate the stages after the given `targets` in their
   corresponding pipelines, including the target stages themselves.
 
 - `-h`, `--help` - prints the usage/help message, and exit.

static/docs/commands-reference/status.md

@@ -50,7 +50,7 @@ Data and pipelines are up to date.
 ```
 
 This indicates that no differences were detected, and therefore no stages would
-be run again by `dvc repro`.
+be regenerated by `dvc repro`.
 
 If instead, differences are detected, `dvc status` lists those changes. For each
 DVC-file (stage) with differences, the changes in _dependencies_ and/or

static/docs/tutorial/define-ml-pipeline.md

@@ -398,4 +398,4 @@ focus is DVC, not ML modeling and we use a relatively small dataset without any
 advanced ML techniques.
 
 In the next chapter we will try to improve the metrics by changing our modeling
-code and using reproducibility in our pipeline regeneration.
+code and using reproducibility in our pipeline.

static/docs/tutorial/reproducibility.md

@@ -86,7 +86,8 @@ Reproducing 'Dvcfile':
 
 The process started with the feature creation stage because one of its
 parameters was changed — the edited source code file `code/featurization.py`.
-All dependent stages were ran again as well.
+All dependent stages were regenerated as well. (See `--downstream` option in
+`dvc repro`.)
 
 Let’s take a look at the metric’s change. The improvement is close to zero
 (+0.0075% to be precise):