ref: remove wrong info about import* to-cache

per #2302 (review)

content/docs/command-reference/import-url.md

@@ -48,9 +48,7 @@ similar to using `dvc add` after downloading the data. It saves the information
 about the data source, so the import can be updated later if the data source has
 changed (see `dvc update`).
 
-💡 Using an
-[external cache](/doc/use-cases/shared-development-server#configure-the-external-shared-cache)
-or the `--to-remote` option lets you
+💡 Using the `--to-remote` option lets you
 [transfer](#example-transfer-to-remote-storage) an import without using the
 local file system.
 
@@ -368,10 +366,7 @@ Normally, `dvc import-url` downloads the target data (to the <abbr>cache</abbr>)
 in order to link and track it locally. But what if there's not enough disk space
 for the download?
 
-One option is to setup an
-[external cache](/doc/use-cases/shared-development-server#configure-the-external-shared-cache)
-in a location that can handle the data. Another is to use the `--to-remote`
-option so the target data is transferred to
+You can use the `--to-remote` option so the target data is transferred to
 [remote storage](/doc/command-reference/remote), while also tracked via an
 import `.dvc` file in the project.
 

content/docs/command-reference/import.md

@@ -38,11 +38,6 @@ working directory with its original file name e.g. `data.txt` (or to a location
 provided with `--out`). An _import `.dvc` file_ is created in the same location
 e.g. `data.txt.dvc` – similar to using `dvc add` after downloading the data.
 
-💡 Using an
-[external cache](/doc/use-cases/shared-development-server#configure-the-external-shared-cache)
-lets you transfer an import there (and link it in the <abbr>workspace</abbr>),
-without using the local file system.
-
 (ℹ️) DVC won't push or pull data imported from other DVC repos to/from
 [remote storage](/doc/command-reference/remote), it will rely on the original
 source instead.