Merge remote-tracking branch 'upstream/master' into dev-1.19

content/en/docs/concepts/services-networking/_index.md

@@ -1,5 +1,12 @@
 ---
 title: "Services, Load Balancing, and Networking"
 weight: 60
+description: >
+  Concepts and resources behind networking in Kubernetes.
 ---
 
+Kubernetes networking addresses four concerns:
+- Containers within a Pod use networking to communicate via loopback.
+- Cluster networking provides communication between different Pods.
+- The Service resource lets you expose an application running in Pods to be reachable from outside your cluster.
+- You can also use Services to publish services only for consumption inside your cluster.

content/en/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md

@@ -23,7 +23,7 @@ Modification not using HostAliases is not suggested because the file is managed
 Start an Nginx Pod which is assigned a Pod IP:
 
 ```shell
-kubectl run nginx --image nginx --generator=run-pod/v1
+kubectl run nginx --image nginx
 ```
 
 ```
@@ -64,14 +64,14 @@ By default, the `hosts` file only includes IPv4 and IPv6 boilerplates like
 ## Adding additional entries with hostAliases
 
 In addition to the default boilerplate, you can add additional entries to the
-`hosts` file.  
+`hosts` file.
 For example: to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`,
 `bar.remote` to `10.1.2.3`, you can configure HostAliases for a Pod under
 `.spec.hostAliases`:
 
 {{< codenew file="service/networking/hostaliases-pod.yaml" >}}
 
-Yoyu can start a Pod with that configuration by running:
+You can start a Pod with that configuration by running:
 
 ```shell
 kubectl apply -f https://k8s.io/examples/service/networking/hostaliases-pod.yaml