Skip to content

Commit 34a93a8

Browse files
committed
Fixing the number of tiers to 4
1 parent adb263b commit 34a93a8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -111,15 +111,15 @@ will be implementation-specific and it will be generally expected to reflect
111111
the **performance tier** in which a user device belongs. Higher values
112112
correspond to higher performance tiers.
113113

114-
There will be at least four distinct performance tiers, numbered 1-4, and the
114+
There will be four distinct performance tiers, numbered 1-4, and the
115115
special value 0 will correspond to an unknown performance tier (returned in
116116
case the API's implementation is unable to classify the user device).
117117
Applications using the API should handle additional tiers which are likely to
118118
be added in future as devices improve over time. Implementations should not
119119
redefine tiers; that is, tier 4 devices should not be reclassified as tier 3
120-
to accommodate newer, higher-powered devices as technology improves. Instead
121-
implementations should add a tier 5 for those newer devices when the need
122-
arises, and then a tier 6 and so on.
120+
to accommodate newer, higher-powered devices as technology improves. Instead,
121+
a new tier 5 will be added for those newer devices when the need arises, and
122+
then a tier 6 and so on.
123123

124124
For example, a video conferencing application could interpret the four
125125
performance tiers as follows. Bear in mind that this interpretation is

0 commit comments

Comments
 (0)