Fixed link to "How does DVC track experiments" (#4013)

iterative · Oct 3, 2022 · f293231 · f293231
1 parent 8a8fb8d
commit f293231
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 6 deletions.
diff --git a/content/docs/command-reference/exp/gc.md b/content/docs/command-reference/exp/gc.md
@@ -15,8 +15,9 @@ usage: dvc exp gc [-h] [-q | -v] [-w]
 This command can delete (garbage collect) experiments that exist in the project
 but are no longer needed.
 
-> See **How does DVC track experiments?** in `dvc exp run` to learn more about
-> DVC experiment storage.
+> See
+> [**How does DVC track experiments?**](/doc/user-guide/experiment-management/experiments-overview#how-does-dvc-track-experiments)
+> in **DVC Experiments Overview** to learn more about DVC experiment storage.
 
 To avoid accidentally deleting work, `dvc exp gc` doesn't do anything unless one
 or a combination of scope options are provided (`--workspace`, `--all-branches`,

diff --git a/content/docs/command-reference/exp/pull.md b/content/docs/command-reference/exp/pull.md
@@ -23,8 +23,9 @@ experiments] across <abbr>repository</abbr> copies via Git and DVC remotes.
 [sharing experiments]: /doc/user-guide/experiment-management/sharing-experiments
 
 > Plain `git push` and `git fetch` don't work with experiments because these are
-> saved under custom Git references. See **How does DVC track experiments?** in
-> `dvc exp run` to learn more about DVC experiment storage.
+> saved under custom Git references. See
+> [**How does DVC track experiments?**](/doc/user-guide/experiment-management/experiments-overview#how-does-dvc-track-experiments)
+> in **DVC Experiments Overview** to learn more about DVC experiment storage.
 
 A working `git_remote` name (e.g. `origin`) or Git URL is required, as well as
 one or more `experiment` names or hashes (see `dvc exp run`) to pull.

diff --git a/content/docs/command-reference/exp/push.md b/content/docs/command-reference/exp/push.md
@@ -23,8 +23,9 @@ experiments] across <abbr>repository</abbr> copies via Git and DVC remotes.
 [sharing experiments]: /doc/user-guide/experiment-management/sharing-experiments
 
 > Plain `git push` and `git fetch` don't work with experiments because these are
-> saved under custom Git references. See **How does DVC track experiments?** in
-> `dvc exp run` to learn more about DVC experiment storage.
+> saved under custom Git references. See
+> [**How does DVC track experiments?**](/doc/user-guide/experiment-management/experiments-overview#how-does-dvc-track-experiments)
+> in **DVC Experiments Overview** to learn more about DVC experiment storage.
 
 A working `git_remote` name (e.g. `origin`) or Git URL is required, as well as
 one or more `experiment` names or hashes (see `dvc exp run`) to push.