More typos in 3.5 documentation and comments

Lib/test/test_time.py

@@ -773,7 +773,7 @@ class TestPyTime_t(unittest.TestCase):
                 (2**23 - 1e-9,  8388607999999999),
                 (2**23,         8388608000000000),
 
-                # start loosing precision for value > 2^23 seconds
+                # start losing precision for value > 2^23 seconds
                 (2**23 + 1e-9,  8388608000000002),
 
                 # nanoseconds are lost for value > 2^23 seconds
@@ -848,7 +848,7 @@ class TestPyTime_t(unittest.TestCase):
             (4194304000000000, 2**22),
             (4194304000000001, 2**22 + 1e-9),
 
-            # start loosing precision for value > 2^23 seconds
+            # start losing precision for value > 2^23 seconds
             (8388608000000002, 2**23 + 1e-9),
 
             # nanoseconds are lost for value > 2^23 seconds

Misc/NEWS

@@ -285,7 +285,7 @@ Build
 -----
 
 - Issue #24915: Add LLVM support for PGO builds and use the test suite to
-  generate the profile data. Initiial patch by Alecsandru Patrascu of Intel.
+  generate the profile data. Initial patch by Alecsandru Patrascu of Intel.
 
 - Issue #24910: Windows MSIs now have unique display names.
 
@@ -1693,7 +1693,7 @@ Core and Builtins
   type) can now be weakref'ed.  Patch by Wei Wu.
 
 - Issue #22077: Improve index error messages for bytearrays, bytes, lists,
-  and tuples by adding 'or slices'. Added ', not <typename' for bytearrays.
+  and tuples by adding 'or slices'. Added ', not <typename>' for bytearrays.
   Original patch by Claudiu Popa.
 
 - Issue #20179: Apply Argument Clinic to bytes and bytearray.

Objects/abstract.c

@@ -2131,7 +2131,7 @@ PyObject_Call(PyObject *func, PyObject *arg, PyObject *kw)
 
     /* PyObject_Call() must not be called with an exception set,
        because it may clear it (directly or indirectly) and so the
-       caller looses its exception */
+       caller loses its exception */
     assert(!PyErr_Occurred());
 
     call = func->ob_type->tp_call;

Objects/methodobject.c

@@ -89,7 +89,7 @@ PyCFunction_Call(PyObject *func, PyObject *args, PyObject *kwds)
 
     /* PyCFunction_Call() must not be called with an exception set,
        because it may clear it (directly or indirectly) and so the
-       caller looses its exception */
+       caller loses its exception */
     assert(!PyErr_Occurred());
 
     flags = PyCFunction_GET_FLAGS(func) & ~(METH_CLASS | METH_STATIC | METH_COEXIST);