From 2d473129b2f6186124b3da980a73b6e0813b1527 Mon Sep 17 00:00:00 2001
From: Daniel Qian <chanjarster@gmail.com>
Date: Sat, 16 Jun 2018 19:06:34 +0800
Subject: [PATCH] Minor modification for
 concepts/services-networking/service.md (#9096)

---
 content/en/docs/concepts/services-networking/service.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md
index d4c4482ff7..c5773a12af 100644
--- a/content/en/docs/concepts/services-networking/service.md
+++ b/content/en/docs/concepts/services-networking/service.md
@@ -409,7 +409,7 @@ The default is `ClusterIP`.
 ### Type NodePort
 
 If you set the `type` field to `NodePort`, the Kubernetes master will
-allocate a port from a flag-configured range (default: 30000-32767), and each
+allocate a port from a range specified by `--service-node-port-range` flag (default: 30000-32767), and each
 Node will proxy that port (the same port number on every Node) into your `Service`.
 That port will be reported in your `Service`'s `.spec.ports[*].nodePort` field.