8000 Minor tweaks · symfony/symfony-docs@82b431a · GitHub
[go: up one dir, main page]

Skip to content

Commit 82b431a

Browse files
committed
Minor tweaks
1 parent c9b27cb commit 82b431a

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

components/clock.rst

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ is expired or not, by modifying the clock's time::
8484
static::assertFalse($expirationChecker->isExpired($validUntil));
8585

8686
// Clock sleeps for 10 minutes, so now is '2022-11-16 15:30:00'
87-
$clock->sleep(600); // Instantly changes time as if we waited for 10 minutes (600secs)
87+
$clock->sleep(600); // Instantly changes time as if we waited for 10 minutes (600 seconds)
8888

8989
// modify the clock, accepts all formats supported by DateTimeImmutable::modify()
9090
static::assertTrue($expirationChecker->isExpired($validUntil));
@@ -99,7 +99,8 @@ is expired or not, by modifying the clock's time::
9999
Monotonic Clock
100100
---------------
101101

102-
The ``MonotonicClock`` allows you to implement a precise stopwatch, depending on the system up to
103-
nanosecond precision. It can be used to measure the elapsed time between 2 calls without being
104-
affected by inconsistencies sometimes introduced by the system clock, e.g. by updating it. Instead,
105-
it consistently increases time, making it especially useful for measuring performance.
102+
The ``MonotonicClock`` allows you to implement a precise stopwatch; depending on
103+
the system up to nanosecond precision. It can be used to measure the elapsed
104+
time between two calls without being affected by inconsistencies sometimes introduced
105+
by the system clock, e.g. by updating it. Instead, it consistently increases time,
106+
making it especially useful for measuring performance.

0 commit comments

Comments
 (0)
0