diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md
index 36febaa30c..eb33879473 100644
--- a/content/en/docs/concepts/services-networking/service.md
+++ b/content/en/docs/concepts/services-networking/service.md
@@ -688,7 +688,7 @@ In the above example, if the Service contained three ports, `80`, `443`, and
 be proxied HTTP.
 
 From Kubernetes v1.9 onwrds you can use [predefined AWS SSL policies](http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-security-policy-table.html) with HTTPS or SSL listeners for your Services.
-To see which policies are available for use, you can the `aws` command line tool:
+To see which policies are available for use, you can use the `aws` command line tool:
 
 ```bash
 aws elb describe-load-balancer-policies --query 'PolicyDescriptions[].PolicyName'
diff --git a/content/en/docs/concepts/workloads/pods/init-containers.md b/content/en/docs/concepts/workloads/pods/init-containers.md
index d6c03abbea..309a8bfad5 100644
--- a/content/en/docs/concepts/workloads/pods/init-containers.md
+++ b/content/en/docs/concepts/workloads/pods/init-containers.md
@@ -215,7 +215,7 @@ kubectl logs myapp-pod -c init-mydb      # Inspect the second init container
 ```
 
 At this point, those init containers will be waiting to discover Services named
-`mydb` and `myservices`.
+`mydb` and `myservice`.
 
 Here's a configuration you can use to make those Services appear: