glossary: there's no pipelines tooltip yet

iterative · Jan 31, 2021 · 71cd972 · 71cd972
1 parent 184b60d
commit 71cd972
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/content/docs/command-reference/init.md b/content/docs/command-reference/init.md
@@ -118,8 +118,9 @@ include:
 - SCM other than Git is being used. Even though there are DVC features that
   require DVC to be run in the Git repo, DVC can work well with other version
   control systems. Since DVC relies on simple `dvc.yaml` files to manage
-  <abbr>pipelines</abbr>, data, etc, they can be added into any version control
-  system, thus providing large data files and directories versioning.
+  [pipelines](/doc/command-reference/dag), data, etc, they can be added into any
+  version control system, thus providing large data files and directories
+  versioning.
 
 - There is no need to keep the history at all, e.g. having a deployment
   automation like running a data pipeline using `cron`.

diff --git a/content/docs/command-reference/repro.md b/content/docs/command-reference/repro.md
@@ -69,7 +69,8 @@ files.
 
 Currently, `dvc repro` is not able to parallelize stage execution automatically.
 If you need to do this, you can launch `dvc repro` multiple times manually. For
-example, let's say a <abbr>pipeline</abbr> graph looks something like this:
+example, let's say a [pipelines](/doc/command-reference/dag) graph looks
+something like this:
 
 ```dvc
 $ dvc dag