@@ -40,8 +40,8 @@ are taken under the hood:
40402 . Move the file contents to the cache, using the file hash to form the cached
4141 file path (see
4242 [ Structure of cache directory] ( /doc/user-guide/project-structure/internal-files#structure-of-the-cache-directory )
43- for details). Using the ` --out ` and ` --to-remote ` options with an external
44- target, the data is copied instead (to cache or remote storage).
43+ for details). Using ` --out ` , or ` --to-remote ` with an external target, the
44+ data is copied instead (to cache or remote storage).
45453 . Attempt to replace the file with a link to (or copy of) the cached data (more
4646 details on file linking ahead). A new link is created if a different ` --out `
4747 ` path ` is given. Skipped if ` --to-remote ` is used
@@ -339,7 +339,7 @@ $ tree .dvc/cache
339339Only the hash values of the `dir/` directory (with `.dir` file extension) and
340340` file2` have been cached.
341341
342- # # Example: Caching large data externally {#straight-to-cache}
342+ # # Example: Large data from an external location {#straight-to-cache}
343343
344344Sometimes you may want to add a large dataset currently found in an external
345345location, so it becomes local to the project. But what if there's not enough
@@ -379,7 +379,7 @@ outs:
379379> For a similar operation that actually keeps a connection to the data source,
380380> please see `dvc import-url`.
381381
382- # # Example: Storing large data remotely {#straight-to-remote}
382+ # # Example: Bootstrap external data tracking with remote storage {#straight-to-remote}
383383
384384Similarly to the previous scenario, you may sometimes want to add a large
385385dataset found externally into a regular <abbr>project</abbr> (with a local
0 commit comments