Skip to content

Commit 949c357

Browse files
invalidnameheckj
andauthored
Apply Joe H's suggestions from code review
Co-authored-by: Joseph Heck <[email protected]>
1 parent cf123b8 commit 949c357

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

stdlib/public/Concurrency/AsyncStream.swift

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -229,7 +229,7 @@ public struct AsyncStream<Element> {
229229
/// instance that it uses to provide elements to the stream and terminate the
230230
/// stream when finished.
231231
///
232-
/// The `AsyncStream.Contuation` received by the `build` closure is appopriate
232+
/// The `AsyncStream.Continuation` received by the `build` closure is appopriate
233233
/// for use in concurrent contexts. It is thread safe to send and finish; all
234234
/// calls are to the continuation are serialized, however calling this from
235235
/// multiple concurrent contexts could result in out-of-order delivery.

stdlib/public/Concurrency/AsyncThrowingStream.swift

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,7 @@ public struct AsyncThrowingStream<Element, Failure: Error> {
258258
/// `AsyncThrowingStream.Continuation` instance that it uses to provide
259259
/// elements to the stream and terminate the stream when finished.
260260
///
261-
/// The `AsyncThrowingStream.Contuation` received by the `build` closure is
261+
/// The `AsyncThrowingStream.Continuation` received by the `build` closure is
262262
/// appopriate for use in concurrent contexts. It is thread safe to send and
263263
/// finish; all calls are to the continuation are serialized, however calling
264264
/// this from multiple concurrent contexts could result in out of order

0 commit comments

Comments
 (0)