fix tests

Signed-off-by: Patrik Cyvoct <patrik@ptrk.io>

keps/sig-network/20191205-kube-proxy-IP-node-binding.md

@@ -4,7 +4,7 @@ authors:
   - "@Sh4d1"
 owning-sig: sig-network
 participating-sigs:
-  - sig-cloudprovider
+  - sig-cloud-provider
 reviewers:
   - "@thockin"
   - "@cheftako"
@@ -51,7 +51,7 @@ There are numerous problems with the current behaviour:
 1. Some cloud provider (Scaleway, ...) are sometimes using the LB's external IP as source IP when sending packets to the cluster. This is a probem in the ipvs mode of kube proxy since the IP is bouded to an interface and healtchecks from the LB are never coming back.
 2. Some cloud provider (DigitalOcean, Scaleway, ...) are also having features at the LB level (TLS termination, PROXY protocol, ...) and bypassing the LB means missing these features when the packet arrives to the service (leading to protocols errors).
 
-So giving an options to these cloud to disable the actual beahviour would be very valuable.
+So giving an options to these cloud to disable the actual behaviour would be very valuable.
 
 Currently there is some hacky workaround that set the `Hostname` on the `Service` in order to bypass kube proxy binding (AWS and DigitalOcean for instance), but as stated, it's a bit hacky. This KEP should also give a solution to this hack.