From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Thu, 31 Oct 2024 21:50:20 +0000 (+0100) Subject: [3.13] gh-126256: Update time.rst to use the same clock as instead of the same clock... X-Git-Tag: v3.13.1~186 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=256fc5529af23f16f0dca2d0e24a936e1c4d67d3;p=thirdparty%2FPython%2Fcpython.git [3.13] gh-126256: Update time.rst to use the same clock as instead of the same clock than (GH-126257) (#126258) gh-126256: Update time.rst to use the same clock as instead of the same clock than (GH-126257) Update time.rst to use `the same clock as` instead of `the same clock than` The time documentation uses the same clock than time.monotonic instead of the same clock as time.monotonic, which is grammatically false. This PR fixes changes two instances of `the same clock than` to `the same clock as`. (cherry picked from commit d0abd0b826cfa574d1515c6f8459c9901939388f) Co-authored-by: Alperen Keleş --- diff --git a/Doc/library/time.rst b/Doc/library/time.rst index 8e29e57d00f9..9cd5db768e98 100644 --- a/Doc/library/time.rst +++ b/Doc/library/time.rst @@ -327,7 +327,7 @@ Functions .. impl-detail:: - On CPython, use the same clock than :func:`time.monotonic` and is a + On CPython, use the same clock as :func:`time.monotonic` and is a monotonic clock, i.e. a clock that cannot go backwards. Use :func:`perf_counter_ns` to avoid the precision loss caused by the @@ -339,7 +339,7 @@ Functions On Windows, the function is now system-wide. .. versionchanged:: 3.13 - Use the same clock than :func:`time.monotonic`. + Use the same clock as :func:`time.monotonic`. .. function:: perf_counter_ns() -> int