Using 'p' instead of 'j' in version

Fixed broken composer.json

README.md

@@ -25,18 +25,17 @@ For transparency and insight into our release cycle, and for striving to maintai
 
 Releases will be numbered with the following format:
 
-`<major>.<minor>.<patch>-j<jasny version>`
+`<major>.<minor>.<patch>-p<jasny version>`
 
 And constructed with the following guidelines:
 
-* Breaking backward compatibility bumps the major (and resets the minor and patch)
-* New additions without breaking backward compatibility bumps the minor (and resets the patch)
-* Bug fixes and misc changes bumps the patch
+* Breaking backward compatibility bumps the major
+* New additions without breaking backward compatibility bumps the minor
+* Bug fixes and misc changes bump the patch
+* Additionally the version for the Jasny extensions will simply be incremented with each release and is prefixed with a 'p'
 
 For more information on SemVer, please visit [http://semver.org/](http://semver.org/).
 
-Additionally the version for the Jasny extensions will simply be incremented with each release and is prefixed with a 'j'.
-
 
 ## Bug tracker
 

composer.json

@@ -8,5 +8,5 @@
      , {"name": "Arnold Daniels", "email": "arnold@jasny.net", "homepage": "http://www.jasny.net"}
   ]
   , "license": "Apache-2.0"
-  , "replace": "twitter/bootstrap"
+  , "replace": { "twitter/bootstrap" : "2.3.1" }
 }