Update 0000-timestamp-offset-and-docs.md

Author: ccoffin

rfds/0000-timestamp-offset-and-docs.md

@@ -60,21 +60,21 @@ should also mention the acceptable range of timezone offset values.
 [examples]: #examples
 
 The agreed upon timezone format for timestamp fields in CVE Record Format:
-yyyy-MM-ddTHH:mm:ss.sssZ
-yyyy-MM-ddTHH:mm:ss.sss+HH:mm
-yyyy-MM-ddTHH:mm:ss.sss-HH:mm
+- yyyy-MM-ddTHH:mm:ss.sssZ
+- yyyy-MM-ddTHH:mm:ss.sss+HH:mm
+- yyyy-MM-ddTHH:mm:ss.sss-HH:mm
 
 Note that a CVE producer can provide a timestamp in the form 
 yyyy-MM-ddTHH:mm:ss.sss without a timezone offset being specified. This will 
 be converted to UTC on submission to CVE Services.
 
 Examples:
-2026-02-05T00:53:09.778Z
-2026-02-05T00:53:09.778+06:00
-2026-02-05T00:53:09.778-12:00
+- 2026-02-05T00:53:09.778Z
+- 2026-02-05T00:53:09.778+06:00
+- 2026-02-05T00:53:09.778-12:00
 
 Current regular expression:
-^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.[0-9]+)?(Z|[+-][0-9]{2}:[0-9]{2})?$
+- ^(((2000|2400|2800|(19|2[0-9](0[48]|[2468][048]|[13579][26])))-02-29)|(((19|2[0-9])[0-9]{2})-02-(0[1-9]|1[0-9]|2[0-8]))|(((19|2[0-9])[0-9]{2})-(0[13578]|10|12)-(0[1-9]|[12][0-9]|3[01]))|(((19|2[0-9])[0-9]{2})-(0[469]|11)-(0[1-9]|[12][0-9]|30)))T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.[0-9]+)?(Z|[+-][0-9]{2}:[0-9]{2})?$
 
 Regular expression update: 
 TBD
@@ -149,3 +149,4 @@ timezone offset (outside of the range -12:00 through 14:00)?
 
 TBD
 
+