Mark singleton types and unsealed table literals RFCs as implemented

rfcs/STATUS.md

@@ -17,17 +17,10 @@ This document tracks unimplemented RFCs.
 
 ## Sealed/unsealed typing changes
 
-[RFC: Unsealed table literals](https://github.com/Roblox/luau/blob/master/rfcs/unsealed-table-literals.md) |
 [RFC: Only strip optional properties from unsealed tables during subtyping](https://github.com/Roblox/luau/blob/master/rfcs/unsealed-table-subtyping-strips-optional-properties.md)
 
 **Status**: Implemented but not fully rolled out yet.
 
-## Singleton types
-
-[RFC: Singleton types](https://github.com/Roblox/luau/blob/master/rfcs/syntax-singleton-types.md)
-
-**Status**: Implemented but not fully rolled out yet.
-
 ## Safe navigation operator
 
 [RFC: Safe navigation postfix operator (?)](https://github.com/Roblox/luau/blob/master/rfcs/syntax-safe-navigation-operator.md)

rfcs/syntax-singleton-types.md

@@ -2,6 +2,8 @@
 
 > Note: this RFC was adapted from an internal proposal that predates RFC process
 
+**Status**: Implemented
+
 ## Summary
 
 Introduce a new kind of type variable, called singleton types. They are just like normal types but has the capability to represent a constant runtime value as a type.

rfcs/unsealed-table-literals.md

@@ -1,5 +1,7 @@
 # Unsealed table literals
 
+**Status**: Implemented
+
 ## Summary
 
 Currently the only way to create an unsealed table is as an empty table literal `{}`.
@@ -73,4 +75,4 @@ We could introduce a new table state for unsealed-but-precise
 tables. The trade-off is that that would be more precise, at the cost
 of adding user-visible complexity to the type system.
 
-We could continue to treat array-like tables as sealed.
+We could continue to treat array-like tables as sealed.