From 44583f525f47eaeb7f6d6275c790a61eebb556d3 Mon Sep 17 00:00:00 2001
From: Iuri Matias <iuri.matias@gmail.com>
Date: Mon, 31 Aug 2015 20:19:07 -0400
Subject: [PATCH] adjust readme

---
 README.md | 27 ++++++++++++++++-----------
 1 file changed, 16 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index ec1d837e..ae29a399 100644
--- a/README.md
+++ b/README.md
@@ -25,16 +25,6 @@ For specs: pyethereum, ethertdd.py
 $ npm install -g embark-framework grunt-cli
 ```
 
-If you get EACCES (access denied) errors, don't use sudo, try this:
-
-```Bash
-$ mkdir ~/npm-global
-$ npm config set prefix ~/npm-global
-$ echo 'export PATH="$PATH:$HOME/npm-global/bin"' >>~/.bashrc
-$ source ~/.bashrc
-$ npm install -g embark-framework grunt-cli
-```
-
 See [Complete Installation Instructions](https://github.com/iurimatias/embark-framework/wiki/Installation).
 
 Usage - Demo
@@ -296,4 +286,19 @@ Because embark is internally using grunt tasks, debugging is not straightforward
 - This gives you nothing with embark. If you look at `deploy` command in [`./bin/embark`](https://github.com/iurimatias/embark-framework/blob/develop/bin/embark#L32-L35) you will notice that it internally runs grunt task `grunt deploy_contracts:[env]`
 - with this knowledge we can prepare proper command to start debugging
 - `node-debug -p 7000 grunt -- deploy_contracts:development`
-- [here](https://github.com/iurimatias/embark-framework/blob/develop/tasks/tasks.coffee) is list of all debuggable grunt tasks
+-
+
+ [here](https://github.com/iurimatias/embark-framework/blob/develop/tasks/tasks.coffee) is list of all debuggable grunt tasks
+
+EACCESS Error
+======
+If you get EACCES (access denied) errors, don't use sudo, try this:
+
+```Bash
+$ mkdir ~/npm-global
+$ npm config set prefix ~/npm-global
+$ echo 'export PATH="$PATH:$HOME/npm-global/bin"' >>~/.bashrc
+$ source ~/.bashrc
+$ npm install -g embark-framework grunt-cli
+```
+