Merge pull request Alexia#30 from bryant1410/master

Fix broken headings in Markdown files

Author: Alexia

README.md

@@ -1,21 +1,21 @@
-#Introduction
-####What is PHP 7 Migration Assistant Report(MAR)?
+# Introduction
+#### What is PHP 7 Migration Assistant Report(MAR)?
 PHP 7 MAR, or just "php7mar", is a command line utility to generate reports on existing PHP 5 code to assist developers in porting their code quickly to PHP 7.  It will run against invididual files or entire project folders.  Reports contain line numbers, issues noted, and suggested fixes along with documentation links.
 
-####Will php7mar automatically fix my code?
+#### Will php7mar automatically fix my code?
 No, php7mar does implement a full lexer to determine code changes and can not determine the intent of the code.  It uses lexer tokenizing, string matching, and regular expressions to find syntax changes that may cause issues when porting code to PHP 7.  As well, it will detect code snippets in comments and report them as it can not distinguish it as commented code.
 
-####What has changed in PHP 7? (Read This!)
+#### What has changed in PHP 7? (Read This!)
 If you are currently unfamiliar with what will change moving to PHP 7 then read the [UPGRADING file in the current master branch of php-src](https://github.com/php/php-src/blob/PHP-7.0.0/UPGRADING).  Understanding these changes is important to reading the reports generated by php7mar.
 
-####Does it handle very poorly styled code?
+#### Does it handle very poorly styled code?
 Very poorly styled code will not parse well, but assuming there is at least some structure to the code style it should still parse.  If the code is entirely too poorly formatted there are several web sites that can be used to clean up source code.
 
 * http://www.phpformatter.com/ (Does not support PHP 5.4 [] array syntax.)
 * http://phpbeautifier.com/
 * http://phpcodecleaner.com/
 
-#Usage
+# Usage
 First, start by downloading or cloning this repository.  It does not need to be placed inside the folder containing the source code.
 
 To begin, type on the command line:
@@ -38,7 +38,7 @@ Give a try, use the included `testcases.php` to generate a report:
 
 	php mar.php -f="testcases.php"
 
-##Available Options:
+## Available Options:
 **-f**
 ```
 	Path to the file or folder to run against.
@@ -74,12 +74,12 @@ Give a try, use the included `testcases.php` to generate a report:
 		*Example: --php="/path/to/php/binary/php"*
 ```
 
-#Test Types
-##Critical
+# Test Types
+## Critical
 Critical tests look for issues that will cause broken code, compilation errors, or otherwise create code that works in unintended manors.
 
-##Nuance
+## Nuance
 Nuance tests look for issues that might cause silent underisable code behavior.  These tests can report many false positives as they can not determine the intent of the code being checked.
 
-##Syntax
+## Syntax
 A basic command line based syntax checker that checks all files for standard syntax issues.  This is useful for double checking work after making many mass find and replace operations.  Please note that syntax checking adds a significant increase to processing time especially for large code bases.  To run without syntax checking use the -t option and omit syntax; -t="critical,nuance"

STYLE.md

@@ -1,10 +1,10 @@
-#DRAFT
+# DRAFT
 
-#General Style
+# General Style
 * Code SHOULD generally follow PSR-1 except where contradicted below.
 * Code MUST use the One True Brace style variant of K&R.  See: http://en.wikipedia.org/wiki/Indent_style#Variant:_1TBS
 * Code MUST use one tab character per ident level.
 
-#Function, Method, Class, and Namespaces
+# Function, Method, Class, and Namespaces
 * Functions, methods, classes, and namespaces MUST use camelCased names.
 * In the instance of an acronym it MUST be converted to lower case.