1 files changed, 5 insertions, 4 deletions
diff --git a/README.md b/README.md
index d4fc8f6..4481a6d 100644
--- a/README.md
+++ b/README.md
@@ -459,10 +459,11 @@ test "Scripts" {
 ## Relation to Ziglyph
 zg is a total re-write of some of the components of Ziglyph. The idea was to
 reduce binary size and improve performance. These goals were achieved by using
-trie-like data structures instead of generated functions. Where Ziglyph uses a 
+trie-like data structures (inspired by [Ghostty's implementation](https://mitchellh.com/writing/ghostty-devlog-006))
-function call, zg uses an array lookup, which is quite faster. In addition, all
+instead of generated functions. Where Ziglyph uses a function call, zg uses an 
-these data structures in zg are loaded at runtime from compressed versions in the
+array lookup, which is quite faster. In addition, all these data structures in
-binary. This allows for smaller binary sizes at the expense of increased memory 
+zg are loaded at runtime from compressed versions in the binary. This allows
+for smaller binary sizes at the expense of increased memory 
 footprint at runtime.
 Benchmarks demonstrate the above stated goals have been met:

diff --git a/README.md b/README.md index d4fc8f6..4481a6d 100644 --- a/README.md +++ b/README.md
@@ -459,10 +459,11 @@ test "Scripts" {
459	## Relation to Ziglyph	459	## Relation to Ziglyph
460	zg is a total re-write of some of the components of Ziglyph. The idea was to	460	zg is a total re-write of some of the components of Ziglyph. The idea was to
461	reduce binary size and improve performance. These goals were achieved by using	461	reduce binary size and improve performance. These goals were achieved by using
462	trie-like data structures instead of generated functions. Where Ziglyph uses a	462	trie-like data structures (inspired by [Ghostty's implementation](https://mitchellh.com/writing/ghostty-devlog-006))
463	function call, zg uses an array lookup, which is quite faster. In addition, all	463	instead of generated functions. Where Ziglyph uses a function call, zg uses an
464	these data structures in zg are loaded at runtime from compressed versions in the	464	array lookup, which is quite faster. In addition, all these data structures in
465	binary. This allows for smaller binary sizes at the expense of increased memory	465	zg are loaded at runtime from compressed versions in the binary. This allows
		466	for smaller binary sizes at the expense of increased memory
466	footprint at runtime.	467	footprint at runtime.
467		468
468	Benchmarks demonstrate the above stated goals have been met:	469	Benchmarks demonstrate the above stated goals have been met: