From f252dce315ad754cf80800c26169571df5f31ec6 Mon Sep 17 00:00:00 2001
From: puneetse <22071208+puneetse@users.noreply.github.com>
Date: Wed, 22 Aug 2018 15:46:36 -0700
Subject: [PATCH] Fix a few typos noticed by @tpleavitt

---
 source/clear-linux/guides/deploy-at-scale.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/source/clear-linux/guides/deploy-at-scale.rst b/source/clear-linux/guides/deploy-at-scale.rst
index 57868a25..cd6aed8a 100644
--- a/source/clear-linux/guides/deploy-at-scale.rst
+++ b/source/clear-linux/guides/deploy-at-scale.rst
@@ -3,8 +3,8 @@
 Deploying |CL| at Scale
 #######################
 
-Once you are comfrotable with `Clear Linux concepts`_, your next step
-as a system administraotr may be needing to understand how to deploy 
+Once you are comfortable with `Clear Linux concepts`_, your next step
+as a system administrator may be needing to understand how to deploy 
 |CL| at scale in your enoviornment.  
 
 Throughout this document the term *endpoint* will be used to generally refer 
@@ -35,7 +35,7 @@ Pick a |CL| usage and update strategy
 =====================================
 
 Different business scenarios can call for different deployment methodologies. 
-|CLOSIA| offers the flexibility to continue consuming upstream |CL|
+|CLOSIA| offers the flexibility to continue consuming the upstream |CL|
 distribution or the option to fork away from the |CL| distribution and
 act as your own OSV.