api: remove manual links to dvc.api

per #1305 (review)

content/docs/command-reference/list.md

@@ -21,7 +21,7 @@ DVC, by effectively replacing data files, models, directories with DVC-files
 files when you browse a <abbr>DVC repository</abbr> on Git hosting (e.g.
 Github), you just see the DVC-files. This makes it hard to navigate the project
 to find <abbr>data artifacts</abbr> for use with `dvc get`, `dvc import`, or
-[`dvc.api`](/doc/api-reference).
+`dvc.api`.
 
 `dvc list` prints a virtual view of a DVC repository, as if files and
 directories [tracked by DVC](/doc/use-cases/versioning-data-and-model-files)
@@ -48,7 +48,7 @@ list files recursively.
 
 Please note that `dvc list` doesn't check whether the listed data (tracked by
 DVC) actually exists in remote storage, so it's not guaranteed whether it can be
-accessed with `dvc get`, `dvc import`, or [`dvc.api`](/doc/api-reference)
+accessed with `dvc get`, `dvc import`, or `dvc.api`.
 
 ## Options
 

content/docs/use-cases/data-registries.md

@@ -88,8 +88,8 @@ $ dvc push
 ## Using registries
 
 The main methods to consume <abbr>data artifacts</abbr> from a **data registry**
-are the `dvc import` and `dvc get` commands, as well as the
-[`dvc.api`](/doc/api-reference) Python API.
+are the `dvc import` and `dvc get` commands, as well as the `dvc.api` Python
+API.
 
 But first, you may want to explore the contents of a data DVC repo.
 
@@ -164,9 +164,9 @@ the project dependency metadata in the import stage (DVC-file).
 
 ### Programmatic reusability of DVC data
 
-Our Python API, included with the `dvc` package installed with DVC, includes the
-`open` function to load/stream data directly from external <abbr>DVC
-projects</abbr>:
+Our [Python API](/doc/api-reference), included with the `dvc` package installed
+with DVC, includes the `open` function to load/stream data directly from
+external <abbr>DVC projects</abbr>:
 
 ```python
 import dvc.api.open