Issue title: Small corrections to episode 1
 Issue body: Hi, thanks for creating the tutorial. I am following along.

A few comments/corrections:

* You might like to mention that Docker has to be pre-installed before starting the tutorial. Otherwise you get this:

track:~$ minikube start
😄  minikube v1.15.1 on Darwin 11.0.1
👎  Unable to pick a default driver. Here is what was considered, in preference order:
    ▪ virtualbox: Not installed: unable to find VBoxManage in $PATH
    ▪ vmware: Not installed: exec: "docker-machine-driver-vmware": executable file not found in $PATH
    ▪ vmwarefusion: Not installed: vmrun path check: exec: "vmrun": executable file not found in $PATH
    ▪ docker: Not installed: exec: "docker": executable file not found in $PATH
    ▪ hyperkit: Not installed: exec: "hyperkit": executable file not found in $PATH
    ▪ parallels: Not installed: exec: "prlctl": executable file not found in $PATH
    ▪ podman: Not installed: exec: "podman": executable file not found in $PATH

❌  Exiting due to DRV_NOT_DETECTED: No possible driver was detected. Try specifying --driver, or see https://minikube.sigs.k8s.io/docs/start/

* "minikube halt" -> "minikube stop"

track:~$ minikube halt
Error: unknown command "halt" for "minikube"

* Missing final “.” from “docker build -t geerlingguy/kube101:intro”

Thanks,

Frank.

 Comments: 
 Comment 0: This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read [this blog post](https://www.jeffgeerling.com/blog/2020/enabling-stale-issue-bot-on-my-github-repositories) to see the reasons why I mark issues as stale.
 Comment 1: Not stale, just my reaction time is stale...
 Comment 2: This issue is no longer marked for closure.
 Comment 3: This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read [this blog post](https://www.jeffgeerling.com/blog/2020/enabling-stale-issue-bot-on-my-github-repositories) to see the reasons why I mark issues as stale.
 Comment 4: Gah!
 Comment 5: This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.
 Comment 6: Wait what? I put the `planned` label on it!
 Comment 7: This issue is no longer marked for closure.
 Comment 8: This issue is no longer marked for closure.
{'source': 'GithubIssues', 'repo_name_with_owner': 'geerlingguy/kubernetes-101', 'issue_id': 757948232, 'repo_stars': 404.0}