Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restyle start: Data Access and Data Versioning to mention Model in titles (#2096) #2231

Merged
merged 1 commit into from
Feb 24, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions content/docs/start/data-and-model-versioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -249,13 +249,13 @@ the <abbr>workspace</abbr> efficiently to match them.

## Model versioning

DVC helps you handle model files as well. Models in a
project usually change more frequently than data files and they need to be kept
in sync with changes in other elements of a project. Model files are no
different than data files when it comes to tracking their versions. DVC also
provides means to track minor changes in model files without fully checking in
to underlying VCS. In later sections of this series, you'll see how DVC enables
to track changes in pipelines consisting of multiple model and data files.
DVC helps you handle model files as well. Models in a project usually change
more frequently than data files and they need to be kept in sync with changes in
other elements of a project. Model files are no different than data files when
it comes to tracking their versions. DVC also provides means to track minor
changes in model files without fully checking in to underlying VCS. In later
sections of this series, you'll see how DVC enables to track changes in
pipelines consisting of multiple model and data files.

## Large datasets versioning

Expand Down