Skip to content

Commit 1f90f6f

Browse files
Honrybeaufortfrancois
authored andcommitted
Fixed some nits (#525)
1 parent 916416b commit 1f90f6f

File tree

1 file changed

+41
-41
lines changed

1 file changed

+41
-41
lines changed

index.html

Lines changed: 41 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -269,29 +269,29 @@ <h2>The NFC Standard</h2>
269269
<p>
270270
A note about the NDEF mapping can be found here:
271271
<a href="https://www.nxp.com/docs/en/application-note/AN1305.pdf">
272-
MIFARE Classic as NFC Type MIFARE Classic Tag</a>
272+
MIFARE Classic as NFC Type MIFARE Classic Tag</a>.
273273
</p>
274274
<div>
275275
<ol>
276276
<li>
277277
<dfn>NFC Forum Type 1</dfn>: This tag is based on the ISO/IEC 14443-3A
278278
(NFC-A). The tags are rewritable and can be
279279
configured to become read-only. Memory size can be between `96` bytes and
280-
`2` Kbytes. Communication speed is `106` kbit/sec. In contrast to all other
280+
`2` Kbytes. Communication speed is `106` kbit/s. In contrast to all other
281281
types, these tags have no anti-collision protection for dealing with multiple
282282
tags within the NFC field.
283283
</li>
284284
<li>
285285
<dfn>NFC Forum Type 2</dfn>: This tag is based on the
286286
ISO/IEC 14443-3A (NFC-A). The tags are rewritable and can be configured
287287
to become read-only. Memory size can be between `48` bytes and `2` Kbytes.
288-
Communication speed is `106` kbit/sec.
288+
Communication speed is `106` kbit/s.
289289
</li>
290290
<li>
291291
<dfn>NFC Forum Type 3</dfn>: This tag is based on the Japanese Industrial
292292
Standard (JIS) X 6319-4 (ISO/IEC 18092), commonly known as FeliCa. The tags are
293293
preconfigured to be either rewritable or read-only. Memory is `2` kbytes.
294-
Communication speed is `212` kbit/sec or `424` kbit/s.
294+
Communication speed is `212` kbit/s or `424` kbit/s.
295295
</li>
296296
<li>
297297
<dfn>NFC Forum Type 4</dfn>: This tag is based on the ISO/IEC 14443-4 A/B
@@ -305,21 +305,21 @@ <h2>The NFC Standard</h2>
305305
</li>
306306
<li>
307307
<dfn>NFC Forum Type 5</dfn>: This tag is based on ISO/IEC 15693 (NFC-V) and
308-
allows reading and writing an NDEF message on a ISO/IEC 15693 RF tag
308+
allows reading and writing an NDEF message on an ISO/IEC 15693 RF tag
309309
that is accessible by long range RFID readers as well. The NFC communication
310310
is limited to short distance and may use the <i>Active Communication Mode</i> of
311311
ISO/IEC 18092 where the sending peer generates the field which balances
312312
power consumption and improves link stability. Variable memory, up to `64` kbytes.
313-
Communication speed `26.48` kbit/s
313+
Communication speed is `26.48` kbit/s.
314314
</li>
315315
<li>
316316
<dfn>MIFARE Standard</dfn>: This tag, often sold under the brand names MIFARE
317317
Classic or MIFARE Mini, is based on the ISO/IEC 14443-3A (also known as NFC-A,
318318
as defined in ISO/IEC 14443-3:2011, Part 3: Initialization and anticollision).
319319
The tags are rewritable and can be configured to become read-only. Memory size
320-
can be between `320` and `4` kbytes. Communication speed is `106` kbit/sec.
320+
can be between `320` and `4` kbytes. Communication speed is `106` kbit/s.
321321
<p class="note">
322-
<a>MIFARE Standard</a> is a not an NFC Forum type and can only be read by devices
322+
<a>MIFARE Standard</a> is not an NFC Forum type and can only be read by devices
323323
using NXP hardware. Support for reading and writing to tags based on the
324324
<a>MIFARE Standard</a> is thus non-nominative, but the type is included
325325
due to the popularity and use in legacy systems.
@@ -499,7 +499,7 @@ <h4>
499499
The type information stored in the <a>TYPE field</a> of
500500
<a>well-known type records</a> can be of two kinds:
501501
<a href="#well-known-local-types">local types</a>
502-
and <a href="#well-known-global-types">global types</a>
502+
and <a href="#well-known-global-types">global types</a>.
503503
</p>
504504

505505
<section><h4>Well-known local types</h4>
@@ -874,7 +874,7 @@ <h4>
874874
Writing to an empty, but formatted <a>NFC tag</a>.
875875
</li>
876876
<li>
877-
Writing to an <a>NFC tag</a> which already contains a
877+
Writing to an <a>NFC tag</a> which already contains an
878878
<a>NDEF message</a>.
879879
</li>
880880
<li>
@@ -1304,8 +1304,8 @@ <h4>
13041304
},
13051305
{
13061306
recordType: "mime",
1307-
mediaType: "image/png"
1308-
data: getImageBytes(fromURL);
1307+
mediaType: "image/png",
1308+
data: getImageBytes(fromURL)
13091309
}
13101310
]
13111311
}
@@ -1384,7 +1384,7 @@ <h4>
13841384
<a>NDEF message</a>.
13851385
</p>
13861386
<p data-dfn-for="NDEFMessageInit">
1387-
The <dfn>NDEFMessageInit</dfn> dictionary is used to initialize a
1387+
The <dfn>NDEFMessageInit</dfn> dictionary is used to initialize an
13881388
<a>NDEF message</a>.
13891389
</p>
13901390
</section>
@@ -1523,7 +1523,7 @@ <h4>
15231523
<section>
15241524
<h2>The <dfn>record type</dfn> string</h2>
15251525
<p>
1526-
This string defines the allowed record types for a <a>NDEFRecord</a>. The
1526+
This string defines the allowed record types for an <a>NDEFRecord</a>. The
15271527
[[[#data-mapping]]] section describes how it is mapped to
15281528
<a>NDEF record</a> types.
15291529
</p>
@@ -2680,7 +2680,7 @@ <h3><dfn>Writing content</dfn></h3>
26802680

26812681
<section><h3>Validating local type</h3>
26822682
<p>
2683-
To <dfn>validate local type</dfn> given a |input:USVString| run
2683+
To <dfn>validate local type</dfn> given an |input:USVString| run
26842684
these steps:
26852685
</p>
26862686
<ol class=algorithm id="validate-local-type">
@@ -2755,7 +2755,7 @@ <h3><dfn>Writing content</dfn></h3>
27552755
[= exception/throw =] a {{TypeError}} and abort these steps.
27562756
</li>
27572757
<li>
2758-
If the type of |record|'s <a>data</a> is not a {{DOMString}} or a
2758+
If the type of |record|'s <a>data</a> is not {{DOMString}} or
27592759
{{BufferSource}}, [= exception/throw =] a {{TypeError}} and abort
27602760
these steps.
27612761
</li>
@@ -2978,7 +2978,7 @@ <h3><dfn>Writing content</dfn></h3>
29782978
and |ndef|, run these steps:
29792979
<ol class=algorithm data-link-for="NDEFRecord">
29802980
<li>
2981-
If the type of a |record|'s <a>data</a> is not a
2981+
If the type of a |record|'s <a>data</a> is not
29822982
{{BufferSource}}, [= exception/throw =] a {{TypeError}}
29832983
and abort these steps.
29842984
</li>
@@ -3035,7 +3035,7 @@ <h3><dfn>Writing content</dfn></h3>
30353035
[= exception/throw =] a {{TypeError}} and abort these steps.
30363036
</li>
30373037
<li>
3038-
If the type of a |record|'s <a>data</a> is not a
3038+
If the type of a |record|'s <a>data</a> is not
30393039
{{BufferSource}} or {{NDEFMessageInit}}, [= exception/throw =] a
30403040
{{TypeError}} and abort these steps.
30413041
</li>
@@ -3048,7 +3048,7 @@ <h3><dfn>Writing content</dfn></h3>
30483048
<a>recordType</a>.
30493049
</li>
30503050
<li>
3051-
If the type of a |record|'s <a>data</a> is a {{BufferSource}},
3051+
If the type of a |record|'s <a>data</a> is {{BufferSource}},
30523052
<ol>
30533053
<li>
30543054
Set |arrayBuffer| to |record|'s <a>data</a>.
@@ -3069,7 +3069,7 @@ <h3><dfn>Writing content</dfn></h3>
30693069
</ol>
30703070
</li>
30713071
<li>
3072-
If the type of a |record|'s <a>data</a> is a {{NDEFMessageInit}},
3072+
If the type of a |record|'s <a>data</a> is {{NDEFMessageInit}},
30733073
<ol>
30743074
<li>
30753075
Set the |ndef|'s <a>PAYLOAD field</a> to the result of running
@@ -3098,7 +3098,7 @@ <h3><dfn>Writing content</dfn></h3>
30983098
[= exception/throw =] a {{TypeError}} and abort these steps.
30993099
</li>
31003100
<li>
3101-
If the type of a |record|'s <a>data</a> is not a
3101+
If the type of a |record|'s <a>data</a> is not
31023102
{{BufferSource}} or {{NDEFMessageInit}}, [= exception/throw =] a
31033103
{{TypeError}} and abort these steps.
31043104
</li>
@@ -3116,7 +3116,7 @@ <h3><dfn>Writing content</dfn></h3>
31163116
<a>local type name</a>.
31173117
</li>
31183118
<li>
3119-
If the type of a |record|'s <a>data</a> is a {{BufferSource}},
3119+
If the type of a |record|'s <a>data</a> is {{BufferSource}},
31203120
<ol>
31213121
<li>
31223122
Set |arrayBuffer| to |record|'s <a>data</a>.
@@ -3137,7 +3137,7 @@ <h3><dfn>Writing content</dfn></h3>
31373137
</ol>
31383138
</li>
31393139
<li>
3140-
If the type of a |record|'s <a>data</a> is a {{NDEFMessageInit}},
3140+
If the type of a |record|'s <a>data</a> is {{NDEFMessageInit}},
31413141
<ol>
31423142
<li>
31433143
Set the |ndef|'s <a>PAYLOAD field</a> to the result of running
@@ -3166,7 +3166,7 @@ <h3><dfn>Writing content</dfn></h3>
31663166
[= exception/throw =] a {{TypeError}} and abort these steps.
31673167
</li>
31683168
<li>
3169-
If the type of a |record|'s <a>data</a> is not a
3169+
If the type of a |record|'s <a>data</a> is not
31703170
{{NDEFMessageInit}}, [= exception/throw =] a {{TypeError}}
31713171
and abort these steps.
31723172
</li>
@@ -3655,19 +3655,19 @@ <h3>Parsing content</h3>
36553655
<dt>"`T`" (`0x54`)</dt>
36563656
<ul>
36573657
<li>
3658-
running <a>parse an NDEF text record</a> on |ndef|.
3658+
Running <a>parse an NDEF text record</a> on |ndef|.
36593659
</li>
36603660
</ul>
36613661
<dt>"`U`" (`0x55`)</dt>
36623662
<ul>
36633663
<li>
3664-
running <a>parse an NDEF URL record</a> on |ndef|
3664+
Running <a>parse an NDEF URL record</a> on |ndef|.
36653665
</li>
36663666
</ul>
36673667
<dt>"`Sp`" (`0x53` `0x70`)</dt>
36683668
<ul>
36693669
<li>
3670-
running <a>parse an NDEF smart-poster record</a> on |ndef|
3670+
Running <a>parse an NDEF smart-poster record</a> on |ndef|.
36713671
</li>
36723672
</ul>
36733673
</dl>
@@ -3705,7 +3705,7 @@ <h3>Parsing content</h3>
37053705

37063706
<section><h3>Parsing NDEF well-known `T` records</h3>
37073707
<div>
3708-
To <dfn>parse an NDEF text record</dfn> given a |ndefRecord| into a
3708+
To <dfn>parse an NDEF text record</dfn> given an |ndefRecord| into a
37093709
|record:NDEFRecord|, run these steps:
37103710
<ol class=algorithm data-link-for="NDEFRecord">
37113711
<li>
@@ -3745,7 +3745,7 @@ <h3>Parsing content</h3>
37453745
Set |record|'s <a>data</a> to |buffer|.
37463746
</li>
37473747
<li>
3748-
return |record|.
3748+
Return |record|.
37493749
</li>
37503750
</ol> <!-- parsing NDEF text record -->
37513751
</div>
@@ -3792,7 +3792,7 @@ <h3>Parsing content</h3>
37923792

37933793
<section><h3>Parsing NDEF well-known `U` records</h3>
37943794
<div>
3795-
To <dfn>parse an NDEF URL record</dfn> given a |ndefRecord| into a
3795+
To <dfn>parse an NDEF URL record</dfn> given an |ndefRecord| into a
37963796
|record:NDEFRecord|, run these steps:
37973797
<ol class=algorithm data-link-for="NDEFRecord">
37983798
<li>
@@ -3832,15 +3832,15 @@ <h3>Parsing content</h3>
38323832
|record|'s <a>data</a> to |buffer|.
38333833
</li>
38343834
<li>
3835-
return |record|.
3835+
Return |record|.
38363836
</li>
38373837
</ol> <!-- parsing NDEF URL record -->
38383838
</div>
38393839
</section>
38403840

38413841
<section><h3>Parsing NDEF well-known `Sp` records</h3>
38423842
<div>
3843-
To <dfn>parse an NDEF smart-poster record</dfn> given a |ndefRecord| into a
3843+
To <dfn>parse an NDEF smart-poster record</dfn> given an |ndefRecord| into a
38443844
|record:NDEFRecord|, run these steps:
38453845
<ol class=algorithm data-link-for="NDEFRecord">
38463846
<li>
@@ -3861,15 +3861,15 @@ <h3>Parsing content</h3>
38613861
Set |record|'s <a>data</a> to |buffer|.
38623862
</li>
38633863
<li>
3864-
return |record|.
3864+
Return |record|.
38653865
</li>
38663866
</ol> <!-- parsing NDEF smart-poster record -->
38673867
</div>
38683868
</section>
38693869

38703870
<section><h3>Parsing NDEF MIME type records</h3>
38713871
<div>
3872-
To <dfn>parse an NDEF MIME type record</dfn> given a |ndefRecord| into a
3872+
To <dfn>parse an NDEF MIME type record</dfn> given an |ndefRecord| into a
38733873
|record:NDEFRecord|, run these steps:
38743874
<ol class=algorithm data-link-for="NDEFRecord">
38753875
<li>
@@ -3889,15 +3889,15 @@ <h3>Parsing content</h3>
38893889
Set |record|'s <a>data</a> to |buffer|.
38903890
</li>
38913891
<li>
3892-
return |record|.
3892+
Return |record|.
38933893
</li>
38943894
</ol> <!-- parsing NDEF MIME type record -->
38953895
</div>
38963896
</section>
38973897

38983898
<section><h3>Parsing NDEF absolute-URL records</h3>
38993899
<div>
3900-
To <dfn>parse an NDEF absolute-URL record</dfn> given a |ndefRecord| into
3900+
To <dfn>parse an NDEF absolute-URL record</dfn> given an |ndefRecord| into
39013901
a |record:NDEFRecord|, run these steps:
39023902
<ol class=algorithm data-link-for="NDEFRecord">
39033903
<li>
@@ -3914,15 +3914,15 @@ <h3>Parsing content</h3>
39143914
Set |record|'s <a>data</a> to |buffer|.
39153915
</li>
39163916
<li>
3917-
return |record|.
3917+
Return |record|.
39183918
</li>
39193919
</ol> <!-- parsing NDEF absolute URI record -->
39203920
</div>
39213921
</section>
39223922

39233923
<section><h3>Parsing NDEF external type records</h3>
39243924
<div>
3925-
To <dfn>parse an NDEF external type record</dfn> given a |ndefRecord| into
3925+
To <dfn>parse an NDEF external type record</dfn> given an |ndefRecord| into
39263926
a |record:NDEFRecord|, run these steps:
39273927
<ol class=algorithm data-link-for="NDEFRecord">
39283928
<li>
@@ -3941,15 +3941,15 @@ <h3>Parsing content</h3>
39413941
Set |record|'s <a>data</a> to |buffer|.
39423942
</li>
39433943
<li>
3944-
return |record|.
3944+
Return |record|.
39453945
</li>
39463946
</ol> <!-- parsing NDEF external type record -->
39473947
</div>
39483948
</section>
39493949

39503950
<section><h3>Parsing NDEF unknown type records</h3>
39513951
<div>
3952-
To <dfn>parse an NDEF unknown record</dfn> given a |ndefRecord| into a
3952+
To <dfn>parse an NDEF unknown record</dfn> given an |ndefRecord| into a
39533953
|record:NDEFRecord|, run these steps:
39543954
<ol class=algorithm data-link-for="NDEFRecord">
39553955
<li>
@@ -3967,7 +3967,7 @@ <h3>Parsing content</h3>
39673967
Set |record|'s <a>data</a> to |buffer|.
39683968
</li>
39693969
<li>
3970-
return |record|.
3970+
Return |record|.
39713971
</li>
39723972
</ol> <!-- parsing NDEF unknown record -->
39733973
</div>

0 commit comments

Comments
 (0)