More typos in 3.5 documentation and comments
diff --git a/Lib/test/test_time.py b/Lib/test/test_time.py
index de0cbc4..76b894e 100644
--- a/Lib/test/test_time.py
+++ b/Lib/test/test_time.py
@@ -773,7 +773,7 @@
(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 @@
(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
diff --git a/Misc/NEWS b/Misc/NEWS
index e0ac4fc..e055bd5 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -285,7 +285,7 @@
-----
- 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 @@
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.
diff --git a/Objects/abstract.c b/Objects/abstract.c
index 31cc0a8..039a4ca 100644
--- a/Objects/abstract.c
+++ b/Objects/abstract.c
@@ -2131,7 +2131,7 @@
/* 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;
diff --git a/Objects/methodobject.c b/Objects/methodobject.c
index 1817722..946357f 100644
--- a/Objects/methodobject.c
+++ b/Objects/methodobject.c
@@ -89,7 +89,7 @@
/* 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);