Merge branch 'main' into em_dash_102987894

Author: amartini51

Sources/TSPL/TSPL.docc/LanguageGuide/AutomaticReferenceCounting.md

@@ -601,7 +601,9 @@ and ARC never sets an unowned reference's value to `nil`.
 -->
 
 > Important: Use an unowned reference only when you are sure that
-> the reference *always* refers to an instance that hasn't been deallocated.If you try to access the value of an unowned reference
+> the reference *always* refers to an instance that hasn't been deallocated.
+>
+> If you try to access the value of an unowned reference
 > after that instance has been deallocated,
 > you'll get a runtime error.
 
@@ -768,7 +770,9 @@ after the `john` variable is set to `nil`.
 > you need to disable runtime safety checks ---
 > for example, for performance reasons.
 > As with all unsafe operations,
-> you take on the responsibility for checking that code for safety.You indicate an unsafe unowned reference by writing `unowned(unsafe)`.
+> you take on the responsibility for checking that code for safety.
+>
+> You indicate an unsafe unowned reference by writing `unowned(unsafe)`.
 > If you try to access an unsafe unowned reference
 > after the instance that it refers to is deallocated,
 > your program will try to access the memory location
@@ -909,7 +913,9 @@ that other courses might have.
 > Note: The underlying type of an optional value is `Optional`,
 > which is an enumeration in the Swift standard library.
 > However, optionals are an exception to the rule that
-> value types can't be marked with `unowned`.The optional that wraps the class
+> value types can't be marked with `unowned`.
+>
+> The optional that wraps the class
 > doesn't use reference counting,
 > so you don't need to maintain a strong reference to the optional.
 

Sources/TSPL/TSPL.docc/LanguageGuide/Closures.md

@@ -731,7 +731,9 @@ the next time the `incrementer` function is called.
 > Note: As an optimization,
 > Swift may instead capture and store a *copy* of a value
 > if that value isn't mutated by a closure,
-> and if the value isn't mutated after the closure is created.Swift also handles all memory management involved in disposing of
+> and if the value isn't mutated after the closure is created.
+>
+> Swift also handles all memory management involved in disposing of
 > variables when they're no longer needed.
 
 Here's an example of `makeIncrementer` in action:

Sources/TSPL/TSPL.docc/LanguageGuide/CollectionTypes.md

@@ -54,7 +54,9 @@ and its size and contents can't be changed.
 An *array* stores values of the same type in an ordered list.
 The same value can appear in an array multiple times at different positions.
 
