Misc. updates (2.0ish)

content/blog/2020-04-06-april-20-dvc-heartbeat.md

@@ -15,12 +15,11 @@ descriptionLong: |
   science.
 picture: 2020-04-06/april_header.png
 pictureComment:
-  A view from [Barrancas del
-  Cobre](https://en.wikipedia.org/wiki/Copper_Canyon), shot by Jorge Orpinel
-  Pérez. Jorge has mastered the art of working on DVC remotely.
-author: elle_obrien
-commentsUrl: https://discuss.dvc.org/t/april-20-heartbeat/347
-tags:
+  A view from
+  [Barrancas del Cobre](https://en.wikipedia.org/wiki/Copper_Canyon), shot by
+  Jorge Orpinel Pérez. Jorge has mastered the art of working on DVC remotely.
+  author: elle_obrien commentsUrl:
+  https://discuss.dvc.org/t/april-20-heartbeat/347 tags:
   - Heartbeat
   - Google Drive
   - MLOps

content/docs/command-reference/plots/index.md

@@ -125,8 +125,8 @@ All metrics files given to `dvc plots show` and `dvc plots diff` as input are
 combined together into a single data array for injection into a template file.
 There are two important fields that DVC adds to the plot data:
 
-- `index` - self-incrementing, zero-based counter for the data rows/values. In
-  many cases it corresponds to a machine learning training epoch or step number.
+- `index` - zero-based counter for the data rows/values. In many cases it
+  corresponds to a machine learning training epoch or step number.
 
 - `rev` - Git commit hash, tag, or branch of the metrics file. This helps
   distinguish between different versions when using the `dvc plots diff`

content/docs/user-guide/dvc-files.md

@@ -143,9 +143,12 @@ stages:
     metrics:
       - performance.json
   training:
-    desc: Training stage description
-    cmd: python train.py
+    desc: Train model with Python
+    cmd:
+      - pip install -r requirements.txt
+      - python train.py --out ${model_file}
     deps:
+      - requirements.txt
       - train.py
       - features
     outs:
@@ -207,8 +210,8 @@ For every `dvc.yaml` file, a matching `dvc.lock` (YAML) file usually exists.
 It's created or updated by DVC commands such as `dvc run` and `dvc repro`.
 `dvc.lock` describes the latest pipeline state. It has several purposes:
 
-- Tracking of intermediate and final results of a pipeline — similar to
-  [`.dvc` files](#dvc-files).
+- Tracking of intermediate and final <abbr>outputs</abbr> of a pipeline —
+  similar to [`.dvc` files](#dvc-files).
 - Allow DVC to detect when stage definitions, or their dependencies have
   changed. Such conditions invalidate stages, requiring their reproduction (see
   `dvc status`, `dvc repro`).