From 38ee54565ff428de8ae1dffb0f59a14f75281bc7 Mon Sep 17 00:00:00 2001
From: Teiva Harsanyi <934784+teivah@users.noreply.github.com>
Date: Wed, 7 Jun 2023 12:39:05 +0200
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 757f221..329e718 100644
--- a/README.md
+++ b/README.md
@@ -139,7 +139,7 @@ This section contains a summary of the 100 mistakes in the book. Meanwhile, it's
   * [Not using testing utility packages](#not-using-testing-utility-packages-httptest-and-iotest-88)
   * [Writing inaccurate benchmarks](#writing-inaccurate-benchmarks-89) ([Read the full excerpt 👀](https://teivah.medium.com/how-to-write-accurate-benchmarks-in-go-4266d7dd1a95))
   * [Not exploring all the Go testing features](#not-exploring-all-the-go-testing-features-90)
-  * [Not using fuzzing](#not-using-fuzzing-community-mistake) (community mistake, credits: [@jeromedoucet](https://github.com/jeromedoucet))
+  * [Not using fuzzing](#not-using-fuzzing-community-mistake) (community mistake)
 * [Optimizations](#optimizations)
   * [Not understanding CPU caches](#not-understanding-cpu-caches-91)
   * [Writing concurrent code that leads to false sharing](#writing-concurrent-code-that-leads-to-false-sharing-92)
@@ -608,7 +608,7 @@ The `iotest` package helps write io.Reader and test that an application is toler
 
   You can use setup and teardown functions to configure a complex environment, such as in the case of integration tests.
 
-#### Not using fuzzing (community mistake)
+#### Not using fuzzing (community mistake, credits: [@jeromedoucet](https://github.com/jeromedoucet))
 
 Fuzzing is an efficient strategy to detect random, unexpected, or malformed inputs to complex functions and methods in order to discover vulnerabilities, bugs, or even potential crashes.