From 3ab7fe6876a2cc0395865e6f4851b477b1de7ae5 Mon Sep 17 00:00:00 2001 From: Joe Ardent Date: Tue, 25 Jul 2023 17:54:20 -0700 Subject: [PATCH] fix images maybe --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c856b0c..6400e5d 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ but not all ULIDs are Julids) identifiers with the following properties: It's that last bit that makes them distinctive. ULIDs have the following big-endian bit structure: -![ULID bit structure][./ulid.svg] +![ULID bit structure](./ulid.svg) According to the ULID spec, for ULIDs created in the same millisecond, the least-significant bit should be incremented for each new one. Since that portion of the ULID is random, that means you may @@ -43,7 +43,7 @@ millisecond. To address these shortcomings, Julids (Joe's ULIDs) have the following big-endian bit structure: -![Julid bit structure][./julid.svg] +![Julid bit structure](./julid.svg]) As with ULIDs, the 48 most-significant bits encode the time of creation. Unlike ULIDs, the next 16 bits are not random, they're a monotonic counter for IDs created within the same millisecond. Since