diff --git a/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md b/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md
index 0c87cc7598..49882e1044 100644
--- a/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md
+++ b/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md
@@ -16,8 +16,8 @@ well as any provider specific details that may be necessary.
  by using `spec.loadBalancerSourceRanges`. This field takes a list of IP CIDR ranges, which Kubernetes will use to configure firewall exceptions.
  This feature is currently supported on Google Compute Engine, Google Container Engine and AWS. This field will be ignored if the cloud provider does not support the feature.
 
- Assuming 10.0.0.0/8 is the internal subnet. In the following example, a load blancer will be created that is only accessible to cluster internal ips. 
- This will not allow clients from outside of your Kubernetes cluster to access the load blancer.
+ Assuming 10.0.0.0/8 is the internal subnet. In the following example, a load balancer will be created that is only accessible to cluster internal ips.
+ This will not allow clients from outside of your Kubernetes cluster to access the load balancer.
 
 ```yaml
 apiVersion: v1
@@ -35,7 +35,7 @@ spec:
   - 10.0.0.0/8
 ```
 
- In the following example, a load blancer will be created that is only accessible to clients with IP addresses from 130.211.204.1 and 130.211.204.2.
+ In the following example, a load balancer will be created that is only accessible to clients with IP addresses from 130.211.204.1 and 130.211.204.2.
 
 ```yaml
 apiVersion: v1