WASI doesn't really use ELF

Author: grynspan

Documentation/ABI/TestContent.md

@@ -27,16 +27,13 @@ section in built test products:
 |-|:-:|-|
 | macOS, iOS, watchOS, tvOS, visionOS | Mach-O | `__DATA_CONST,__swift5_tests` |
 | Linux, FreeBSD, Android | ELF | `swift5_tests` |
-| WASI | Statically Linked | `swift5_tests`[^1] |
-| Windows | PE/COFF | `.sw5test`[^2] |
-
-[^1]: SwiftWasm effectively uses the ELF format for its images, however it is
-      currently always statically linked and runtime discovery is performed
-      using a different mechanism than what we use on other ELF-based platforms.
-[^2]: On Windows, the Swift compiler [emits](https://github.com/swiftlang/swift/blob/main/stdlib/public/runtime/SwiftRT-COFF.cpp)
-      leading and trailing padding into this section, both zeroed and of size
-      `MemoryLayout<UInt>.stride`. Code that walks this section can safely skip
-      over this padding.
+| WASI | WebAssembly | `swift5_tests` |
+| Windows | PE/COFF | `.sw5test`[^windowsPadding] |
+
+[^windowsPadding]: On Windows, the Swift compiler [emits](https://github.com/swiftlang/swift/blob/main/stdlib/public/runtime/SwiftRT-COFF.cpp)
+  leading and trailing padding into this section, both zeroed and of size
+  `MemoryLayout<UInt>.stride`. Code that walks this section must skip over this
+  padding.
 
 ### Record headers