Updated Available C# and .NET features (markdown)

Available-C#-and-.NET-features.md

@@ -5,15 +5,15 @@ BizHawk-specific notes:
 - In the added "convention" column, I've used required/disallowed/encouraged/discouraged/allowed like [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119)'s MUST / MUST NOT / SHOULD / SHOULD NOT / MAY, respectively. Unsupported is also MUST NOT (because attempting to use the feature will result in an error).
 - Each project's target (Framework vs. Standard) is at the top of its project file, or you can check the [project graph](https://gitlab.com/TASVideos/BizHawk/-/snippets/1886666).
 
-Legend:
-✔️ Available
-⭕ Available with polyfill
-❌ Not available
-? Unknown
+Legend:  
+✔️ Available  
+⭕ Available with polyfill  
+❌ Not available  
+? Unknown  
 Some features are marked ✔️ despite ostensibly needing a polyfill because they are enhancements to existing features and work anywhere the base feature is available—for example, `switch`ing on a `Span<char>` requires no additional polyfill.
 
-🔵 Availability in .NET Framework 4.8 (`net48`)
-🟢 Availability in .NET Standard 2.0 (`netstandard2.0`)
+🔵 Availability in .NET Framework 4.8 (`net48`)  
+🟢 Availability in .NET Standard 2.0 (`netstandard2.0`)  
 I have not considered Framework 4.7.2 and below as there is little reason not to upgrade to Framework 4.8.
 I have not considered Framework 4.8.1 because it matches Framework 4.8 in terms of language features and is generally not useful.
 I use Standard 2.0 and not Standard 2.1 as the latter is not subsumed by Framework 4.8, rendering it useless.