docs: rename TL;DR heading, remove LinkedIn reference

MPCoreDeveloper · MPCoreDeveloper · commit 961ba3b5cb3b · 2026-04-20T05:49:21.000+02:00
diff --git a/docs/NULLABLE_VS_OPTIONAL_REBUTTAL.md b/docs/NULLABLE_VS_OPTIONAL_REBUTTAL.md
@@ -42,7 +42,7 @@ The argument isn't about *more kinds of absence*. It's about **where** the absen
 
 The statement *"runtime data semantics cannot always be fully proven at compile time"* means exactly this: **the compiler can annotate intent, but it cannot enforce contracts on data it has never seen** (SQL results, JSON payloads, reflection-populated DTOs). `Option<T>` closes that gap by making the proof travel *with the value*.
 
-## TL;DR for LinkedIn
+## TL;DR
 
 > **"Aren't nullable types just optional types?"**
 >

Original file line number	Diff line number	Diff line change
`@@ -42,7 +42,7 @@ The argument isn't about more kinds of absence. It's about where the absen`
`42`	`42`
`43`	`43`	The statement "runtime data semantics cannot always be fully proven at compile time" means exactly this: the compiler can annotate intent, but it cannot enforce contracts on data it has never seen (SQL results, JSON payloads, reflection-populated DTOs). `Option<T>` closes that gap by making the proof travel with the value.
`44`	`44`
`45`		`-## TL;DR for LinkedIn`
	`45`	`+## TL;DR`
`46`	`46`
`47`	`47`	`> "Aren't nullable types just optional types?"`
`48`	`48`	`>`