Changed "Objects of different types, except different numeric types, nevercompare equal" to "Objects of different types, unless documented otherwise,never compare equal" to account for documented exceptions like set/frozensetcomparisons.

The acquire() method documentation stated 'Exactly one thread will be awokenby each call to release()' which became incorrect when the n parameter wasadded to release() in Python 3.9.The release() method documentation was ambiguous about behavior whenn > waiting_threads.Changes:- acquire(): Updated to reflect that release(n) wakes min(j,n) threads  where j = waiting threads- release(): Clarified that it wakes 'up to n' threads, or all available  if fewer than n are waitingThe fix aligns documentation with actual implementation behavior inLib/threading.py where release(n) calls Condition.notify(n).

Clarifies that cancelling a Task awaiting another Task or Future willalso cancel the awaited object. This behavior was undocumented despitebeing fundamental to asyncio's cancellation architecture.Changes:- Updated general Task description to mention Task cancellation propagation- Added explicit explanation in Task.cancel() method documentation- Clarified that Tasks inherit Future's cancellation behaviorAddresses issuepython#141186 where users were unaware this cancellationpropagation was intentional architectural behavior, not a side effect.The fix uses the exact wording suggested by the issue reporter anddocuments the _fut_waiter implementation behavior that enables thepropagation down entire await chains.

StanFromIreland left a comment