From e3dd8f967fc96e3dc7805245d202d8134bb2b148 Mon Sep 17 00:00:00 2001
From: Tony Brix <tony@brix.ninja>
Date: Fri, 8 Nov 2024 19:13:37 -0700
Subject: [PATCH] docs: fix indexOf typo

---
 docs/USING_PRO.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/USING_PRO.md b/docs/USING_PRO.md
index a55960f51e..478b9215b4 100644
--- a/docs/USING_PRO.md
+++ b/docs/USING_PRO.md
@@ -388,7 +388,7 @@ An **inline-level** extension will be handled inside each block-level token, bef
 <dt><code><strong>start</strong>(<i>string</i> src)</code></dt>
 <dd>A function that returns the index of the next potential start of the custom token.
 
-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>
+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>
 
 <dt><code><strong>tokenizer</strong>(<i>string</i> src, <i>array</i> tokens)</code></dt>
 <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.