From 1eb017581597a8201f6a96826e9ecc0a2b941105 Mon Sep 17 00:00:00 2001
From: ComplexPlane <46565903+ComplexPlane@users.noreply.github.com>
Date: Fri, 14 Jun 2024 11:21:15 -0400
Subject: [PATCH] Update Type Compatibility.md (#3157)

---
 packages/documentation/copy/en/reference/Type Compatibility.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/documentation/copy/en/reference/Type Compatibility.md b/packages/documentation/copy/en/reference/Type Compatibility.md
index 7fd58d9c1e60..b8d4566db5cb 100644
--- a/packages/documentation/copy/en/reference/Type Compatibility.md	
+++ b/packages/documentation/copy/en/reference/Type Compatibility.md	
@@ -409,4 +409,4 @@ Reiterating [The Basics](/docs/handbook/2/basic-types.html):
 - `void` is not assignable to or from anything, with the following exceptions: `any`, `unknown`, `never`, `undefined`, and `null` (if [`strictNullChecks`](/tsconfig#strictNullChecks) is off, see table for details).
 - When [`strictNullChecks`](/tsconfig#strictNullChecks) is off, `null` and `undefined` are similar to `never`: assignable to most types, most types are not assignable to them.
   They are assignable to each other.
-- When [`strictNullChecks`](/tsconfig#strictNullChecks) is on, `null` and `undefined` behave more like `void`: not assignable to or from anything, except for `any`, `unknown`, `never`, and `void` (`undefined` is always assignable to `void`).
+- When [`strictNullChecks`](/tsconfig#strictNullChecks) is on, `null` and `undefined` behave more like `void`: not assignable to or from anything, except for `any`, `unknown`, and `void` (`undefined` is always assignable to `void`).