Skip to content

Commit dc4ae3b

Browse files
authored
docs: fix indexOf typo (#3526)
1 parent 10a53d9 commit dc4ae3b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/USING_PRO.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -388,7 +388,7 @@ An **inline-level** extension will be handled inside each block-level token, bef
388388
<dt><code><strong>start</strong>(<i>string</i> src)</code></dt>
389389
<dd>A function that returns the index of the next potential start of the custom token.
390390

391-
The index can be the result of a <code>src.match().index</code>, or even a simple <code>src.index()</code>. Marked will use this function to ensure that it does not skip over any text that should be part of the custom token.</dd>
391+
The index can be the result of a <code>src.match().index</code>, or even a simple <code>src.indexOf()</code>. Marked will use this function to ensure that it does not skip over any text that should be part of the custom token.</dd>
392392

393393
<dt><code><strong>tokenizer</strong>(<i>string</i> src, <i>array</i> tokens)</code></dt>
394394
<dd>A function that reads string of Markdown text and returns a generated token. The token pattern should be found at the beginning of the <code>src</code> string. Accordingly, if using a Regular Expression to detect a token, it should be anchored to the string start (`^`). The <code>tokens</code> parameter contains the array of tokens that have been generated by the lexer up to that point, and can be used to access the previous token, for instance.

0 commit comments

Comments
 (0)