From 75c8b3c0f07f97bd0373602213ef803a53434224 Mon Sep 17 00:00:00 2001 From: Anthony Date: Fri, 18 Aug 2017 11:05:58 +0800 Subject: [PATCH] Update dns-custom-nameservers.md add "." to the sentence --- docs/tasks/administer-cluster/dns-custom-nameservers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/administer-cluster/dns-custom-nameservers.md b/docs/tasks/administer-cluster/dns-custom-nameservers.md index 1e760be394..b2917f96bb 100644 --- a/docs/tasks/administer-cluster/dns-custom-nameservers.md +++ b/docs/tasks/administer-cluster/dns-custom-nameservers.md @@ -93,7 +93,7 @@ routed according to the following flow: ## ConfigMap options -Options for the kube-dns `kube-system:kube-dns` ConfigMap +Options for the kube-dns `kube-system:kube-dns` ConfigMap: | Field | Format | Description | | ----- | ------ | ----------- | @@ -107,7 +107,7 @@ Options for the kube-dns `kube-system:kube-dns` ConfigMap In this example, the user has a Consul DNS service discovery system that they wish to integrate with kube-dns. The consul domain server is located at 10.150.0.1, and all consul names have the suffix “.consul.local”. To configure Kubernetes, the -cluster administrator simply creates a ConfigMap object as shown below. +cluster administrator simply creates a ConfigMap object as shown below. ```yaml apiVersion: v1