cmd: document target granularity for push/pull/etc, et al.

content/docs/command-reference/pull.md

@@ -55,6 +55,9 @@ dependencies backward from the target [stage files](/doc/command-reference/run),
 through the corresponding [pipelines](/doc/command-reference/pipeline), to find
 data files to pull.
 
+If `targets` are files/directories tracked by DVC, DVC will download cache for
+them, skipping the rest.
+
 After a data file is in cache, `dvc pull` can use OS-specific mechanisms like
 reflinks or hardlinks to put it in the workspace without copying. See
 `dvc checkout` for more details.

content/docs/command-reference/push.md

@@ -71,6 +71,9 @@ with them. Using the `--with-deps` option, DVC tracks dependencies backward from
 the target [stage files](/doc/command-reference/run), through the corresponding
 [pipelines](/doc/command-reference/pipeline), to find data files to push.
 
+If `targets` are files/directories tracked by DVC, DVC will download cache for
+them skipping the rest.
+
 ## Options
 
 - `-a`, `--all-branches` - determines the files to upload by examining

content/docs/command-reference/status.md

@@ -45,8 +45,11 @@ only, by listing them as `targets`. (Changes are reported only against these.)
 When this is combined with the `--with-deps` option, a search is made for
 changes in other stages that affect each target.
 
+In the remote mode, if `targets` are files/directories tracked by DVC, DVC will
+only compare the cache for them, skipping the rest.
+
 In the local mode, changes are detected through the hash value of every file
-listed in every stage (in `dvc.yaml` or `.dvc` files) in question against the
+listed in every stage (in `dvc.yaml`) or `.dvc` files in question against the
 corresponding file in the file system. The command output indicates the detected
 changes, if any. If no differences are detected, `dvc status` prints this
 message: