From d4a07f44702b57629aeb010fdd5d64cc87f55761 Mon Sep 17 00:00:00 2001
From: puneetse <22071208+puneetse@users.noreply.github.com>
Date: Wed, 22 Aug 2018 16:09:50 -0700
Subject: [PATCH] Add OSV abbreviation

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

diff --git a/source/clear-linux/guides/deploy-at-scale.rst b/source/clear-linux/guides/deploy-at-scale.rst
index a4f7dcf1..b8c2ecc4 100644
--- a/source/clear-linux/guides/deploy-at-scale.rst
+++ b/source/clear-linux/guides/deploy-at-scale.rst
@@ -37,7 +37,7 @@ Pick a |CL| usage and update strategy
 Different business scenarios can call for different deployment methodologies. 
 |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. 
+act as your own :abbr:`OSV (Operating System Vendor)`. 
 
 
 Below are overviews of both approaches and some considerations.
@@ -83,10 +83,10 @@ Option #2: Create your own Linux distribution (mix)
 ---------------------------------------------------
 
 This approach forks away from the |CL| upstream and has you act as your own 
-Operating System Vendor (OSV) by leveraging the `mixer process`_ to create 
-customized images based on |CL|. This is a level of responsibility that 
-requires having more infrastructure and processes  to adopt. In return, this 
-approach *offers you a high degree of control and customization*.
+:abbr:`OSV (Operating System Vendor)` by leveraging the `mixer process`_ to 
+create customized images based on |CL|. This is a level of responsibility 
+that requires having more infrastructure and processes  to adopt. In return, this approach 
+*offers you a high degree of control and customization*.
 
 
 * Development systems which are generating bundles and updates should be