Apply suggestions from code review

Co-authored-by: Matt Wozniski <godlygeek@gmail.com>

Author: pablogsal

peps/pep-0768.rst

@@ -132,14 +132,11 @@ Runtime State Extensions
 
 A new structure is added to PyThreadState to support remote debugging:
 
-debugging:
-
 .. code-block:: C
 
     typedef struct _remote_debugger_support {
         int debugger_pending_call;
         char debugger_script_path[MAX_SCRIPT_PATH_SIZE];
-        char *debugger_buffer;
         Py_ssize_t debugger_buffer_size;
     } _PyRemoteDebuggerSupport;
 
@@ -475,7 +472,7 @@ 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 requring less memory , we discovered it would actually prevent scenarios
+appeared simpler and requiring 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,