update README with latest changes. Ref #28

Author: Sebastien Pereira

README.md

@@ -4,34 +4,25 @@ This project proposes a unified and consistent javascript events API which aims
 
 This API is a shim of the [W3C Pointer Events specification][W3C_pointer] and adds features that are out of scope of the current specification.
 
-- Generates **Pointer Events** according to the current specification..
+- Generates **Pointer Events** according to the current specification.
 - Use attribute `touch-action` to set touch action on HTML elements; generates `touch-action` and `ms-touch-action` CSS properties when supported by the browser.
 - Support **Pointer Capture** with mouse and touch events.
 - Normalize **click** (Tap) events, **double click** (double Tap) events, and event **button/buttons/which** values.
-- Generate immediate clicks (no ~300ms delay)
+- Supports immediate clicks (no ~300ms delay) 
 
 ##Supported environments
 The API has been successfully tested on the following environments.
 ###Mobile
 
-- Android 4.1.1+ (Stock browser and Chrome)
+- Android 4.1.2+ (Stock browser and Chrome)
 - BlackBerry 10+
 - iOS 6.1.3+
-- WindowsPhone 8
+- WindowsPhone 8.x
 
 ###Desktop
-- **Pointer Events are always generated when using a mouse on a supported desktop browser**. 
-- Multi touch (the ability to get multiple pointers) depends on how the browser handles "finger/pen" user actions. The general rule is:
-	- **If your browser supports only mouse events, you will get Pointer Events mapped on mouse events.** For instance, IE9 may be used with a touch screen but you would get only one pointer at a time because pointer events are mapped on mouse events. 
-	- **If your browser supports native touch events, you will get Pointer Events mapped on native touch events.** For instance, on Chrome which handles native touch events you will get multiple pointers because pointer events are mapped on touch events.
-
-####Multi touch support
-- Chrome
-- IE10+
-
-####Mouse support (and single touch when possible)
-- IE9
-- FireFox 24 (multi touch expected starting release 26)
+- Chrome (mouse)
+- FireFox (mouse + touchscreen)
+- IE10+ (mouse + touchscreen)
 
 ## Dependencies
 This project can be integrated into any AMD capable javascript application.
@@ -67,13 +58,9 @@ To run the tests/samples you need to set [requirejs] and [domReady] as a sibling
 	<root>/domReady/domReady.js
 
 ##Limitations
-- Touch action values `pan-x` and `pan-y` have the same effect as `none`.
-- `event.button` returns `0` instead of `-1` on mouse move when no buttons are pressed.
-	- Pointer Events specification defines a new set of values for `event.button` and `event.buttons`: Mouse move with no buttons pressed should generate `event.button=-1`. It is not possible to force `-1` on `event.button` on browsers because they use unsigned int as internal representation of `event.button`. Setting -1 gives inconsistent results (some browsers return 0, other 65535...).
 - Pen properties (pressure/tiltx,y/height/width...) are not implemented. Properties are defined with default values. The API has not been tested with pens.
 - Avoid to rely on `pointerType`. In some cases (for instance, when a mouse is plugged on Android devices), the type may not be accurate (the mouse generates touch events and there is no way to know that they originate from a mouse.).
 
-
 ## Status
 - No official release, **work in progress**.