From f4cd4d1d4ecaed4fa82223b066995a3c262f8a49 Mon Sep 17 00:00:00 2001 From: mine-cetinkaya-rundel Date: Sun, 9 Apr 2023 22:23:01 -0400 Subject: [PATCH] Fix ISO typo, closes #1415 --- datetimes.qmd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/datetimes.qmd b/datetimes.qmd index 75edc4c..c687432 100644 --- a/datetimes.qmd +++ b/datetimes.qmd @@ -92,8 +92,8 @@ csv <- " read_csv(csv) ``` -If you haven't heard of **ISO8601** before, it's an international standard[^datetimes-2] for writing dates where the components of a date are organized from biggest to smallest separated by `-`. For example, in ISO8601 March 5 2022 is `2022-05-03`. ISO8601 dates can also include times, where hour, minute, and second are separated by `:`, and the date and time components are separated by either a `T` or a space. -For example, you could write 4:26pm on March 5 2022 as either `2022-05-03 16:26` or `2022-05-03T16:26`. +If you haven't heard of **ISO8601** before, it's an international standard[^datetimes-2] for writing dates where the components of a date are organized from biggest to smallest separated by `-`. For example, in ISO8601 May 3 2022 is `2022-05-03`. ISO8601 dates can also include times, where hour, minute, and second are separated by `:`, and the date and time components are separated by either a `T` or a space. +For example, you could write 4:26pm on May 3 2022 as either `2022-05-03 16:26` or `2022-05-03T16:26`. [^datetimes-2]: