bulleted points end with : or .

static/docs/commands-reference/fetch.md

@@ -100,7 +100,7 @@ specified in DVC-files currently in the workspace are considered by `dvc fetch`
   of a DVC-file ([experiments](/doc/get-started/experiments)), not just the
   current one.
 
-- `-T`, `--all-tags` - fetch cache for all tags. Similar to `-a` above
+- `-T`, `--all-tags` - fetch cache for all tags. Similar to `-a` above.
 
 - `--show-checksums` - show checksums instead of file names when printing the
   download progress.

static/docs/commands-reference/import-url.md

@@ -23,10 +23,10 @@ In some cases it's convenient to add a data file or directory from a remote
 location into the workspace, such that it will be automatically updated (by
 `dvc repro`) when the external data source changes. Examples:
 
-- a remote system may produce occasional data files that are used in other
-  projects;
-- a batch process running regularly updates a data file to import; and
-- a shared dataset on a remote storage that is managed and updated outside DVC.
+- A remote system may produce occasional data files that are used in other
+  projects.
+- A batch process running regularly updates a data file to import.
+- A shared dataset on a remote storage that is managed and updated outside DVC.
 
 The `dvc import-url` command helps the user create such an external data
 dependency. The `url` argument specifies the external location of the data to be

static/docs/commands-reference/index.md

@@ -1,17 +1,17 @@
 # Using DVC Commands
 
-DVC is a command-line tool. The typical use case for DVC goes as follows
+DVC is a command-line tool. The typical use case for DVC goes as follows:
 
-- In an existing Git repository, initialize a DVC repository with `dvc init`,
+- In an existing Git repository, initialize a DVC repository with `dvc init`.
 - Copy source code files for modeling into the repository and convert the files
-  into DVC data files with `dvc add` command;
+  into DVC data files with `dvc add` command.
 - Process raw data files through your data processing and modeling code using
-  the `dvc run` command;
+  the `dvc run` command.
 - Use `--outs` option to specify `dvc run` command outputs which will be
-  converted to DVC data files after the code runs;
+  converted to DVC data files after the code runs.
 - Clone a git repo with the code of your ML application pipeline. However, this
   will not copy your DVC cache. Use
   [data remotes](/doc/commands-reference/remote) and `dvc push` to share the
-  cache (data);
+  cache (data).
 - Use `dvc repro` to quickly reproduce your pipeline on a new iteration, after
   your data item files or source code of your ML application are modified.

static/docs/commands-reference/install.md

@@ -46,9 +46,9 @@ The installed Git hook automates executing `dvc push`.
 ## Installed Git hooks
 
 - Git `pre-commit` hook executes `dvc status` before `git commit` to inform the
-  user about the workspace status;
+  user about the workspace status.
 - Git `post-checkout` hook executes `dvc checkout` after `git checkout` to
-  automatically synchronize the data files with the new workspace state;
+  automatically synchronize the data files with the new workspace state.
 - Git `pre-push` hook executes `dvc push` before `git push` to upload files and
   directories under DVC control to remote.
 

static/docs/commands-reference/pull.md

@@ -200,4 +200,3 @@ the `model.p.dvc` stage occurs later, its data was not pulled.
 Then we ran `dvc pull` specifying the last stage, `model.p.dvc`, and its data
 was downloaded. Finally, we ran `dvc pull` with no options to make sure that all
 data was already pulled with the previous commands.
-

static/docs/commands-reference/push.md

@@ -339,4 +339,3 @@ Pipelines are up to date. Nothing to reproduce.
 
 And running `dvc status --cloud` verifies that indeed there are no more files to
 upload to the remote cache.
-

static/docs/commands-reference/run.md

@@ -58,7 +58,7 @@ pipeline.
   dependencies can be specified like this: `-d data.csv -d process.py`. Usually,
   each dependency is a file or a directory with data, or a code file, or a
   configuration file. DVC also supports certain
