From 1a96ff6766120e855e1a867f76a0518b3f1489d0 Mon Sep 17 00:00:00 2001
From: lchristina26 <leah@wolfssl.com>
Date: Thu, 29 Oct 2015 13:45:58 -0600
Subject: [PATCH] readme updates

---
 IDE/WORKBENCH/README.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/IDE/WORKBENCH/README.md b/IDE/WORKBENCH/README.md
index 7158596ce..4d5c6c56a 100644
--- a/IDE/WORKBENCH/README.md
+++ b/IDE/WORKBENCH/README.md
@@ -35,20 +35,20 @@ if everything is working.
 1. In usrAppInit.c, make a call to the wolfCrypt test application by adding
 the following to the usrAppInit() function:
 
-    typedef struct func_args {
-        int    argc;
-        char** argv;
-        int    return_code;
-    } func_args;
+        typedef struct func_args {
+            int    argc;
+            char** argv;
+            int    return_code;
+        } func_args;
 
-    func_args args;
+        func_args args;
 
     wolfcrypt_test(&args);
 2. Include these header files in usrAppInit.c:
-    #include <wolfcrypt/test/test.h>
-    #include <wolfssl/ssl.h>
-    #include <wolfssl/wolfcrypt/settings.h>
-    #include <wolfssl/test.h>
+        #include <wolfcrypt/test/test.h>
+        #include <wolfssl/ssl.h>
+        #include <wolfssl/wolfcrypt/settings.h>
+        #include <wolfssl/test.h>
 3. Start the simulator and check that all wolfCrypt tests pass. If there is a
 certificate file error, adjust the caCert file locations in
 wolfcrypt/test/test.c or wolfssl/test.h to those of the filesystem in use.