From ddadce7857cfb0b69e1ad68e4a64276f5d2b2155 Mon Sep 17 00:00:00 2001
From: puneetse <22071208+puneetse@users.noreply.github.com>
Date: Tue, 14 Aug 2018 16:31:37 -0700
Subject: [PATCH] RST syntax fixes and minor intro edit

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

diff --git a/source/clear-linux/guides/deploy-at-scale.rst b/source/clear-linux/guides/deploy-at-scale.rst
index 4312a84f..57868a25 100644
--- a/source/clear-linux/guides/deploy-at-scale.rst
+++ b/source/clear-linux/guides/deploy-at-scale.rst
@@ -1,11 +1,11 @@
 .. _deploy-at-scale.rst:
 
 Deploying |CL| at Scale
-##############################
+#######################
 
 Once you are comfrotable with `Clear Linux concepts`_, your next step
-may be needing to understand how to deploy |CL| at scale in your 
-enoviornment.  
+as a system administraotr 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 
 to a system targeted for |CL| installation, whether that is a datacenter 
@@ -32,7 +32,7 @@ system or unit deployed in field.
 
 
 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|