Apply suggestions from code review

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>

Author: pablogsal

peps/pep-0768.rst

@@ -180,7 +180,7 @@ the target process's memory space. The ``eval_breaker`` and ``remote_debugger_su
 offsets are relative to each ``PyThreadState``, while the ``debugger_pending_call``
 and ``debugger_script`` offsets are relative to each ``_PyRemoteDebuggerSupport``
 structure, allowing the new structure and its fields to be found regardless of
-where they are in memory. ``debugger_script_path_sizee`` informs the attaching
+where they are in memory. ``debugger_script_path_size`` informs the attaching
 tool of the size of the buffer.
 
 Attachment Protocol
@@ -470,11 +470,11 @@ them to force their malicious code to be executed rather than the code the
 debugger intends to run.
 
 Using a Single Runtime Buffer
------------------------------------
+-----------------------------
 
 During the review of this PEP it has been suggested using a single
 shared buffer at the runtime level for all debugger communications. While this
-appeared simpler and requiring less memory, we discovered it would actually prevent scenarios
+appeared simpler and required less memory, we discovered it would actually prevent scenarios
 where multiple debuggers need to coordinate operations across different threads,
 or where a single debugger needs to orchestrate complex debugging operations. A
 single shared buffer would force serialization of all debugging operations,