Skip to content

Commit f8e8761

Browse files
authored
chore: update readme
1 parent b4b8443 commit f8e8761

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
# Media Event Filter
22

3-
A dependecy free package providing [HTMLMediaElement](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement) event interpretation: a single source of truth for UI state and KPI tracking, equal across all web platforms.
3+
A dependecy free package, providing [HTMLMediaElement](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement) event interpretation: a single source of truth for UI state and KPI tracking, equal across web platforms.
44

5-
Works in all modern browsers, including web environments like Chromecast, and Smart TVs (LG, Samsung).
5+
Works in modern browsers, including environments like Chromecast and Smart TV (LG, Samsung).
66

7-
Works together with popular player engines, like [shaka](https://github.com/shaka-project/shaka-player), [hls.js](https://github.com/video-dev/hls.js/), [dash.js](https://github.com/Dash-Industry-Forum/dash.js), and native MSE video playback.
7+
Works together with popular player engines: [shaka](https://github.com/shaka-project/shaka-player), [hls.js](https://github.com/video-dev/hls.js/), [dash.js](https://github.com/Dash-Industry-Forum/dash.js), and native MSE video playback.
88

99
## Why
1010

11-
Make UI video playback state and KPI tracking easy.
11+
Make video playback UI state and KPI tracking easy.
1212

13-
The HTML5 video element does not produce a consistent set of events that correspond to the updates required by trackers and user interfaces, like `loaded`, `buffering` or `seeking`. Different browsers, browser versions, and player engines will make the video element behave differently. Events are often emitted in an unpredictable manner regardless of what the specification says, in various edge cases. The media-event-filter wraps these differences, and provides an easy to consume API.
13+
The HTML5 video element does not produce a consistent set of events that correspond to the updates required by trackers and user interfaces, like `loaded`, `buffering` or `seeking`. The video element behaves differently across browsers, browser versions, and player engines. Events are often emitted in an unpredictable manner, regardless of what the specification says. The media-event-filter wraps these differences, and provides an API that is easy to consume.
1414

1515
Adheres to the [Eyevinn Player Analytics Specification](https://github.com/Eyevinn/player-analytics-specification).
1616

0 commit comments

Comments
 (0)