Corrections in README (#15)

Author: neoscie

README.md

@@ -14,13 +14,13 @@ The base ruleset consists of the default ruleset of the Roslyn Analyzers we incl
 - We include our own [stylecop.json](https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/Configuration.md) configuration file.
 
 ## Versioning
-Given a version number MAJOR.MINOR.PATCH, an incremented number for:
+Given a version number `MAJOR.MINOR.PATCH`, an incremented number for:
 
-- MAJOR version means there are incompatible changes with the previous version,
-- MINOR version means functionality and rules were added, and
-- PATCH version means that the changes are all completely backwards compatible. Usually when rules were lowered in severity or disabled/removed.
+- `MAJOR` version means there are incompatible changes with the previous version,
+- `MINOR` version means functionality and rules were added, and
+- `PATCH` version means that the changes are all completely backwards compatible. Usually when rules were lowered in severity or disabled/removed.
 
 ### What it means in practice:
-- You can (and should) always update the package to the latest **PATCH** version whenever you have the chance to do it, it should never break the build. 
-- Updating to the latest **MINOR** version can break the build and may require minor refactorings. But you can expect to have Roslyn code fixes and/or documentation available for the changes that are needed to fix the build.
--  **MAJOR** updates will break your build and may require major refactorings.
+- You can (and should) always update the package to the latest `PATCH` version whenever you have the chance to do it, it should never break the build. 
+- Updating to the latest `MINOR` version can break the build and may require minor refactorings. But you can expect to have Roslyn code fixes and/or documentation available for the changes that are needed to fix the build.
+-  `MAJOR` updates will break your build and may require major refactorings.