-  [external dependencies](/doc/user-guide/external-dependencies)
+  [external dependencies](/doc/user-guide/external-dependencies).
 
   DVC builds a computation graph and this list of dependencies is a way to
   connect different stages with each other. When you run `dvc repro` to

static/docs/commands-reference/unprotect.md

@@ -29,10 +29,10 @@ on this process.
 
 `dvc unprotect` can be an expensive operation (involves copying data), check
 first whether your task matches one of the cases that are considered safe, even
-when cache protected mode is enabled:
+when cache protected mode is enabled by:
 
-- Adding more files to a directory input data set (say, images or videos)
-- Deleting files from a directory data set
+- Adding more files to a directory input data set (say, images or videos).
+- Deleting files from a directory data set.
 
 ## Options
 

static/docs/commands-reference/version.md

@@ -125,3 +125,4 @@ Platform: Linux-4.15.0-50-generic-x86_64-with-debian-buster-sid
 Binary: False
 Filesystem type (workspace): ('ext4', '/dev/sdb3')
 ```
+

static/docs/get-started/agenda.md

@@ -29,9 +29,9 @@ datasets, etc., then you may want to:
 - Capture and save those <abbr>data artifacts</abbr> the same way we capture
   code
 - Track and switch between different versions of the data easily
-- Being able to answer the question of how data artifacts (e.g. ML models) were
+- Be able to answer the question of how data artifacts (e.g. ML models) were
   built in the first place
-- Being able to compare them
+- Be able to compare them
 - Bring best practices to your team and get everyone on the same page
 
 Then you are in a good place! Click the `Next` button below to start ↘

static/docs/user-guide/dvc-files-and-directories.md

@@ -5,8 +5,14 @@ Once initialized in a project, DVC populates its installation directory
 
 ### Special DVC internal files and directories
 
-`.dvc/config` - this is a configuration file. The config file can be edited by
-hand or with a special command: `dvc config`.
+- `.dvc/config` - this is a configuration file. The config file can be edited by
+  hand or with a special command: `dvc config`.
+
+- `.dvc/config.local` - this is a local configuration file, that will overwrite
+  options in `.dvc/config`. This is useful when you need to specify private
+  options in your config that you don't want to track and share through Git
+  (credentials, private locations, etc). The local config file can be edited by
+  hand or with a special command: `dvc config --local`.
 
 - `.dvc/cache` - the [cache directory](#structure-of-cache-directory) will
   contain your data files. (The data directories of DVC repositories will only
@@ -19,22 +25,22 @@ hand or with a special command: `dvc config`.
   > the Git repository, only [DVC-files](/doc/user-guide/dvc-file-format) that
   > are needed to reproduce them.
 
-`.dvc/state` - this file is used for optimization. It is a SQLite db, that
-contains checksums for files in a project with respective timestamps and
-inodes to avoid unnecessary checksum computations. It also contains a list of
-links (from cache to workspace) created by dvc and is used to cleanup your
-workspace when calling `dvc checkout`.
+- `.dvc/state` - this file is used for optimization. It is a SQLite db, that
+  contains checksums for files in a project with respective timestamps and
+  inodes to avoid unnecessary checksum computations. It also contains a list of
+  links (from cache to workspace) created by dvc and is used to cleanup your
+  workspace when calling `dvc checkout`.
 
-`.dvc/state-journal` - temporary file for SQLite operations
+- `.dvc/state-journal` - temporary file for SQLite operations
 
-`.dvc/state-wal` - another SQLite temporary file
+- `.dvc/state-wal` - another SQLite temporary file
 
-`.dvc/updater` - this file is used store latest available version of dvc,
-which is used to remind user to upgrade.
+- `.dvc/updater` - this file is used store latest available version of dvc,
+  which is used to remind user to upgrade.
 
-`.dvc/updater.lock` - a lock file for `.dvc/updater`.
+- `.dvc/updater.lock` - a lock file for `.dvc/updater`.
 
-`.dvc/lock` - a lock file for the whole dvc project.
+- `.dvc/lock` - a lock file for the whole dvc project.
 
 ## Structure of cache directory