add compressed imgs

ishtms · Sep 16, 2023 · 563b3b7 · 563b3b7
1 parent dff4c32
commit 563b3b7
Show file tree

Hide file tree

Showing 24 changed files with 1 addition and 6 deletions.
diff --git a/assets/imgs/compressed/Untitled-2023-07-28-1312.png b/assets/imgs/compressed/Untitled-2023-07-28-1312.png
diff --git a/assets/imgs/compressed/call-stack.png b/assets/imgs/compressed/call-stack.png
diff --git a/assets/imgs/compressed/client-server.png b/assets/imgs/compressed/client-server.png
diff --git a/assets/imgs/compressed/cover.jpg b/assets/imgs/compressed/cover.jpg
diff --git a/assets/imgs/compressed/elysia-claim.png b/assets/imgs/compressed/elysia-claim.png
diff --git a/assets/imgs/compressed/hello-world.png b/assets/imgs/compressed/hello-world.png
diff --git a/assets/imgs/compressed/idle_memory.png b/assets/imgs/compressed/idle_memory.png
diff --git a/assets/imgs/compressed/intellisense.png b/assets/imgs/compressed/intellisense.png
diff --git a/assets/imgs/compressed/latency_2.png b/assets/imgs/compressed/latency_2.png
diff --git a/assets/imgs/compressed/latency_without_max.png b/assets/imgs/compressed/latency_without_max.png
diff --git a/assets/imgs/compressed/max_latency.png b/assets/imgs/compressed/max_latency.png
diff --git a/assets/imgs/compressed/mem_const_load.png b/assets/imgs/compressed/mem_const_load.png
diff --git a/assets/imgs/compressed/mem_const_load_2.png b/assets/imgs/compressed/mem_const_load_2.png
diff --git a/assets/imgs/compressed/mem_idle_2.png b/assets/imgs/compressed/mem_idle_2.png
diff --git a/assets/imgs/compressed/modular-function-ch6.png b/assets/imgs/compressed/modular-function-ch6.png
diff --git a/assets/imgs/compressed/next.png b/assets/imgs/compressed/next.png
diff --git a/assets/imgs/compressed/prev.png b/assets/imgs/compressed/prev.png
diff --git a/assets/imgs/compressed/referer.png b/assets/imgs/compressed/referer.png
diff --git a/assets/imgs/compressed/rps.png b/assets/imgs/compressed/rps.png
diff --git a/assets/imgs/compressed/rps_2.png b/assets/imgs/compressed/rps_2.png
diff --git a/assets/imgs/compressed/trie-eow.png b/assets/imgs/compressed/trie-eow.png
diff --git a/assets/imgs/compressed/trie-overview.png b/assets/imgs/compressed/trie-overview.png
diff --git a/assets/imgs/compressed/user-agent.png b/assets/imgs/compressed/user-agent.png
diff --git a/chapters/ch07.0-ex-implementing-a-trie.md b/chapters/ch07.0-ex-implementing-a-trie.md
@@ -1,6 +1,6 @@
 [![Read Prev](/assets/imgs/prev.png)](/chapters/ch06.4-the-need-for-a-trie.md)
 
-# Exercise - Implementing a `Trie`
+# Exercises - Implementing a `Trie`
 
 > This exercise will motivate you to work on implementing your solution independently. Once you have completed the exercise, you can move on to the next challenge or read the solution to find a different approach.
 >
@@ -25,9 +25,7 @@ The Trie starts with a root node that doesn't hold any character. It serves as t
 ```
 
 -   **Level 1**: You have the characters "O", "T", and "C" branching from the root node.
-
 -   **Level 2 and Beyond**: These nodes further branch out to form the words.
-
     -   "O" branches to "K", completing the word "OK".
     -   "T" branches to "O", completing the word "TO".
     -   "C" branches to "A" and "U":
@@ -53,15 +51,12 @@ In this first challenge, your task is to implement a Trie data structure with on
 ### Requirements
 
 1. Create a class called `Trie`.
-
 2. Implement an `insert(word)` method that takes a string `word` and inserts it into the Trie.
 
 ### More details
 
 1. **Initialization**: You'll begin with a root node. This node will be the starting point for all word insertions, and it won't store any character itself.
-
 2. **Traversal**: For each character in the word you want to insert, you'll traverse the Trie from the root node, going as far down as the current character sequence allows.
-
 3. **Node Creation**: If a character in the word doesn't match any child node of the current node:
 
     - Create a new node for that character.