updated the readme, now it actually makes some sense and talks about what bruiser really does

1 files changed, 2 insertions, 2 deletions

diff --git a/bruiser/README.md b/bruiser/README.md
index 07139c6..95a759a 100644
--- a/bruiser/README.md
+++ b/bruiser/README.md
@@ -1,10 +1,10 @@
 ## bruiser
 
 ### What is it?
-The idea is simple. bruiser will try to break your code. One way to do this is have bruiser mutate the source code and then run the code to see if it breaks. The other way to do this is have bruiser first "analyze" the code, to get to know it and then decide how to break it.<br/>
+First off let's start with concrete facts. bruiser is implemented as an interactive shell, you can ask it to list information regrading the source codes it is run on. Future implementation plans include mutating the code as you want it to, and the little feeature that gives bruiser it's name which is to look at the code and decide how to break it.<br/>
 
 ### Why?
-Well you can probably use your imagination to come up with practical uses for bruiser, but I'm doing this because it's fun.<br/>
+It's an interactive mutation tool, mutation has it's own uses like muation testing. It can give you some insight into the code-base you are maintaining.<br/>
 
 ### Implementation Ideas(Or bruiser Requirements if you will)
 The analysis part can be handled by m0(mutator-lvl0), while bruiser consumes the report generated by m0. I'm leaning towards using the XML reoport mostly because of X-Path.<br/>