From 8b9683f14de3b574b4c81560322b54dc0a4c8fd9 Mon Sep 17 00:00:00 2001
From: catodd <cory@pyramidacceptors.com>
Date: Tue, 14 Feb 2017 07:43:37 -0700
Subject: [PATCH] Update README.md

Fix the numbering
---
 PauseResumeCLI/README.md | 37 ++++++++++++++++---------------------
 1 file changed, 16 insertions(+), 21 deletions(-)

diff --git a/PauseResumeCLI/README.md b/PauseResumeCLI/README.md
index e761c88..a1e82be 100644
--- a/PauseResumeCLI/README.md
+++ b/PauseResumeCLI/README.md
@@ -12,30 +12,25 @@ These command work in either Escrow or Non-Escrow mode.
 
 ##Highlights
 
-1. Subscribe
-
-```
-    validator.OnEscrow +=validator_OnEscrow;
-```    
-	
-2. Control your state
-    
-```    
-    AppState = InternalState.Escrow;
-```
-
-3. Execute your action
-
-```
+ 1. Subscribe
+ 
+ ```csharp
+     validator.OnEscrow +=validator_OnEscrow;
+ ```    
+ 2. Control your state
+ 
+ ```csharp    
+     AppState = InternalState.Escrow;
+ ```
+ 3. Execute your action
+ 
+ ```csharp
     // If Escrowed, prompt for stack or reject
     else if (AppState == InternalState.Escrow)
     {
         validator.Stack();	 
     }
-```	  
-	  
-4. Emit the PauseAcceptance() or ResmeAcceptance() when the acceptor is in the Idle state. If you call PauseAcceptance()
-while stacking, the note may return immediately depending on your poll rate. It is advised that either check the state 
-validator.PreviousState or maintain your own state if you have more complex customer requirements. The PreviousState 
-property is called such because it is not realtime. It is the state reported by the slave during the previous message loop.
+ ```
+ 4. Emit the PauseAcceptance() or ResmeAcceptance() when the acceptor is in the Idle state
+- If you call PauseAcceptance() while stacking, the note may return immediately depending on your poll rate. It is advised that either check the state validator.PreviousState or maintain your own state if you have more complex customer requirements. The PreviousState  property is called such because it is not realtime. It is the state reported by the slave during the previous message loop.