Bugfix: Incorrect example in time specification regarding EpochTime.

The EpochTime uses two colons '::'.
Make sure the EpochTime examples appropriately communicates this.

diff --git a/specifications/time.txt b/specifications/time.txt
index 625116ec53a9bc065fd2ea94603c2956b3be4586..4416dab715014a4071861a09aedcdce388c28ee6 100644 (file)
--- a/specifications/time.txt
+++ b/specifications/time.txt
@@ -1,7 +1,7 @@
 # fss-0002 iki-0000
 #
 # license open-standard-license-1.0-or-later
-# version 2024/11/23
+# version 2025/03/22
 #
 # This file (assumed to be named time.txt) can be more easily read using the following iki_read commands:
 #   iki_read time.txt +Q -r UTC UTC -w -WW character "'" "'" code '"' '"'
@@ -56,15 +56,15 @@ Time Specification:
     code:`time:"12345"`.
     code:`time:"2022:12345"`.
     code:`epochtime:"12345"`.
-    code:`epochtime:"2022:12345"`.
+    code:`epochtime:"2022::12345"`.
 
   The bold:"EKI" could be used to designate the standard unit bold:"time" and bold:"epochtime" along with a more explicit base time like the following\:
     code:`day:time:"12345"`.
     code:`day:time:"100:12345"`.
     code:`year:time:"2022:12345"`.
     code:`day:epochtime:"12345"`.
-    code:`day:epochtime:"100:12345"`.
-    code:`year:epochtime:"2022:12345"`.
+    code:`day:epochtime:"100::12345"`.
+    code:`year:epochtime:"2022::12345"`.
 
   In the previous examples for bold:"EKI" show code:"day" along with code:"epochtime".
   For code:`day:epochtime:"100:12345"`, this means that the timestamp starts 100 days after the bold:"UNIX Epoch" year.