diff --git a/examples/README.md b/examples/README.md
index a8fd7f0f1066..9cf11797f7d8 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -46,8 +46,7 @@ In case you want to follow along with this walkthrough, here's a quick overview
 argo submit hello-world.yaml    # submit a workflow spec to Kubernetes
 argo list                       # list current workflows
 argo get hello-world-xxx        # get info about a specific workflow
-argo logs -w hello-world-xxx    # get logs from all steps in a workflow
-argo logs hello-world-xxx-yyy   # get logs from a specific step in a workflow
+argo logs hello-world-xxx       # print the logs from a workflow
 argo delete hello-world-xxx     # delete workflow
 ```
 
@@ -66,7 +65,7 @@ kubectl delete wf hello-world-xxx
 
 Let's start by creating a very simple workflow template to echo "hello world" using the docker/whalesay container image from DockerHub.
 
-You can run this directly from your shell with a simple docker command:
+You can run this directly from your shell with a simple docker command:
 
 ```sh
 $ docker run docker/whalesay cowsay "hello world"
@@ -1521,4 +1520,4 @@ spec:
 
 Continuous integration is a popular application for workflows. Currently, Argo does not provide event triggers for automatically kicking off your CI jobs, but we plan to do so in the near future. Until then, you can easily write a cron job that checks for new commits and kicks off the needed workflow, or use your existing Jenkins server to kick off the workflow.
 
-A good example of a CI workflow spec is provided at https://github.com/argoproj/argo/tree/master/examples/influxdb-ci.yaml. Because it just uses the concepts that we've already covered and is somewhat long, we don't go into details here.
+A good example of a CI workflow spec is provided at https://github.com/argoproj/argo/tree/master/examples/influxdb-ci.yaml. Because it just uses the concepts that we've already covered and is somewhat long, we don't go into details here.
\ No newline at end of file