Updated: Spelling Mistake

Issue-ID: AAF-589

Change-Id: I2e9188f68baff6722144a885ba8a14f7263e8b24
Signed-off-by: Manish Kumar <manishjpiet@gmail.com>

diff --git a/docs/sections/installation/Bootstrapping-AAF-Components.rst b/docs/sections/installation/Bootstrapping-AAF-Components.rst
index 79b2fff..64987e4 100644 (file)
--- a/docs/sections/installation/Bootstrapping-AAF-Components.rst
+++ b/docs/sections/installation/Bootstrapping-AAF-Components.rst
@@ -202,8 +202,8 @@ AAF is setup so it can run
 
 On the O/S, using Java
 On Docker
-On K8
-In each case, even for Docker/K8, we utilize the File O/S for host specific information.   This is because
+On K8s
+In each case, even for Docker/K8s, we utilize the File O/S for host specific information.   This is because
 
 Many things are Host Specific
 The Hostname required for TLS interactions
@@ -217,7 +217,7 @@ Steps:
 
 2) Copy your "p12" file generated by your CA (see above), and place in your "certs" directory
 
-3) SSH (or otherwise login) to your Docker/K8 Host Machine
+3) SSH (or otherwise login) to your Docker/K8s Host Machine
 
 4) setup your directories (you might need to be root, then adjust what you need for O/S File Permissions