diff --git a/content/docs/command-reference/fetch.md b/content/docs/command-reference/fetch.md index 460cc2b5a6..c9ba9a05ab 100644 --- a/content/docs/command-reference/fetch.md +++ b/content/docs/command-reference/fetch.md @@ -25,7 +25,7 @@ This makes them available for linking (or copying) into the workspace (refer to Without arguments, `dvc fetch` ensures that the files specified in all `dvc.lock` and `.dvc` files in the workspace exist in the cache. The `--all-branches`, `--all-tags`, and `--all-commits` options enable fetching data -for `dvc.lock`/`.dvc` files in multiple Git commits. +for multiple Git commits. The `targets` given to this command (if any) limit what to fetch. It accepts paths to tracked files or directories (including paths inside tracked diff --git a/content/docs/command-reference/status.md b/content/docs/command-reference/status.md index 0f09940c5f..969ba884aa 100644 --- a/content/docs/command-reference/status.md +++ b/content/docs/command-reference/status.md @@ -32,11 +32,11 @@ _remote_ mode is triggered by using the `--cloud` or `--remote` options: | remote | `--remote` | Comparisons are made between the cache, and the given remote. Remote storage is defined using the `dvc remote` command. | | remote | `--cloud` | Comparisons are made between the cache, and the default remote (typically defined with `dvc remote --default`). | -Without arguments, this command checks all stages (in `dvc.yaml`) and `.dvc` -files to compare the hash values of their outputs (in `dvc.lock`) -against the actual data files or directories in the workspace. The -`--all-branches`, `--all-tags`, and `--all-commits` options enable checking data -for multiple versions, not just the current branch. +Without arguments, this command checks all stages (defined in `dvc.yaml`) and +`.dvc` files, and compares the hash values of their outputs (found +in `dvc.lock` for stages) against the actual data files or directories in the +workspace. The `--all-branches`, `--all-tags`, and `--all-commits` options +enable checking data for multiple Git commits. The `targets` given to this command (if any) limit what to check. Paths to tracked files or directories (including paths inside tracked directories),