rewording

1 files changed, 9 insertions, 9 deletions

diff --git a/design-documents/036-currency-conversion-service.rst b/design-documents/036-currency-conversion-service.rst
index d2cc6833..7c9bbc72 100644
--- a/design-documents/036-currency-conversion-service.rst
+++ b/design-documents/036-currency-conversion-service.rst
@@ -12,7 +12,7 @@ merchants to cash-out from the regional currency to fiat.
 Motivation
 ==========
 
-The conversion service (CS) is fundamental for a regional
+The conversion service (CCS) is fundamental for a regional
 currency and is missing in the Taler/Libeufin ecosystem.
 
 Definitions
@@ -35,21 +35,21 @@ currency.
 Requirements
 ============
 
-* CS must not impact the Nexus structure.
-* CS must create Taler withdraws every time a customer buys the
+* CCS must not impact the Nexus structure.
+* CCS must trigger Taler withdrawls every time a customer buys the
   regional currency ('buy-in' operation).
-* CS must offer cash-out operations.
-* CS should react as soon as possible to buy-in and cash-out operations.
-* CS must show its state to administrators.
-* CS must link every fiat-side of a cash-out to its regional currency
+* CCS must offer cash-out operations.
+* CCS should react as soon as possible to buy-in and cash-out operations.
+* CCS must show its state to administrators.
+* CCS must link every fiat-side of a cash-out to its regional currency
   counterpart.  In particular, because every cash-out starts with a
   payment *P* from regio-user to regio-issuer and ends with another
-  payment *Q* from fiat-issuer to fiat-target, CS must link P and Q. 
+  payment *Q* from fiat-issuer to fiat-target, CCS must link P and Q. 
 
 Proposed Solution
 =================
 
-The following design assumes that CS is coded into libeufin Sandbox.
+The following design assumes that CCS is coded into libeufin Sandbox.
 
 Cash-out operation
 ------------------