Mark RFCs that were implemented as such.

docs/config-luaurc.md

@@ -1,5 +1,7 @@
 # Configure analysis via .luaurc
 
+**Status**: Implemented
+
 ## Summary
 
 Introduces a way to configure type checker and linter using JSON-like .luaurc files

docs/function-table-freeze.md

@@ -2,6 +2,8 @@
 
 > Note: this RFC was adapted from an internal proposal that predates RFC process
 
+**Status**: Implemented
+
 ## Summary
 
 Add `table.freeze` which allows to make a table read-only in a shallow way.

docs/generic-functions.md

@@ -1,5 +1,7 @@
 # Generic functions
 
+**Status**: Implemented
+
 ## Summary
 
 Extend the syntax and semantics of functions to support explicit generic functions, which can bind type parameters as well as data parameters.

docs/recursive-type-restriction.md

@@ -1,5 +1,11 @@
 # Recursive type restriction
 
+**Status**: Implemented
+
+## Summary
+
+Restrict generic type aliases to only be able to refer to the exact same instantiation of the generic that's being declared.
+
 ## Motivation
 
 Luau supports recursive type aliases, but with an important restriction:

docs/syntax-if-expression.md

@@ -2,6 +2,8 @@
 
 > Note: this RFC was adapted from an internal proposal that predates RFC process
 
+**Status**: Implemented
+
 ## Summary
 
 Introduce a form of ternary conditional using `if cond then value else alternative` syntax.

docs/unsealed-table-assign-optional-property.md

@@ -1,5 +1,7 @@
 # Unsealed table assignment creates an optional property
 
+## Summary
+
 In Luau, tables have a state, which can, among others, be "unsealed".
 An unsealed table is one that we are still constructing.  Currently
 assigning a table literal to an unsealed table does not introduce new
@@ -53,4 +55,4 @@ and so needs access to an allocator.
 ## Alternatives
 
 Rather than introducing optional properties, we could introduce an indexer. For example we could infer the type of 
-`t` as `{ u: { [string]: number } }`.
+`t` as `{ u: { [string]: number } }`.