From 6682eae771b85a7f646282a6b7beff5ed7aecab3 Mon Sep 17 00:00:00 2001 From: AdamDang Date: Mon, 5 Mar 2018 14:04:05 +0800 Subject: [PATCH] Typo fix "NAT Gateways" -> "NAT gateways" "NAT gateway" appears 3 times in this doc. Two are "NAT gateway" ,while one is "NAT Gateway" . They should be kept consistency. --- docs/cluster_spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cluster_spec.md b/docs/cluster_spec.md index 01d7d40f84..f71ee67553 100644 --- a/docs/cluster_spec.md +++ b/docs/cluster_spec.md @@ -106,7 +106,7 @@ ID of a subnet to share in an existing VPC. #### egress The resource identifier (ID) of something in your existing VPC that you would like to use as "egress" to the outside world. -This feature was originally envisioned to allow re-use of NAT Gateways. In this case, the usage is as follows. Although NAT gateways are "public"-facing resources, in the Cluster spec, you must specify them in the private subnet section. One way to think about this is that you are specifying "egress", which is the default route out from this private subnet. +This feature was originally envisioned to allow re-use of NAT gateways. In this case, the usage is as follows. Although NAT gateways are "public"-facing resources, in the Cluster spec, you must specify them in the private subnet section. One way to think about this is that you are specifying "egress", which is the default route out from this private subnet. ``` spec: