Merge branch '2.0-rc2' into developer-guide-build-image-section

Author: alai8

site/developer.md

@@ -99,20 +99,21 @@ $ scp operator.tar YOUR_USER@YOUR_SERVER:/some/path/operator.tar
 $ docker load < /some/path/operator.tar
 ```
 
-Use the Helm charts to [install the operator](helm-charts.md).
+Use the Helm charts to [install the operator](install.md).
 
-If the operator's behavior or pod log is insufficient to diagnose and resolve failures, then you can connect a Java debugger to the operator using the [debugging options](helm-charts.md#debugging-options).
+If the operator's behavior or pod log is insufficient to diagnose and resolve failures, then you can connect a Java debugger to the operator using the [debugging options](install.md#debugging-options).
 
 ## Running integration tests
 
 The project includes integration tests that can be run against a Kubernetes cluster.  If you want to use these tests, you will need to provide your own Kubernetes cluster.  The Kubernetes cluster must meet the version number requirements and have Helm installed.  Ensure that the operator Docker image is in a Docker registry visible to the Kubernetes cluster.
 
 
-You will need to obtain the `kube.config` file for an administrative user and make it available on the machine running the build.  To run the tests, update the `KUBECONFIG` environment varaible to point to your config file and then execute:
+You will need to obtain the `kube.config` file for an administrative user and make it available on the machine running the build.  To run the tests, update the `KUBECONFIG` environment variable to point to your config file and then execute:
 
 ```
 $ mvn clean verify -P java-integration-tests
 ```
+**NOTE**: When you run the integrations tests, they do a cleanup of any operator or domains on that cluster.   
 
 ## Coding standards