Apply Jelle's copy edits

Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>

Author: hoodmane

peps/pep-0776.rst

@@ -110,11 +110,11 @@ there are problems with networking APIs and blocking I/O, and there is no
 support for ``fork()``. See `Emscripten Portability Guidelines
 <https://emscripten.org/docs/porting/guidelines/portability_guidelines.html>`__.
 
-Emscripten executables can be linked with threading support, however, it comes
+Emscripten executables can be linked with threading support, but it comes
 with several limitations:
 
 * Enabling threading requires websites to be served with special security headers
-  that indicate acceptance of the possibility of spectre-style information
+  that indicate acceptance of the possibility of `Spectre <https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)>`__-style information
   leakage. These headers are a usability hazard for users who are not intimately
   familiar with the web platform.
 
@@ -166,7 +166,7 @@ macOS. Upstream tools:
   command line. This emulation behaves best on Linux with macOS as a runner up.
   Node.js is the most convenient way to test Emscripten programs.
 * It is possible to run Emscripten programs inside of any web browser. Browser
-  automation tools like selenium, playwright, or pupeeteer can be used to test
+  automation tools like Selenium, Playwright, or Puppeteer can be used to test
   features that are browser-only.
 
 Pyodide's tools:
@@ -249,7 +249,7 @@ Emscripten file system. There are several possible approaches to this:
   compression to the standard library itself. It also uses the more efficient
   native decompression algorithms of the browser rather than less efficient
   WebAssembly decompression. The disadvantage of this is a higher memory
-  footprint and it breaks ``inspect`` and various tests that do not expect the
+  footprint and it breaks :py:mod:`inspect` and various tests that do not expect the
   standard library to be packaged in this way.
 
 * Put the standard library into an uncompressed tar archive and mount it into a
@@ -273,7 +273,7 @@ default to calling ``console.log`` and ``console.error`` respectively. It is
 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
+behaved TTY in-browser, it is necessary to remove the default I/O devices and
 replace them in a ``preRun`` hook.
 
 Making ``stdin`` work correctly in the browser poses an additional challenge
@@ -317,7 +317,7 @@ switch in order to instantiate a dynamic library synchronously.
 
 To avoid the synchronous loading limit, Pyodide currently preloads all dynamic
 libraries present in a wheel when installing the wheel (or on startup). This is
-a significant disadvantage with packages like scipy that include a very large
+a significant disadvantage with packages like SciPy that include a very large
 number of shared libraries that are expected to be only loaded on demand.
 Pyodide will implement a solution based on stack switching as it becomes more
 widely available in runtimes.
@@ -660,7 +660,7 @@ versions of Python, Node.js, and Emscripten.
 PEP 11
 ------
 
-:pep:`11` will be updated to indicate that Emscripten is supported. Specifically
+:pep:`11` will be updated to indicate that Emscripten is supported, specifically
 the triples ``wasm32-unknown-emscripten_xx_xx_xx``.
 
 Russell Keith-Magee will serve as the initial core team contact for these ABIs.