From d18b1e24a68da99d93806578bbb98e2c56cd0648 Mon Sep 17 00:00:00 2001
From: MusicalNinjaDad <102677655+MusicalNinjaDad@users.noreply.github.com>
Date: Wed, 15 Apr 2026 12:42:16 +0200
Subject: [PATCH] Clarify complexity criticism in hacking.md

Rephrase section title and clarify complexity criticism.
---
 docs/hacking.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/hacking.md b/docs/hacking.md
index 315c7ea..b63445a 100644
--- a/docs/hacking.md
+++ b/docs/hacking.md
@@ -25,7 +25,7 @@ To date I've thought about using the trait multiple times but always found I wou
 
 [MusicalNinjaDad/try_v2](https://github.com/MusicalNinjaDad/try_v2) provides a set of derive macros to make `Try` more accessible. (See below for details)
 
-## (Invalid) criticism: complexity
+## On the common criticism: complexity
 
 After working with the trait in various use cases, taking it apart to try (!) and derive a generic implementation and spending time reading RFCs, unstable books, comments in std source code, github issues, PRs, discord discussions, ... to my mind, the remaining complexity in `Try` is **inherent**. The implementation is **as simple as possible** to provide the power and flexibility required for the more **meaningful use cases**.