Merge pull request #796 from oracle/edits

incorporate edits

Author: rjeberhard

site/developer.md

@@ -93,11 +93,12 @@ If the operator's behavior or pod log is insufficient to diagnose and resolve fa
 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
 

site/scaling.md

@@ -77,7 +77,7 @@ When you POST to the `/scale` REST endpoint, you must send the following headers
 For example, when using `curl`:
 
 ```
-curl -v -k -H X-Requested-By:MyClient -H Content-Type:application/json -H Accept:application/json -H "Authorization:Bearer ..." -d { "managedServerCount": 3 } https:/.../scaling
+curl -v -k -H X-Requested-By:MyClient -H Content-Type:application/json -H Accept:application/json -H "Authorization:Bearer ..." -d '{ "managedServerCount": 3 }' https://.../scaling
 ```
 
 If you omit the header, you'll get a `400 (bad request)` response without any details explaining why the request was bad.  If you omit the Bearer Authentication header, then you'll get a `401 (Unauthorized)` response.