-> Note: Swift's `Array` type is bridged to Foundation's `NSArray` class.For more information about using `Array` with Foundation and Cocoa,
+> Note: Swift's `Array` type is bridged to Foundation's `NSArray` class.
+>
+> For more information about using `Array` with Foundation and Cocoa,
 > see [Bridging Between Array and NSArray](https://developer.apple.com/documentation/swift/array#2846730).
 
 ### Array Type Shorthand Syntax
@@ -580,7 +582,9 @@ in a collection with no defined ordering.
 You can use a set instead of an array when the order of items isn't important,
 or when you need to ensure that an item only appears once.
 
-> Note: Swift's `Set` type is bridged to Foundation's `NSSet` class.For more information about using `Set` with Foundation and Cocoa,
+> Note: Swift's `Set` type is bridged to Foundation's `NSSet` class.
+>
+> For more information about using `Set` with Foundation and Cocoa,
 > see [Bridging Between Set and NSSet](https://developer.apple.com/documentation/swift/set#2845530).
 
 <!--
@@ -605,7 +609,7 @@ are also hashable by default.
 > by making them conform to the `Hashable` protocol
 > from the Swift standard library.
 > For information about implementing the required `hash(into:)` method,
-> see [Hashable](https://developer.apple.com/documentation/swift/hashable).
+> see [`Hashable`](https://developer.apple.com/documentation/swift/hashable).
 > For information about conforming to protocols, see <doc:Protocols>.
 
 ### Set Type Syntax
@@ -1027,7 +1031,9 @@ You use a dictionary when you need to look up values based on their identifier,
 in much the same way that a real-world dictionary is used to look up
 the definition for a particular word.
 
-> Note: Swift's `Dictionary` type is bridged to Foundation's `NSDictionary` class.For more information about using `Dictionary` with Foundation and Cocoa,
+> Note: Swift's `Dictionary` type is bridged to Foundation's `NSDictionary` class.
+>
+> For more information about using `Dictionary` with Foundation and Cocoa,
 > see [Bridging Between Dictionary and NSDictionary](https://developer.apple.com/documentation/swift/dictionary#2846239).
 
 ### Dictionary Type Shorthand Syntax

Sources/TSPL/TSPL.docc/LanguageGuide/Concurrency.md

@@ -297,7 +297,7 @@ you'll get compile-time error instead of introducing a bug.
   and give you better guarantees and clearer errors
 -->
 
-> Note: The [Task.sleep(until:tolerance:clock:)](https://developer.apple.com/documentation/swift/task/sleep(until:tolerance:clock:)) method
+> Note: The [`Task.sleep(until:tolerance:clock:)`](https://developer.apple.com/documentation/swift/task/sleep(until:tolerance:clock:)) method
 > is useful when writing simple code
 > to learn how concurrency works.
 > This method does nothing,
@@ -388,10 +388,10 @@ when it's waiting for the next element to be available.
 -->
 
 In the same way that you can use your own types in a `for`-`in` loop
-by adding conformance to the [Sequence](https://developer.apple.com/documentation/swift/sequence) protocol,
+by adding conformance to the [`Sequence`](https://developer.apple.com/documentation/swift/sequence) protocol,
 you can use your own types in a `for`-`await`-`in` loop
 by adding conformance to the
-[AsyncSequence](https://developer.apple.com/documentation/swift/asyncsequence) protocol.
+[`AsyncSequence`](https://developer.apple.com/documentation/swift/asyncsequence) protocol.
 
 <!--
   TODO what happened to ``Series`` which was supposed to be a currency type?
@@ -554,7 +554,7 @@ Because of the explicit relationship between tasks and task groups,
 this approach is called *structured concurrency*.
 Although you take on some of the responsibility for correctness,
 the explicit parent-child relationships between tasks
-lets Swift handle some behaviors like propagating cancellation for you,
+let Swift handle some behaviors like propagating cancellation for you,
 and lets Swift detect some errors at compile time.
 
 ```
@@ -571,7 +571,7 @@ await withTaskGroup(of: Data.self) { taskGroup in
 -->
 
 For more information about task groups,
-see [TaskGroup](https://developer.apple.com/documentation/swift/taskgroup).
+see [`TaskGroup`](https://developer.apple.com/documentation/swift/taskgroup).
 
 <!--
   OUTLINE
@@ -699,10 +699,10 @@ You have complete flexibility to manage unstructured tasks
 in whatever way your program needs,
 but you're also completely responsible for their correctness.
 To create an unstructured task that runs on the current actor,
-call the [Task.init(priority:operation:)](https://developer.apple.com/documentation/swift/task/3856790-init) initializer.
+call the [`Task.init(priority:operation:)`](https://developer.apple.com/documentation/swift/task/3856790-init) initializer.
 To create an unstructured task that's not part of the current actor,
 known more specifically as a *detached task*,
-call the [Task.detached(priority:operation:)](https://developer.apple.com/documentation/swift/task/3856786-detached) class method.
+call the [`Task.detached(priority:operation:)`](https://developer.apple.com/documentation/swift/task/3856786-detached) class method.
 Both of these operations return a task that you can interact with ---
 for example, to wait for its result or to cancel it.
 
@@ -715,7 +715,7 @@ let result = await handle.value
 ```
 
 For more information about managing detached tasks,
-see [Task](https://developer.apple.com/documentation/swift/task).
+see [`Task`](https://developer.apple.com/documentation/swift/task).
 
 <!--
   TODO Add some conceptual guidance about
@@ -738,16 +738,16 @@ that usually means one of the following:
 - Returning the partially completed work
 
 To check for cancellation,
-either call [Task.checkCancellation()](https://developer.apple.com/documentation/swift/task/3814826-checkcancellation),
+either call [`Task.checkCancellation()`](https://developer.apple.com/documentation/swift/task/3814826-checkcancellation),
 which throws `CancellationError` if the task has been canceled,
-or check the value of [Task.isCancelled](https://developer.apple.com/documentation/swift/task/3814832-iscancelled)
+or check the value of [`Task.isCancelled`](https://developer.apple.com/documentation/swift/task/3814832-iscancelled)
 and handle the cancellation in your own code.
 For example,
 a task that's downloading photos from a gallery
 might need to delete partial downloads and close network connections.
 
 To propagate cancellation manually,
-call [Task.cancel()](https://developer.apple.com/documentation/swift/task/3851218-cancel).
+call [`Task.cancel()`](https://developer.apple.com/documentation/swift/task/3851218-cancel).
 
 <!--
   OUTLINE
@@ -1040,7 +1040,7 @@ In general, there are three ways for a type to be sendable:
 -->
 
 For a detailed list of the semantic requirements,
-see the [Sendable](https://developer.apple.com/documentation/swift/sendable) protocol reference.
+see the [`Sendable`](https://developer.apple.com/documentation/swift/sendable) protocol reference.
 
 Some types are always sendable,
 like structures that have only sendable properties

Sources/TSPL/TSPL.docc/LanguageGuide/ControlFlow.md

@@ -274,7 +274,7 @@ The examples above use a `for`-`in` loop to iterate
 ranges, arrays, dictionaries, and strings.
 However, you can use this syntax to iterate *any* collection,
 including your own classes and collection types,
-as long as those types conform to the [Sequence](https://developer.apple.com/documentation/swift/sequence) protocol.
+as long as those types conform to the [`Sequence`](https://developer.apple.com/documentation/swift/sequence) protocol.
 
 <!--
   TODO: for (index, object) in enumerate(collection)
@@ -1732,9 +1732,11 @@ and to determine whether the move is allowed:
 
 > Note: If the `break` statement above didn't use the `gameLoop` label,
 > it would break out of the `switch` statement, not the `while` statement.
-> Using the `gameLoop` label makes it clear which control statement should be terminated.It isn't strictly necessary to use the `gameLoop` label
+> Using the `gameLoop` label makes it clear which control statement should be terminated.
+>
+> It isn't strictly necessary to use the `gameLoop` label
 > when calling `continue gameLoop` to jump to the next iteration of the loop.
-> there's only one loop in the game,
+> There's only one loop in the game,
 > and therefore no ambiguity as to which loop the `continue` statement will affect.
 > However, there's no harm in using the `gameLoop` label with the `continue` statement.
 > Doing so is consistent with the label's use alongside the `break` statement

Sources/TSPL/TSPL.docc/LanguageGuide/Enumerations.md

@@ -307,7 +307,7 @@ for beverage in Beverage.allCases {
 
 The syntax used in the examples above
 marks the enumeration as conforming to the
-[CaseIterable](https://developer.apple.com/documentation/swift/caseiterable) protocol.
+[`CaseIterable`](https://developer.apple.com/documentation/swift/caseiterable) protocol.
 For information about protocols, see <doc:Protocols>.
 
 ## Associated Values

Sources/TSPL/TSPL.docc/LanguageGuide/Inheritance.md

@@ -435,7 +435,9 @@ For more information on property observers, see <doc:Properties#Property-Observe
 > inherited constant stored properties or inherited read-only computed properties.
 > The value of these properties can't be set,
 > and so it isn't appropriate to provide a `willSet` or `didSet` implementation
-> as part of an override.Note also that you can't provide both
+> as part of an override.
+>
+> Note also that you can't provide both
 > an overriding setter and an overriding property observer for the same property.
 > If you want to observe changes to a property's value,
 > and you are already providing a custom setter for that property,

Sources/TSPL/TSPL.docc/LanguageGuide/MemorySafety.md

@@ -112,7 +112,9 @@ you have to determine what it was intended to do.
 > However,
 > the conflicting access discussed here can happen
 > on a single thread and
-> *doesn't* involve concurrent or multithreaded code.If you have conflicting access to memory
+> *doesn't* involve concurrent or multithreaded code.
+>
+> If you have conflicting access to memory
 > from within a single thread,
 > Swift guarantees that you'll get an error
 > at either compile time or runtime.

Sources/TSPL/TSPL.docc/LanguageGuide/Properties.md

@@ -737,7 +737,9 @@ the new value that you assign replaces the one that was just set.
 > are called when a property is set in a subclass initializer,
 > after the superclass initializer has been called.
 > They aren't called while a class is setting its own properties,
-> before the superclass initializer has been called.For more information about initializer delegation,
+> before the superclass initializer has been called.
+>
+> For more information about initializer delegation,
 > see <doc:Initialization#Initializer-Delegation-for-Value-Types>
 > and <doc:Initialization#Initializer-Delegation-for-Class-Types>.
 
@@ -1676,7 +1678,9 @@ and they're written in the same way as computed properties.
 > Note: Global constants and variables are always computed lazily,
 > in a similar manner to <doc:Properties#Lazy-Stored-Properties>.
 > Unlike lazy stored properties,
-> global constants and variables don't need to be marked with the `lazy` modifier.Local constants and variables are never computed lazily.
+> global constants and variables don't need to be marked with the `lazy` modifier.
+>
+> Local constants and variables are never computed lazily.
 
 You can apply a property wrapper to a local stored variable,
 but not to a global variable or a computed variable.
@@ -1763,7 +1767,9 @@ in the same way as computed instance properties.
 > Note: Unlike stored instance properties,
 > you must always give stored type properties a default value.
 > This is because the type itself doesn't have an initializer
-> that can assign a value to a stored type property at initialization time.Stored type properties are lazily initialized on their first access.
+> that can assign a value to a stored type property at initialization time.
+>
+> Stored type properties are lazily initialized on their first access.
 > They're guaranteed to be initialized only once,
 > even when accessed by multiple threads simultaneously,
 > and they don't need to be marked with the `lazy` modifier.

Sources/TSPL/TSPL.docc/LanguageGuide/StringsAndCharacters.md

@@ -29,7 +29,9 @@ and provides support for accessing those characters in various Unicode represent
 > Note: Swift's `String` type is bridged with Foundation's `NSString` class.
 > Foundation also extends `String` to expose methods defined by `NSString`.
 > This means, if you import Foundation,
-> you can access those `NSString` methods on `String` without casting.For more information about using `String` with Foundation and Cocoa,
+> you can access those `NSString` methods on `String` without casting.
+>
+> For more information about using `String` with Foundation and Cocoa,
 > see [Bridging Between String and NSString](https://developer.apple.com/documentation/swift/string#2919514).
 
 ## String Literals
@@ -958,7 +960,9 @@ print("the number of characters in \(word) is \(word.count)")
 > If you are working with particularly long string values,
 > be aware that the `count` property
 > must iterate over the Unicode scalars in the entire string
-> in order to determine the characters for that string.The count of the characters returned by the `count` property
+> in order to determine the characters for that string.
+>
+> The count of the characters returned by the `count` property
 > isn't always the same as the `length` property of
 > an `NSString` that contains the same characters.
 > The length of an `NSString` is based on
@@ -1173,7 +1177,7 @@ welcome.removeSubrange(range)
 When you get a substring from a string ---
 for example, using a subscript or a method like `prefix(_:)` ---
 the result is an instance
-of [Substring](https://developer.apple.com/documentation/swift/substring),
+of [`Substring`](https://developer.apple.com/documentation/swift/substring),
 not another string.
 Substrings in Swift have most of the same methods as strings,
 which means you can work with substrings
@@ -1249,7 +1253,7 @@ The figure below shows these relationships:
 ![](stringSubstring)
 
 > Note: Both `String` and `Substring` conform to the
-> [StringProtocol](https://developer.apple.com/documentation/swift/stringprotocol) protocol,
+> [`StringProtocol`](https://developer.apple.com/documentation/swift/stringprotocol) protocol,
 > which means it's often convenient for string-manipulation functions
 > to accept a `StringProtocol` value.
 > You can call such functions with either a `String` or `Substring` value.