no issue # fix failing test to use selenium driver

[arvados.git] / doc / user / topics / running-pipeline-command-line.html.textile.liquid

diff --git a/doc/user/topics/running-pipeline-command-line.html.textile.liquid b/doc/user/topics/running-pipeline-command-line.html.textile.liquid
index c29584228267b6d9c9bb4cd82935ab18af8b837d..85d9188ff040edd55940b6164f94024143bf46ea 100644 (file)
--- a/doc/user/topics/running-pipeline-command-line.html.textile.liquid
+++ b/doc/user/topics/running-pipeline-command-line.html.textile.liquid
@@ -30,7 +30,7 @@ bwa-mem qr1hi-8i9sb-67n1qvsronmd2z6 49bae1066f4ebce72e2587a3efa61c7d+88
 </code></pre>
 </notextile>
 
-This instantiates your pipeline and displays a live feed of its status.  The new pipeline instance will also show up on Workbench dashboard.
+This instantiates your pipeline and displays a live feed of its status.  The new pipeline instance will also show up on the Workbench Dashboard.
 
 Arvados adds each pipeline component to the job queue as its dependencies are satisfied (or immediately if it has no dependencies) and finishes when all components are completed or failed and there is no more work left to do.