A couple more typos

Author: markshannon

Include/internal/pycore_ceval.h

@@ -219,7 +219,7 @@ static inline int _Py_MakeRecCheck(PyThreadState *tstate)  {
     _PyThreadStateImpl *_tstate = (_PyThreadStateImpl *)tstate;
     // Overflow if stack pointer is between soft limit and the base of the hardware stack.
     // If it is below the hardware stack base, assume that we have the wrong stack limits, and do nothing.
-    // We could have the wrong stack limits becuase of limited platform support, or user-space threads.
+    // We could have the wrong stack limits because of limited platform support, or user-space threads.
 #if _Py_STACK_GROWS_DOWN
     return here_addr < _tstate->c_stack_soft_limit && here_addr >= _tstate->c_stack_soft_limit - 2 * _PyOS_STACK_MARGIN_BYTES;
 #else

InternalDocs/stack_protection.md

@@ -48,7 +48,7 @@ elif stack_pointer < soft_limit:
 
 ### User space threads and other oddities
 
-Some libraries provide user-space threads. These will change the C stack are runtime.
+Some libraries provide user-space threads. These will change the C stack at runtime.
 To guard against this we only raise if the stack pointer is in the window between the expected stack base and the soft limit.
 
 ### Diagnosing and fixing stack overflows