From 53d55320e778c1346c8b7654b21f2e9d0abaa41b Mon Sep 17 00:00:00 2001
From: Junaid Ali <junaidali@plumgrid.com>
Date: Mon, 12 Dec 2016 22:03:46 +0500
Subject: [PATCH 1/2] Improving expose-intro.html

  - Fixed a typo

Signed-off-by: Junaid Ali <junaid_ali4@yahoo.com>
---
 docs/tutorials/kubernetes-basics/expose-intro.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/tutorials/kubernetes-basics/expose-intro.html b/docs/tutorials/kubernetes-basics/expose-intro.html
index 524e051c68..4e65a16988 100644
--- a/docs/tutorials/kubernetes-basics/expose-intro.html
+++ b/docs/tutorials/kubernetes-basics/expose-intro.html
@@ -31,7 +31,7 @@
 
 			<p>This abstraction will allow us to expose Pods to traffic originating from outside the cluster. Services have their own unique cluster-private IP address and expose a port to receive traffic. If you choose to expose the service outside the cluster, the options are:</p>
 			<ul>
-				<li>LoadBalancer - provides a public IP address (what you would typically use when you run Kubernetes on GKE or AWS)</li>
+				<li>LoadBalancer - provides a public IP address (what you would typically use when you run Kubernetes on GCE or AWS)</li>
 				<li>NodePort - exposes the Service on the same port on each Node of the cluster using NAT (available on all Kubernetes clusters, and in Minikube)</li>
 			</ul>
 			</div>

From 5bcc66a16a81078766e1ef94dcd4b1321630a71c Mon Sep 17 00:00:00 2001
From: devin-donnelly <ddonnelly@google.com>
Date: Thu, 22 Dec 2016 18:39:52 -0800
Subject: [PATCH 2/2] Update expose-intro.html

---
 docs/tutorials/kubernetes-basics/expose-intro.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/tutorials/kubernetes-basics/expose-intro.html b/docs/tutorials/kubernetes-basics/expose-intro.html
index 4e65a16988..cd40b22f8b 100644
--- a/docs/tutorials/kubernetes-basics/expose-intro.html
+++ b/docs/tutorials/kubernetes-basics/expose-intro.html
@@ -31,7 +31,7 @@
 
 			<p>This abstraction will allow us to expose Pods to traffic originating from outside the cluster. Services have their own unique cluster-private IP address and expose a port to receive traffic. If you choose to expose the service outside the cluster, the options are:</p>
 			<ul>
-				<li>LoadBalancer - provides a public IP address (what you would typically use when you run Kubernetes on GCE or AWS)</li>
+				<li>LoadBalancer - provides a public IP address (what you would typically use when you run Kubernetes on GCP or AWS)</li>
 				<li>NodePort - exposes the Service on the same port on each Node of the cluster using NAT (available on all Kubernetes clusters, and in Minikube)</li>
 			</ul>
 			</div>