Remove broken js:func refs

Author: hoodmane

peps/pep-0776.rst

@@ -14,8 +14,9 @@ Abstract
 ========
 
 `Emscripten <https://emscripten.org/>`__ is a complete open source compiler
-toolchain. It compiles C/C++ code into WebAssembly/JavaScript executables,
-for use in JavaScript runtimes, including browsers and Node.js.
+toolchain. It compiles C/C++ code into WebAssembly/JavaScript executables, for
+use in JavaScript runtimes, including browsers and Node.js. The Rust language
+also maintains an Emscripten target.
 
 This PEP formalizes the addition of Tier 3 for Emscripten support in Python 3.14
 which `was approved by the Steering Council on October 25, 2024
@@ -195,13 +196,13 @@ shut down the runtime on exit. It also includes an implementation for all of the
 system calls, including the file system, the dynamic loader, and any logic to
 expose additional functionality from the JavaScript runtime to C code.
 
-The ``.mjs`` file exports a single :js:func:`bootstrapEmscriptenExecutable()`
+The ``.mjs`` file exports a single ``bootstrapEmscriptenExecutable()``
 JavaScript function that bootstraps the runtime, calls the ``main()`` function,
 and returns an API object that can be used to call C functions. Each time it is
 called produces a complete and independent copy of the runtime with its own
 separate address space.
 
-The :js:func:`bootstrapEmscriptenExecutable()` takes a large number of runtime
+The ``bootstrapEmscriptenExecutable()`` takes a large number of runtime
 settings. `The full list is described in the Emscripten documentation here.
 <https://emscripten.org/docs/api_reference/module.html#id3>`__ The most
 important of these are as follows:
@@ -296,7 +297,7 @@ Console and Interactive Usage
 
 ``stdin`` defaults to always returning ``EOF``, while ``stdout`` and ``stderr``
 default to calling ``console.log`` and ``console.error`` respectively. It is
-possible to pass handlers to :js:func:`bootstrapEmscriptenExecutable()` to configure
+possible to pass handlers to ``bootstrapEmscriptenExecutable()`` to configure
 the standard streams, but no matter what the I/O devices have undesirable line
 buffering behavior that forces a new line when flushed. To implement a well
 behaved TTY in-browser, it is necessary to remove the default I/O devices and
@@ -421,7 +422,7 @@ traceback.
 
 Because Emscripten Python currently has no JavaScript API and no foreign function
 interface, the situation is much simpler. The Python Node.js runner wraps the call
-to :js:func:`bootstrapEmscriptenExecutable()` in a try/catch block. If an exception is
+to ``bootstrapEmscriptenExecutable()`` in a try/catch block. If an exception is
 caught, it displays the JavaScript exception and calls ``_Py_DumpTraceback()``.
 It then exits with code 1. We will stick with this approach until we add either
 a JavaScript API or foreign function interface, which is out of scope for this PEP.