diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index bf703a95..a584b7f7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -19,8 +19,8 @@ We label issues with the ["good first issue" tag](https://github.com/reactiveops
The following commands are all required to pass as part of Fairwinds testing:
```
-go list ./ | grep -v vendor | xargs golint -set_exit_status
-go list ./ | grep -v vendor | xargs go vet
+go list ./... | grep -v vendor | xargs golint -set_exit_status
+go list ./... | grep -v vendor | xargs go vet
go test ./pkg/... -v -coverprofile cover.out
```
diff --git a/README.md b/README.md
index 88eb297b..f852eac2 100644
--- a/README.md
+++ b/README.md
@@ -2,14 +2,14 @@
@@ -33,11 +33,13 @@ helm upgrade --install fairwinds deploy/helm/fairwinds/ --namespace fairwinds
### Viewing the Dashboard
Once the dashboard is deployed, it can be viewed by using kubectl port-forward:
+
```
-kubectl port-forward --namespace fairwinds svc/fairwinds-fairwinds-dashboard 8080:80 &
-open http://localhost:8080
+kubectl port-forward --namespace fairwinds svc/fairwinds-fairwinds-dashboard 8080:80
```
+With the port forwarding in place, you can open http://localhost:8080 in your browser to view the dashboard.
+
### Using a Binary Release
If you'd prefer to run Fairwinds locally, binary releases are available on the [releases page](https://github.com/reactiveops/fairwinds/releases). When running as a binary, Fairwinds will use your local kubeconfig to connect to a cluster. There are a variety of options available, but the most common usage may be to view the dashboard: