Apply suggestions from code review

Co-authored-by: Tina L <49205802+itingliu@users.noreply.github.com>

Author: glessard

Proposals/nnnn-generalize-closure-based-functions-in-Data.md

@@ -6,7 +6,7 @@
 * Status: **Awaiting implementation** or **Awaiting review**
 * Bug: *if applicable* [swiftlang/swift-foundation#1638](https://github.com/swiftlang/swift-foundation/issues/1638)
 
-Implementation: [swiftlang/swift-foundation#1622](https://github.com/swiftlang/swift-foundation/pull/1622)
+* Implementation: [swiftlang/swift-foundation#1622](https://github.com/swiftlang/swift-foundation/pull/1622)
 
 * Review: ([pitch](https://forums.swift.org/...))
 
@@ -16,9 +16,9 @@ We propose to generalize the closure-taking API of `Data` for typed throws and f
 
 ## Motivation
 
-Since [SE-0427], noncopyable types can participate in Swift generics, but `Data` has not been adapted to allow working with noncopyable values. [SE-0437] paved the way by generalizing low-level constructs such as `UnsafeBufferPointer<T>`, and as a result the community of Swift systems programmers now expects that generic functions such as `withUnsafeBytes()` can return noncopyable values.
+Since [SE-0427](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0427-noncopyable-generics.md), noncopyable types can participate in Swift generics, but `Data` has not been adapted to allow working with noncopyable values. [SE-0437](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0437-noncopyable-stdlib-primitives.md) paved the way by generalizing low-level constructs such as `UnsafeBufferPointer<T>`, and as a result the community of Swift systems programmers now expects that generic functions such as `withUnsafeBytes()` can return noncopyable values.
 
-In [SE-0413], we also added the ability for functions to throw typed errors. This ability is important in high-performance contexts such as embedded Swift, and functions such as `withUnsafeBytes()` should support closures with typed errors.
+In [SE-0413](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0413-typed-throws.md), we also added the ability for functions to throw typed errors. This ability is important in high-performance contexts such as embedded Swift, and functions such as `withUnsafeBytes()` should support closures with typed errors.
 
 `Data`'s current closure-based functions such as `withUnsafeBytes()` cannot take advantage of either of these newer features:
 
@@ -42,14 +42,17 @@ The signatures of `Data`'s three closure-based functions will become:
 
 ```swift
 extension Data {
+  @_alwaysEmitIntoClient
   public func withUnsafeBytes<E: Error, ResultType: ~Copyable>(
     _ apply: (UnsafeRawBufferPointer) throws(E) -> ResultType
   ) throws(E) -> ResultType
 
+  @_alwaysEmitIntoClient
   public func withContiguousStorageIfAvailable<E: Error, ResultType: ~Copyable>(
     _ body: (_ buffer: UnsafeBufferPointer<UInt8>) throws(E) -> ResultType
   ) throws(E) -> ResultType?
 
+  @_alwaysEmitIntoClient
   public mutating func withUnsafeMutableBytes<E: Error, ResultType: ~Copyable>(
     _ body: (UnsafeMutableRawBufferPointer) throws(E) -> ResultType
   ) throws(E) -> ResultType