diff --git a/docs/quickstart.md b/docs/quickstart.md
index a3ea043c7568..777e41305288 100644
--- a/docs/quickstart.md
+++ b/docs/quickstart.md
@@ -24,8 +24,8 @@ $> make
 $> cd out
 $> sudo cp ./minikube /usr/local/bin  (on linux)
    sudo cp ./minikube-darwin-amd64 /usr/local/bin/minikube (on Mac)
-   
-   
+
+
 $> export LATEST_VERSION=$(curl -L -s -H 'Accept: application/json' https://github.com/machine-drivers/docker-machine-driver-vmware/releases/latest | sed -e 's/.*"tag_name":"\([^"]*\)".*/\1/') \
    && curl -L -o docker-machine-driver-vmware https://github.com/machine-drivers/docker-machine-driver-vmware/releases/download/$LATEST_VERSION/docker-machine-driver-vmware_darwin_amd64 \
    && chmod +x docker-machine-driver-vmware \
@@ -37,8 +37,8 @@ $> export LATEST_VERSION=$(curl -L -s -H 'Accept: application/json' https://gith
 To run clusterctl on vCenter, you must build the CLI from this repo.  The following instruction assumes $GOPATH is defined and $GOPATH/bin is in your current path.
 
 ```
-$> git clone https://github.com/kubernetes-sigs/cluster-api-provider-vsphere $GOPATH/src/sigs.k8s.io/cluster-api-provider-vsphere
-$> cd $GOPATH/src/sigs.k8s.io/cluster-api-provider-vsphere/clusterctl
+$> go get sigs.k8s.io/cluster-api-provider-vsphere
+$> cd $GOPATH/src/sigs.k8s.io/cluster-api-provider-vsphere/cmd/clusterctl
 $> go build && go install
 ```
 
@@ -54,7 +54,7 @@ The current cluster api components and clusterctl CLI assumes two preconditions:
 
 ### Prepare cluster definition files
 
-In *$GOPATH/src/sigs.k8s.io/cluster-api-provider-vsphere/clusterctl/examples/vsphere*, there are some example definition files. There is also a generate-yaml.sh file.  Run the generate script and copy the .template file to the same name without the .template extensions.
+In *$GOPATH/src/sigs.k8s.io/cluster-api-provider-vsphere/cmd/clusterctl/examples/vsphere*, there are some example definition files. There is also a generate-yaml.sh file.  Run the generate script and copy the .template file to the same name without the .template extensions.
 ```
 $> ./generate-yaml.sh
 $> cp cluster.yaml.template cluster.yaml
@@ -132,4 +132,4 @@ To delete an existing target cluster, we use the kubeconfig file created during
 $> clusterctl delete cluster --kubeconfig ./kubeconfig --cluster kubernetes -p provider-components.yaml --vm-driver vmware
 ```
 
-The workflow for deleting the cluster is very similar to the workflow for creating the cluster.  A bootstrap cluster is created using minikube.  The bootstrap cluster is used to then delete the target cluster.  On cleanup, the bootstrap cluster is removed.
\ No newline at end of file
+The workflow for deleting the cluster is very similar to the workflow for creating the cluster.  A bootstrap cluster is created using minikube.  The bootstrap cluster is used to then delete the target cluster.  On cleanup, the bootstrap cluster is removed.