use-cases: new datasets registry case study, et al.

src/Documentation/RightPanel/RightPanel.js

@@ -140,7 +140,7 @@ export default class RightPanel extends React.PureComponent {
           <span role="img" aria-label="bug">
             🐛
           </span>{' '}
-          Found an issue? Let us know or fix it:
+          Found an issue? Let us know! Or fix it:
         </Description>
 
         <GithubButton href={githubLink} target="_blank">

src/Documentation/glossary.js

@@ -21,10 +21,20 @@ form part of your expanded workspace, technically.
       name: 'DVC Project',
       match: ['DVC project', 'project', 'projects'],
       desc: `
-Initialized by running \`dvc init\` in the **workspace**. It will contain the
+Initialized by running \`dvc init\` in the **workspace** (typically in a Git
+repository). It will contain the
 [\`.dvc/\` directory](/doc/user-guide/dvc-files-and-directories) and
 [DVC-files](/doc/user-guide/dvc-file-format) created with commands such as
-\`dvc add\` or \`dvc run\`. It's typically also a Git repository.
+\`dvc add\` or \`dvc run\`. It may also be a Git repository.
+      `
+    },
+    {
+      name: 'DVC Repository',
+      match: ['DVC repository', 'DVC repositories'],
+      desc: `
+**DVC project** initialized using \`dvc init\` in a Git repository. It will
+contain \`.git/\` and [\`.dvc/\`](/doc/user-guide/dvc-files-and-directories)
+directories, as well as any DVC-files created by DVC.
       `
     },
     {
@@ -37,14 +47,24 @@ For more details, please refer to this [document]
 (/doc/user-guide/dvc-files-and-directories#structure-of-cache-directory).
       `
     },
+    {
+      name: 'Output',
+      match: ['output', 'outputs'],
+      desc: `
+A file or a directory that is under DVC control, recorded in the \`outs\`
+section of a DVC-file. See \`dvc add\` \`dvc run\`, \`dvc import\`,
+\`dvc import-url\` commands. A.k.a. **data artifact*.
+      `
+    },
     {
       name: 'Data Artifact',
       match: ['data artifact', 'data artifacts'],
       desc: `
 Any data file or directory, as well as intermediate or final result (such as
 extracted features or a ML model file) that is under DVC control. Refer to
 [Versioning Data and Model Files]
-(/doc/use-cases/versioning-data-and-model-files) for more details.
+(/doc/use-cases/versioning-data-and-model-files) for more details. A.k.a
+**output*.
       `
     },
     {
@@ -55,14 +75,6 @@ Stage (DVC-file) created with the \`dvc import\` or \`dvc import-url\`
 commands. They represent files or directories from external sources.
       `
     },
-    {
-      name: 'Output',
-      match: ['output', 'outputs'],
-      desc: `
-A file or a directory that is under DVC control. See \`dvc add\` \`dvc run\`,
-\`dvc import\`, \`dvc import-url\` commands.
-      `
-    },
     {
       name: 'External Dependency',
       match: ['external dependency', 'external dependencies'],

src/Documentation/sidebar.json

@@ -96,7 +96,8 @@
         "label": "Sharing Data & Model Files",
         "slug": "sharing-data-and-model-files"
       },
-      "shared-development-server"
+      "shared-development-server",
+      "data-registry"
     ]
   },
   {

static/docs/changelog/0.18.md

@@ -43,5 +43,5 @@ really excited to share the progress with you:
 
 Please use the discussion forum [discuss.dvc.org](discuss.dvc.org) and
 [issue tracker]() and don't hesitate to [⭐](https://github.com/iterative/dvc)
-our [DVC repository](https://github.com/iterative/dvc) if you haven't yet. We
+the [DVC repository](https://github.com/iterative/dvc) if you haven't yet. We
 are waiting for your feedback!

static/docs/changelog/0.35.md

@@ -72,5 +72,5 @@ There are new [integrations and plugins](/doc/install/plugins) available:
   (PyCharm, IntelliJ, etc).
 
 Don't hesitate to
-[like\star DVC repository](https://github.com/iterative/dvc/stargazers) if you
+[star the DVC repository](https://github.com/iterative/dvc/stargazers) if you
 haven't yet. We are waiting for your feedback!

static/docs/command-reference/add.md

@@ -165,9 +165,7 @@ $ file .dvc/cache/d8/acabbfd4ee51c95da5d7628c7ef74b
 ```
 
 Note that tracking compressed files (e.g. ZIP or TAR archives) is not
-recommended, as `dvc add` supports tracking directories. (Details below.) For
-more context, refer to
-[Data Registry](/doc/use-cases/data-registry#problem-1-compressed-data-files)
+recommended, as `dvc add` supports tracking directories. (Details below.)
 
 ## Example: Directory
 
@@ -176,14 +174,14 @@ pictures. You may then have hundreds or thousands of pictures of these animals
 in a directory, and this is your training dataset:
 
 ```dvc
-$ tree pics
+$ tree pics --filelimit 3
 pics
 ├── train
-│   ├── cats        <-- A lot of images of cats
-│   └── dogs        <-- A lot of images of dogs
+│   ├── cats [many image files]
+│   └── dogs [many image files]
 └── validation
-    ├── cats        <-- More images of cats
-    └── dogs        <-- More images of dogs
+    ├── cats [more image files]
+    └── dogs [more image files]
 ```
 
 Taking a directory under DVC control as simple as with a single file:

static/docs/command-reference/cache/index.md

@@ -21,9 +21,9 @@ including the default cache directory.
 
 The cache is where your data files, models, etc (anything you want to version
 with DVC) are actually stored. The corresponding files you see in the
-<abbr>workspace</abbr> simply link to the ones in cache. (See
-`dvc config cache`, `type` config option, for more information on file links on
-different platforms.)
+<abbr>workspace</abbr> can simply link to the ones in cache. (Refer to
+[File link types](/doc/user-guide/large-dataset-optimization#file-link-types-for-the-dvc-cache)
+for more information on file links on different platforms.)
 
 > For more cache-related configuration options refer to `dvc config cache`.
 

static/docs/command-reference/destroy.md

@@ -17,9 +17,9 @@ usage: dvc destroy [-h] [-q | -v] [-f]
 be removed as well, unless it's set to an external location with
 `dvc cache dir`. (By default a local cache is located in the `.dvc/cache`
 directory.) If you were using
-[symlinks for linking data](/doc/user-guide/large-dataset-optimization) from the
+[symlinks for linking](/doc/user-guide/large-dataset-optimization) data from the
 cache, DVC will replace them with copies, so that your data is intact after the
-DVC repository destruction.
+project's destruction.
 
 ## Options
 

static/docs/command-reference/fetch.md

@@ -1,8 +1,7 @@
 # fetch
 
 Get files that are under DVC control from
-[remote](/doc/command-reference/remote#description) storage into the
-<abbr>cache</abbr>.
+[remote storage](/doc/command-reference/remote) into the <abbr>cache</abbr>.
 
 ## Synopsis
 
@@ -74,7 +73,7 @@ specified in DVC-files currently in the project are considered by `dvc fetch`
 ## Options
 
 - `-r REMOTE`, `--remote REMOTE` - name of the
-  [remote storage](/doc/command-reference/remote#description) to fetch from (see
+  [remote storage](/doc/command-reference/remote) to fetch from (see
   `dvc remote list`). If not specified, the default remote is used (see
   `dvc config core.remote`). The argument `REMOTE` is a remote name defined
   using the `dvc remote` command.
@@ -117,8 +116,7 @@ specified in DVC-files currently in the project are considered by `dvc fetch`
 ## Examples
 
 Let's employ a simple <abbr>workspace</abbr> with some data, code, ML models,
-pipeline stages, as well as a few Git tags, such as the <abbr>DVC project</abbr>
-created in our
+pipeline stages, as well as a few Git tags, such as our
 [get started example repo](https://github.com/iterative/example-get-started).
 Then we can see what happens with `dvc fetch` as we switch from tag to tag.
 

static/docs/command-reference/get-url.md

@@ -31,8 +31,8 @@ be placed inside of it.
 Note that this command doesn't require an existing DVC project to run in. It's a
 single-purpose command that can be used out of the box after installing DVC.
 
-> See `dvc get` to download data or model files or directories from other DVC
-> repositories (e.g. GitHub URLs).
+> See `dvc get` to download data or model files or directories from other
+> <abbr>DVC repository</abbr> (e.g. GitHub URLs).
 
 DVC supports several types of (local or) remote locations (protocols):
 

static/docs/command-reference/get.md

@@ -1,7 +1,8 @@
 # get
 
-Download or copy file or directory from any <abbr>DVC project</abbr> in a Git
-repository (e.g. hosted on GitHub) into the current working directory.
+Download or copy file or directory from the
+[remote storage](/doc/command-reference/remote) of any <abbr>DVC project</abbr>
+in a Git repository (e.g. hosted on GitHub) into the current working directory.
 
 > Unlike `dvc import`, this command does not track the downloaded data files
 > (does not create a DVC-file).
@@ -20,7 +21,8 @@ positional arguments:
 
 Provides an easy way to download datasets, intermediate results, ML models, or
 other files and directories (any <abbr>data artifact</abbr>) tracked in another
-DVC repository, by downloading them into the current working directory.
+<abbr>DVC repository</abbr>, by downloading them into the current working
+directory. (It works like `wget`, but for DVC repositories.)
 
 Note that this command doesn't require an existing DVC project to run in. It's a
 single-purpose command that can be used out of the box after installing DVC.

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

@@ -36,7 +36,7 @@ desired for the downloaded data. If an existing directory is specified, then the
 output will be placed inside of it.
 
 > See `dvc import` to download and tack data or model files or directories from
-> other DVC repositories (e.g. GitHub URLs).
+> other <abbr>DVC repositories</abbr> (e.g. GitHub URLs).
 
 DVC supports [DVC-files](/doc/user-guide/dvc-file-format) that refer to data in
 external locations, see