From 6b3acf6063c092cbf77734c72e3f066a5d0021f2 Mon Sep 17 00:00:00 2001
From: Teiva Harsanyi <teiva.harsanyi@gmail.com>
Date: Thu, 29 Sep 2022 17:07:28 +0200
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index ca6c355..14558dc 100644
--- a/README.md
+++ b/README.md
@@ -158,7 +158,7 @@ Working with a slice of pointers or structs with pointer fields, you can avoid m
 
 See [#21](#inefficient-slice-initialization-21).
 
-#### Map and memory leaks (#28)
+#### [Map and memory leaks](https://teivah.medium.com/maps-and-memory-leaks-in-go-a85ebe6e7e69) (#28)
 
 A map can always grow in memory, but it never shrinks. Hence, if it leads to some memory issues, you can try different options, such as forcing Go to recreate the map or using pointers.