format doc alteration

CODE_FORMATING.md

@@ -3,15 +3,20 @@ relatively consistent and readable. No one is going to kill you if you mess up,
 but it is nice to keep things looking consistent throughout.
 
 1. Operators and Keywords are spaced out.
+
 	Examples:
+	````
 		Bad: if(a+b==c){return;}
 		Good: if (a + b == c) { return; }
+	````
 
 2. Capitalization:
 	- High order Objects (similar to classic classes) get capitalized.
 	- Variables serving as constants are ALL_CAPS with underscore spacing
 	- Everything else is camelCase
+
 	Examples:
+	````
 		Bad: Book.page = {
 				pageNumber: 0,
 				font: 'arial',
@@ -26,12 +31,15 @@ but it is nice to keep things looking consistent throughout.
 		
 		Bad: var maxPagesPerBook = 100; // This is a constant variable, do not change in code!
 		Good: var MAX_PAGES_PER_BOOK = 100;
+	````
 		
 3. Comments:
 	- Use block javaDoc style comments for large blocks or code sections.
 		(The extra space for * lines is not mandatory, just done automatically by some editors.)
 	- Leave a space after double slash for in-line comments, capitalize them, use [brackets] for special distinctions
+
 	Examples:
+	````
 		Bad: //++++++++++
 			// Section for Math stuff
 			//===================================
@@ -42,5 +50,6 @@ but it is nice to keep things looking consistent throughout.
 		
 		Bad: //this variable is temporary for testing reason
 		Good: // [TEMP] Variable for testing purposes only
+	````
 		
 4. Leave a blank line at the end of all documents.