cmd ref: remove "(s)" and similar from command sample outputs...

Per changes in iterative/dvc#2281
and iterative/dvc#2299

static/docs/commands-reference/commit.md

@@ -213,7 +213,7 @@ execute this set of commands:
 ```dvc
 $ dvc commit
 $ dvc status
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 $ ls .dvc/cache/70
 599f166c2098d7ffca91a369a78b0d
 ```
@@ -275,7 +275,7 @@ Are you sure you commit it? [y/n] y
 
 $ dvc status
 
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 Nothing special is required, we simply `commit` to both the SCM and DVC. Since

static/docs/commands-reference/fetch.md

@@ -309,4 +309,4 @@ the workspace (with `dvc repro train.dvc`).
 > Note that in this sample project, the last stage file `evaluate.dvc` doesn't
 > add any more data files than those form previous stages so at this point all
 > of the files for this pipeline are in local cache and `dvc status -c` would
-> output `Pipeline(s) is (are) up to date.`
+> output `Pipelines are up to date.`

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

@@ -348,7 +348,7 @@ $ tree
 3 directories, 10 files
 
 $ dvc status
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 Then in the data store directory, edit `data.xml`. It doesn't matter what you
@@ -396,7 +396,7 @@ $ git commit -a -m "updated data"
  2 files changed, 6 insertions(+), 6 deletions(-)
 
 $ dvc status
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 Because the external data source for the data file changed, the change was

static/docs/commands-reference/install.md

@@ -174,7 +174,7 @@ $ dvc checkout
 
 $ dvc status
 
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 After running `git checkout` we are also shown a message saying _You are in
@@ -231,7 +231,7 @@ HEAD is now at d13ba9a add featurization stage
 
 $ dvc status
 
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 Look carefully at this output and it is clear that the `dvc checkout` command
@@ -280,7 +280,7 @@ $ git status -s
 
 $ git commit -a -m "updated data after modified featurization"
 
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 
 [master 78d0c44] modified featurization
  5 files changed, 12 insertions(+), 12 deletions(-)
@@ -289,5 +289,5 @@ Pipeline(s) is (are) up to date. Nothing to reproduce.
 After reproducing this pipeline up to the "evaluate" stage, the data files are
 in sync with the code/config files, but we must now commit the changes to the
 Git repository. Looking closely we see that `dvc status` is run again, informing
-us that the data files are synchronized with the
-`Pipeline(s) is (are) up to date.` message.
+us that the data files are synchronized with the `Pipelines are up to date.`
+message.

static/docs/commands-reference/pipeline_list.md

@@ -38,5 +38,5 @@ raw.dvc
 data.dvc
 output.dvc
 ======================================================================
-2 pipeline(s) total
+2 pipelines total
 ```

static/docs/commands-reference/push.md

@@ -199,7 +199,7 @@ Everything is up to date.
 
 $ dvc status --cloud
 
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 With the first `dvc push` we specified a stage in the middle of this pipeline
@@ -336,7 +336,7 @@ $ tree ../vault/recursive
 
 $ dvc status --cloud
 
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 And running `dvc status --cloud` verifies that indeed there are no more files to

static/docs/commands-reference/repro.md

@@ -176,7 +176,7 @@ $ dvc repro
 WARNING: assuming default target 'Dvcfile'.
 Stage 'filter.dvc' didn't change.
 Stage 'Dvcfile' didn't change.
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 It makes sense, since we haven't changed neither of the dependencies this
@@ -225,7 +225,7 @@ Now, using the `--downstream` option results in the following output:
 $ dvc repro --downstream
 WARNING: assuming default target 'Dvcfile'.
 Stage 'Dvcfile' didn't change.
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 The reason being that the `text.txt` is a file which is a dependency in the

static/docs/commands-reference/status.md

@@ -45,7 +45,7 @@ detected, `dvc status` prints this message:
 
 ```dvc
 $ dvc status
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 ```
 
 This says that no differences were detected, and therefore that no stages would
@@ -109,7 +109,7 @@ cache. For the typical process to update workspaces, see
 - `-h`, `--help` - prints the usage/help message, and exit.
 
 - `-q`, `--quiet` - do not write anything to standard output. Exit with 0 if
-  pipeline(s) is (are) up to date, otherwise 1.
+  Pipelines are up to date, otherwise 1.
 
 - `-v`, `--verbose` - displays detailed tracing information.
 
@@ -139,7 +139,7 @@ $ vi code/featurization.py
 ... edit the code
 
 $ dvc status model.p.dvc
-Pipeline(s) is (are) up to date. Nothing to reproduce.
+Pipelines are up to date. Nothing to reproduce.
 
 $ dvc status model.p.dvc --with-deps
 matrix-train.p.dvc