guides/developer/Developer-guide.md

@@ -20,18 +20,18 @@ Component development
 
 Every modular aspect of Arachni is abstracted in the form of
 *components* .
-As long as components lie within their root directories (*/modules* for
-modules, */reports* for reports and */plugins* for plugins)\
+As long as components lie within their root directories (```/modules``` for
+modules, ```/reports``` for reports and ```/plugins``` for plugins)
 there is no limitation as to how they can be grouped together.
 
-Arachni scans these directories recursively and loads all Ruby (\*.rb)
+Arachni scans these directories recursively and loads all Ruby (```*.rb```)
 files as components.
 However, since there will often be a need to include helper Ruby files
 (like classes, modules, etc) components are allowed to include such files under
 a directory with the same name as the component that utilizes them.
 
-For example, the *Proxy* plugin which has a filename of *proxy.rb* holds its
-helper classes in the *proxy/* directory.
+For example, the *Proxy* plugin which has a filename of ```proxy.rb``` holds its
+helper classes under the ```proxy/``` directory.
 
 Ruby files identified as helpers will not be loaded by the framework.