diff --git a/content/docs/user-guide/project-structure/pipelines-files.md b/content/docs/user-guide/project-structure/pipelines-files.md
index f4b7790f21..636e8b8314 100644
--- a/content/docs/user-guide/project-structure/pipelines-files.md
+++ b/content/docs/user-guide/project-structure/pipelines-files.md
@@ -252,12 +252,14 @@ each stage name after a `@`. The final stages generated by the `foreach` syntax
 are saved to `dvc.lock`:
 
 ```yaml
-cleanups@raw2 labels2:
-  cmd: echo "raw2 labels2"
-cleanups@raw1:
-  cmd: echo "raw1"
-cleanups@labels1:
-  cmd: echo "labels1"
+schema: '2.0'
+stages:
+  cleanups@raw2 labels2:
+    cmd: echo "raw2 labels2"
+  cleanups@raw1:
+    cmd: echo "raw1"
+  cleanups@labels1:
+    cmd: echo "labels1"
 ```
 
 For lists containing complex values (e.g. dictionaries), the substitution
@@ -278,6 +280,7 @@ stages:
 
 ```yaml
 # dvc.lock
+schema: '2.0'
 stages:
   train@0:
     cmd: python train.py 3 10
@@ -307,11 +310,14 @@ stages:
 
 ```yaml
 # dvc.lock
+schema: '2.0'
 stages:
   build@uk:
     cmd: python train.py 'uk' 3 10
     outs:
-      - model-uk.hdfs
+      - path: model-uk.hdfs
+        md5: 17b3d1efc339b416c4b5615b1ce1b97e
+        size: 2712300
   build@us: ...
 ```
 
@@ -385,6 +391,7 @@ DVC will maintain a `dvc.lock` file for each `dvc.yaml`. Their purposes include:
 Here's an example:
 
 ```yaml
+schema: '2.0'
 stages:
   features:
     cmd: jupyter nbconvert --execute featurize.ipynb