From defe8b7ffc2fa80817f58e5815e7e88fd093eee6 Mon Sep 17 00:00:00 2001
From: Dave Parker <lowkey@kaffeinlabs.com>
Date: Wed, 6 May 2020 16:14:51 -0700
Subject: [PATCH] Use consistent headless service name

Fix a typo and update the headless service name to be consistent.
---
 docs/tutorials/hostport.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/tutorials/hostport.md b/docs/tutorials/hostport.md
index 7568b36b4..56a82ff84 100644
--- a/docs/tutorials/hostport.md
+++ b/docs/tutorials/hostport.md
@@ -17,7 +17,7 @@ A simple deploy could look like this:
 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: exeternal-dns
+  name: external-dns
 spec:
   strategy:
     type: Recreate
@@ -111,7 +111,7 @@ spec:
 
 ### Kafka Stateful Set
 
-First lets deploy a Kafka Stateful set, a simple example(a lot of stuff is missing) with a headless service called `kafka-hsvc`
+First lets deploy a Kafka Stateful set, a simple example(a lot of stuff is missing) with a headless service called `ksvc`
 
 ```yaml
 apiVersion: apps/v1beta1
@@ -155,7 +155,7 @@ spec:
         requests:
           storage:  500Gi
 ```
-Very important here, is to set the `hostport`(only works if the PodSecurityPolicy allows it)! and in case your app requires an actual hostname inside the container, unlike Kafka, which can advertise on another address, you have to set the hostname yourself.
+Very important here, is to set the `hostPort`(only works if the PodSecurityPolicy allows it)! and in case your app requires an actual hostname inside the container, unlike Kafka, which can advertise on another address, you have to set the hostname yourself.
 
 ### Headless Service