Lab Documents Should Explain How To Verify If Things Are Working as Expected
One of the frustrations I'm finding with this class so far (Lab 2) is that we'll be told in the lab to run a command like:
**docker ps **
but the lab documents ought to include a screenshot or output example clearly explaining what we ought to be seeing if things are working correctly before moving on.
I'd also suggest that PDF's are just a terrible format for this type of class and students are wasting an incredible amount of time doing things like getting their YAML indented again after Adobe wrecks it.