Update README.md

typo: exists, update: separated html and js code examples, update: jquery version, update: using script tag without attribute, update: using only one backtick on inline code.
Retrieving unmasked value\n\nThis patch allows to get the unmasked value of an input (issue #97).\n\n**1. Why is this change necessary?**\nPlugins like this, who format an input in a WYSIWYG way, have a specific audience: developers who care about usability. In the case of this particular type of plugin, we want that the user can insert a monetary value without worrying whether he should/can use a period, comma, etc, and we want he can be able to see smoothly the results as he type. But this is just a part of the process. The basic flow is: a) use some formatter to improve the user\'s usability and experience. b) unformat the result c) save to some database. To make any processing with the value we have to remove the format. So its natural for who make use of a plugin like this that has to make some code to remove the format and extract the pure data. This is the natural use, so why not add this functionality?\n\n**2. How does it address the issue?**\nI\'m add a new method called _unmasked()_ encapsuled within the maskMoney methods. By calling _myinput.maskMoney(\'unmasked\')_ will return a float object with something like _1234.56_.\n\n**3. What side effects does this change have?**\n\nNone I believe. It\'s backward compatible.
adopting the Plentz solution
Merge pull request #100 from wbotelhos/patch-1

Update README.md
keeping everything together to make it easier to understand
README conflicts
minor adjustment in @loureirorg's pull request
fixing bug introduced by a unrelated change in #102
ok, I decided to do it right. adding an unmasked method that returns each of the elements as a float. fixes #14 #97 #102
ingrish
fixing a bug that could happen in unmasked function, when the number is negative