actually fix remaining detail sections broken due to #510

iterative · Aug 22, 2019 · d28add6 · d28add6
1 parent 6d642ef
commit d28add6
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 12 deletions.
diff --git a/static/docs/commands-reference/import-url.md b/static/docs/commands-reference/import-url.md
@@ -139,7 +139,7 @@ $ git checkout 2-remote
 $ mkdir data
 ```
 
-You should now have a blank <abbr>workspace</abbr>, just before the
+You should now have a blank workspace, just before the
 [Add Files](/doc/get-started/add-files) step.
 
 </details>

diff --git a/static/docs/get-started/configure.md b/static/docs/get-started/configure.md
@@ -24,7 +24,7 @@ project/repository itself.
 
 ```dvc
 $ dvc remote add -d myremote /tmp/dvc-storage
-$ git commit .dvc/config -m "initialize DVC local remote"
+$ git commit .dvc/config -m "Configure local remote"
 ```
 
 > We only use a local remote in this guide for simplicity's sake in following

diff --git a/static/docs/get-started/example-pipeline.md b/static/docs/get-started/example-pipeline.md
@@ -108,10 +108,9 @@ of the data file itself.
 
 Actual data file `Posts.xml.zip` is linked into the `.dvc/cache` directory,
 under the `.dvc/cache/ce/68b98d82545628782c66192c96f2d2` name and is added to
-`.gitignore`. Even if you remove it in the <abbr>workspace</abbr>, or checkout a
-different branch/commit the data is not lost if a corresponding DVC-file is
-committed. It's enough to run `dvc checkout` or `dvc pull` to restore data
-files.
+`.gitignore`. Even if you remove it in the workspace, or checkout a different
+branch/commit the data is not lost if a corresponding DVC-file is committed.
+It's enough to run `dvc checkout` or `dvc pull` to restore data files.
 
 </details>
 
@@ -161,11 +160,10 @@ outs:
     path: data/Posts.xml
 ```
 
-This file is using the same technique (checksums that point to to the
-<abbr>cache</abbr>) to describe and version control dependencies and outputs.
-Output `Posts.xml` file is automatically added to the `.gitignore` file and a
-link is created into a cache `.dvc/cache/a3/04afb96060aad90176268345e10355` to
-save it.
+This file is using the same technique (checksums that point to to the cache) to
+describe and version control dependencies and outputs. Output `Posts.xml` file
+is automatically added to the `.gitignore` file and a link is created into a
+cache `.dvc/cache/a3/04afb96060aad90176268345e10355` to save it.
 
 Two things are worth noticing here. First, by analyzing dependencies and outputs
 that DVC-files describe, we can restore the full chain (DAG) of commands we need

diff --git a/static/docs/get-started/initialize.md b/static/docs/get-started/initialize.md
@@ -19,7 +19,7 @@ and directories:
 
 ```dvc
 $ dvc init
-$ git commit -m "initialize DVC"
+$ git commit -m "Initialize DVC project"
 ```
 
 After DVC initialization, a new directory `.dvc/` will be created with `config`