Rename Map struct _ not related to hashmap to Map struct not related …

…to hashmap

the file name was causing some git issue on Windows. On Mac/Linux was fine

my_qustions_and_ai_answers/Map struct _ not related to hashmap → my_qustions_and_ai_answers/Map struct not related to hashmap

@@ -148,4 +148,4 @@ Here are a few reasons why the Map struct is needed:
 
 From a user's perspective, you don't need to worry about the Map struct directly. The Rust standard library provides a clean and ergonomic interface for working with iterators, and the existence of the Map struct is an implementation detail that allows the iterator infrastructure to function correctly and efficiently.
 
-When you call `.map(closure)` on an iterator, you're creating a new iterator of type `Map<OriginalIterator, ClosureType>`, but you can treat it like any other iterator and continue chaining other adapter methods or consuming the iterator as needed.
+When you call `.map(closure)` on an iterator, you're creating a new iterator of type `Map<OriginalIterator, ClosureType>`, but you can treat it like any other iterator and continue chaining other adapter methods or consuming the iterator as needed.