Skip to content

Commit ea68465

Browse files
committed
use the correct way of referencing a function
1 parent 898796e commit ea68465

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

index.html

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,7 @@ <h2>
212212
</pre>
213213
<dl>
214214
<dt>
215-
<dfn>requestPointerLock</dfn> method
215+
<dfn>requestPointerLock()</dfn> method
216216
</dt>
217217
<dd>
218218
<p>
@@ -241,7 +241,7 @@ <h2>
241241
gesture</a>, or pointer lock has not previously been entered for
242242
this document, an event generated as a result of an <a>engagement
243243
gesture</a> must be received by the document before
244-
<a>requestPointerLock</a> will succeed.
244+
{{requestPointerLock()}} will succeed.
245245
</p>
246246
<aside class="note" data-link-for="Document">
247247
<p>
@@ -251,7 +251,7 @@ <h2>
251251
re-engages directly with the document.
252252
</p>
253253
<p>
254-
Conversely, if pointer lock is exited via <a>exitPointerLock</a>
254+
Conversely, if pointer lock is exited via {{exitPointerLock()}}
255255
no <a>engagement gesture</a> is required to reenter pointer lock.
256256
This enables applications that frequently move between
257257
interaction modes, and ones that may do so based on a timer or
@@ -260,7 +260,7 @@ <h2>
260260
<p data-link-for="Element">
261261
Pointer lock is commonly combined with fullscreen [[FULLSCREEN]],
262262
and if an <a>engagement gesture</a> is used to enter fullscreen
263-
it is sufficient for a subsequent <a>requestPointerLock</a>.
263+
it is sufficient for a subsequent {{requestPointerLock()}}.
264264
</p>
265265
</aside>
266266
<p>
@@ -327,7 +327,7 @@ <h2>
327327
</p>
328328
</dd>
329329
<dt>
330-
<dfn>exitPointerLock</dfn> method
330+
<dfn>exitPointerLock()</dfn> method
331331
</dt>
332332
<dd>
333333
<p>

0 commit comments

Comments
 (0)