Incorporate feedback

Author: grynspan

Documentation/ABI/TestContent.md

@@ -97,9 +97,9 @@ or returns `false` if it could not generate the relevant content. On successful
 return, the caller is responsible for deinitializing the memory at `outValue`
 when done with it.
 
-`accessor` is optional. If it is `nil`, the test content record is ignored. The
-testing library may, in the future, define record kinds that do not provide an
-accessor function (that is, they represent pure compile-time information only.)
+If `accessor` is `nil`, the test content record is ignored. The testing library
+may, in the future, define record kinds that do not provide an accessor function
+(that is, they represent pure compile-time information only.)
 
 The second argument to this function, `hint`, is an optional input that can be
 passed to help the accessor function determine if its corresponding test content
@@ -140,15 +140,15 @@ content record that needs to be made available before the accessor is called:
 - For test or suite declarations (kind `0x74657374`), this field contains a bit
   mask with the following flags currently defined:
 
-  | Bit | Description |
-  |-:|-|
-  | `1 << 0` | This record contains a suite declaration |
-  | `1 << 1` | This record contains a parameterized test function declaration |
+  | Bit | Value | Description |
+  |-:|-:|-|
+  | `1 << 0` | `1` | This record contains a suite declaration |
+  | `1 << 1` | `2` | This record contains a parameterized test function declaration |
 
-  Other bits are currently always set to `0`, but may be used in the future.
+  Other bits are reserved for future use and must be set to `0`.
 
-- For exit test declarations (kind `0x65786974`), this field is not used and
-  should be set to `0`.
+- For exit test declarations (kind `0x65786974`), this field is reserved for
+  future use and must be set to `0`.
 
 #### The reserved1 and reserved2 fields
 

Documentation/Porting.md

@@ -134,13 +134,12 @@ operation.
 > future release.
 
 _Most_ platforms in use today use the ELF image format and will be able to reuse
-the implementation used by Linux. That implementation calls `dl_iterate_phdr()`
-in the GNU C Library to enumerate available metadata.
+the implementation used by Linux.
 
-If you are porting Swift Testing to Classic, `dl_iterate_phdr()` won't be
-available, so you'll need to write a custom implementation instead. Assuming
-that the Swift compiler emits section information into the resource fork on
-Classic, you would use the [Resource Manager](https://developer.apple.com/library/archive/documentation/mac/pdf/MoreMacintoshToolbox.pdf)
+Classic does not use the ELF image format, so you'll need to write a custom
+implementation of `_testContentSectionBounds()` instead. Assuming that the Swift
+compiler emits section information into the resource fork on Classic, you would
+use the [Resource Manager](https://developer.apple.com/library/archive/documentation/mac/pdf/MoreMacintoshToolbox.pdf)
 to load that information:
 
 ```diff