this is redundant, also the tutorial contains more information anyway.
my suggestion is in install.html, under "Test the System", to just say something like:
Disco should be ready to use...
Head over to the Tutorial to see how to actually start running jobs on Disco.
If anything fails, see the section about Troubleshooting Disco installation.
Also, about the tutorial document, I suggest to put "Run a job" first on the page, because it doesn't rely on any of the other steps (preparing input data or writing functions), so users can test their setup by running a job right away.
I can implement changes like these if you agree with me.
If you have a specific way you think the docs should be improved, create a patch and open up a pull request. It's too complicated to make doc changes any other way than accepting / rejecting specific modifications. Also, since it's somewhat subjective area, others might not feel as motivated as you to make those changes, whereas if you feel strongly and submit a pull request it is more likely to be changed.