From 506842bc165cf1c4e205e4fcdaf5e678509a55d3 Mon Sep 17 00:00:00 2001 From: Ce Gu Date: Tue, 15 Aug 2017 13:51:37 +0800 Subject: [PATCH] Remove duplicate 'the'. (#4715) * Remove duplicate 'the'. * Update add-entries-to-pod-etc-hosts-with-host-aliases.md --- .../add-entries-to-pod-etc-hosts-with-host-aliases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md b/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md index 1e3892dd8a..b3bcab7e71 100644 --- a/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md +++ b/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md @@ -38,7 +38,7 @@ by default, the hosts file only includes ipv4 and ipv6 boilerplates like `localh ## Adding Additional Entries with HostAliases -In addition the the default boilerplate, we can add additional entries to the hosts file to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`, `bar.remote` to `10.1.2.3`, we can by adding HostAliases to the Pod under `.spec.hostAliases`: +In addition to the default boilerplate, we can add additional entries to the hosts file to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`, `bar.remote` to `10.1.2.3`, we can by adding HostAliases to the Pod under `.spec.hostAliases`: {% include code.html language="yaml" file="hostaliases-pod.yaml" ghlink="/docs/concepts/services-networking/hostaliases-pod.yaml" %}