From b33c150ecf4692160b4fabed6dcde668d256831a Mon Sep 17 00:00:00 2001
From: SolarScuffle-Bot <93509782+SolarScuffle-Bot@users.noreply.github.com>
Date: Wed, 3 Jan 2024 00:47:26 -1000
Subject: [PATCH] Update type-implicit-table-generics.md

---
 docs/type-implicit-table-generics.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/type-implicit-table-generics.md b/docs/type-implicit-table-generics.md
index 732f3b8..caf45a9 100644
--- a/docs/type-implicit-table-generics.md
+++ b/docs/type-implicit-table-generics.md
@@ -58,8 +58,8 @@ local foo = {} :: <T>{ [F<T>]: G<T> }
 This is not only simpler code, but shorter without all the duplication or extra api that comes with such a structure. Looking at the syntax, it reads very similarly to if it were a function:
 
 ```lua
-<T>{ [F<T>]: G<T> }
-<T>(F<T>) -> G<T>
+type A = <T>{ [F<T>]: G<T> }
+type B = <T>(F<T>) -> G<T>
 ```
 
 We believe that this implementation is a natural step in the direction towards a fuller Luau type-system, as it already has a functional cousin and practical use-cases. Concerns with api coherency, stylistic coherency, learning curve, acceptance, and more are all already answered with implicit function generics.