Update README.md

updated readme to make ir cozy

README.md

@@ -1,19 +1,43 @@
-# circular_buffer
+# General Purpouse Circular Buffer
 
-A general purpose circular buffer implementation.
+This C library is supposed to solve one of the most common problems when developing. Implements a bunch of functions to deal with an user defined array of any kind as a circular buffer.
 
+Users should statically allocate on memory an array of any kind and provide to the library the underlying array pointer, the array size, and the size of the elements when initializing the circular buffer library and it will return the pointer to a circular buffer handler to them.                                            
+
+Systems which cannot use dynamic memory simply need to statically allocate memory for a buffer struct instance and take a look to circular_buffer_struct_init() function to initialize it.
 
-### Folder structure
+## Documentation
+
+You could find detailed Doxygen documentation clicking [here](https://fededc88.github.io/circular_buffer/).
+
+## Folder structure
+
+* **buffer**: Contains the circular buffer library source and header files.
+
+* **test**: Contains the unit tests related to different algorithms of the
+  project. 
+
+* **docs**: Contains html Doxygen documentation source files. See [Documentation](#Documentation)
+
+### Get the repo
 
 This repo includes [Unity Test](https://github.com/ThrowTheSwitch/Unity) as a submodule, so in order to clone and get the unit testing framework built for C test do:
 
 ```
 git clone https://github.com/fededc88/circular_buffer.git --recurse-submodules -j<n_cores>
 ```
 
-## Documentation
+## Testing
 
-You could find detailed Doxygen documentation clicking [here](https://fededc88.github.io/circular_buffer/).
+I am running some local test for specific algorithms using [Unitest](http://www.throwtheswitch.org/unity). Unity is written in 100% pure C code. It follows ANSI standards while supporting most embedded compiler quirks. To run them, just clone the recursively the repo and get a C/C++ compiller to have the framework running. 
+
+And them, to compile source files and execute tests run:
+
+```
+cd path_to_repo/test && make
+```
+
+Unitest will present you the results as console outputs. 
 
 ## Referencing