Merge pull request #772 from arciem/updateMarkdown

Fixed markdown of code in mrbgems/README.md

doc/mrbgems/README.md

@@ -11,33 +11,24 @@ extension integrated.
 
 To add a GEM into the build_config.rb add the following line for example:
 
-```
-conf.gem '/path/to/your/gem/dir'
-```
+	conf.gem '/path/to/your/gem/dir'
 
 You can also use a relative path which would be relative from the mruby root:
 
-```
-conf.gem 'doc/mrbgems/ruby_extension_example'
-```
+	conf.gem 'doc/mrbgems/ruby_extension_example'
 
 A remote GIT repository location for a GEM is also supported:
 
-```
-conf.gem :git => 'https://github.com/masuidrive/mrbgems-example.git', :branch => 'master'
-```
+	conf.gem :git => 'https://github.com/masuidrive/mrbgems-example.git', :branch => 'master'
 
-```
-conf.gem :github => 'masuidrive/mrbgems-example', :branch => 'master'
-```
+	conf.gem :github => 'masuidrive/mrbgems-example', :branch => 'master'
 
 
 ## GEM Structure
 
 The maximal GEM structure looks like this:
 
-```
-+- GEM_NAME         <- Name of GEM
+	+- GEM_NAME         <- Name of GEM
 	   |
 	   +- mrblib/       <- Source for Ruby extension
 	   |
@@ -48,7 +39,6 @@ The maximal GEM structure looks like this:
 	   +- mrbgem.rake   <- GEM Specification
 	   |
 	   +- README.md     <- Readme for GEM
-```
 
 The folder *mrblib* contains pure Ruby files to extend mruby. The folder *src*
 contains C files to extend mruby. The folder *test* contains C and pure Ruby files
@@ -61,12 +51,10 @@ of your GEM.
 mrbgems expects a specifcation file called *mrbgem.rake* inside of your
 GEM direcotry. A typical GEM specification could look like this for example:
 
-```
-MRuby::Gem::Specification.new('c_and_ruby_extension_example') do |spec|
+	MRuby::Gem::Specification.new('c_and_ruby_extension_example') do |spec|
 	  spec.license = 'MIT'
 	  spec.authors = 'mruby developers'
-end
-```
+	end
 
 The mrbgems build process will use this specification to compile Object and Ruby
 files. The compilation results will be add to *lib/libmruby.a*. This file is used
@@ -98,13 +86,11 @@ mrbgems expects that you have implemented a C method called
 by the name of your GEM. If you call your GEM *c_extension_example*, your
 initialisation method could look like this:
 
-```
-void
-mrb_c_extension_example_gem_init(mrb_state* mrb) {
+	void
+	mrb_c_extension_example_gem_init(mrb_state* mrb) {
 	  struct RClass *class_cextension = mrb_define_module(mrb, "CExtension");
 	  mrb_define_class_method(mrb, class_cextension, "c_method", mrb_c_method, ARGS_NONE());
-}
-```
+	}
 
 ### Finalize
 
@@ -123,8 +109,7 @@ mrb_c_extension_example_gem_final(mrb_state* mrb) {
 
 ### Example
 
-```
-+- c_extension_example/
+	+- c_extension_example/
 	   |
 	   +- src/
 	   |  |
@@ -137,7 +122,6 @@ mrb_c_extension_example_gem_final(mrb_state* mrb) {
 	   +- mrbgem.rake          <- GEM specification
 	   |
 	   +- README.md
-```
 
 ## Ruby Extension
 
@@ -151,8 +135,7 @@ none
 
 ### Example
 
-```
-+- ruby_extension_example/
+	+- ruby_extension_example/
 	   |
 	   +- mrblib/
 	   |  |
@@ -165,7 +148,6 @@ none
 	   +- mrbgem.rake          <- GEM specification
 	   |
 	   +- README.md
-```
 
 ## C and Ruby Extension
 
@@ -179,8 +161,7 @@ See C and Ruby example.
 
 ### Example
 
-```
-+- c_and_ruby_extension_example/
+	+- c_and_ruby_extension_example/
 	   |
 	   +- mrblib/
 	   |  |