Skip to content

Commit 445d2c8

Browse files
committed
minor fixes
1 parent 7211729 commit 445d2c8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

1-js/05-data-types/11-date/article.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -388,7 +388,7 @@ The string format should be: `YYYY-MM-DDTHH:mm:ss.sssZ`, where:
388388
- `YYYY-MM-DD` -- is the date: year-month-day.
389389
- The character `"T"` is used as the delimiter.
390390
- `HH:mm:ss.sss` -- is the time: hours, minutes, seconds and milliseconds.
391-
- The optional `'Z'` part denotes the time zone in the format `+-hh:mm`. A single letter `Z` that would mean UTC+0.
391+
- The optional `'Z'` part denotes the time zone in the format `+-hh:mm`. A single letter `Z` would mean UTC+0.
392392

393393
Shorter variants are also possible, like `YYYY-MM-DD` or `YYYY-MM` or even `YYYY`.
394394

@@ -427,7 +427,7 @@ Sometimes we need more precise time measurements. JavaScript itself does not hav
427427
alert(`Loading started ${performance.now()}ms ago`);
428428
// Something like: "Loading started 34731.26000000001ms ago"
429429
// .26 is microseconds (260 microseconds)
430-
// more than 3 digits after the decimal point are precision errors, but only the first 3 are correct
430+
// more than 3 digits after the decimal point are precision errors, only the first 3 are correct
431431
```
432432

433433
Node.js has `microtime` module and other ways. Technically, almost any device and environment allows to get more precision, it's just not in `Date`.

0 commit comments

Comments
 (0)