Small docs fixes.

Author: mbrandonw

Sources/ComposableArchitecture/Documentation.docc/Articles/Testing.md

@@ -74,7 +74,7 @@ class CounterTests: XCTestCase {
 > Tip: Test cases that use ``TestStore`` should be annotated as `@MainActor` and test methods should 
 be marked as `async` since most assertion helpers on ``TestStore`` can suspend.
 
-Test stores have a ``TestStore/send(_:_:file:line:)-3pf4p`` method, but it behaves differently from
+Test stores have a ``TestStore/send(_:_:file:line:)-6s1gq`` method, but it behaves differently from
 stores and view stores. You provide an action to send into the system, but then you must also
 provide a trailing closure to describe how the state of the feature changed after sending the
 action:
@@ -95,7 +95,7 @@ await store.send(.incrementButtonTapped) {
 }
 ```
 
-> The ``TestStore/send(_:_:file:line:)-3pf4p`` method is `async` for technical reasons that we do
+> The ``TestStore/send(_:_:file:line:)-6s1gq`` method is `async` for technical reasons that we do
 not have to worry about right now.
 
 If your mutation is incorrect, meaning you perform a mutation that is different from what happened
@@ -146,7 +146,7 @@ await store.send(.decrementButtonTapped) {
 > by one, but we haven't proven we know the precise value of `count` at each step of the way.
 >
 > In general, the less logic you have in the trailing closure of
-> ``TestStore/send(_:_:file:line:)-3pf4p``, the stronger your assertion will be. It is best to use
+> ``TestStore/send(_:_:file:line:)-6s1gq``, the stronger your assertion will be. It is best to use
 > simple, hard coded data for the mutation.
 
 Test stores do expose a ``TestStore/state`` property, which can be useful for performing assertions
@@ -160,7 +160,7 @@ store.send(.incrementButtonTapped) {
 XCTAssertTrue(store.state.isPrime)
 ```
 
-However, when inside the trailing closure of ``TestStore/send(_:_:file:line:)-3pf4p``, the 
+However, when inside the trailing closure of ``TestStore/send(_:_:file:line:)-6s1gq``, the 
 ``TestStore/state`` property is equal to the state _before_ sending the action, not after. That 
 prevents you from being able to use an escape hatch to get around needing to actually describe the 
 state mutation, like so:

Sources/ComposableArchitecture/Documentation.docc/Extensions/TestStore.md

@@ -13,14 +13,14 @@
 
 ### Testing a reducer
 
-- ``send(_:_:file:line:)-3pf4p``
+- ``send(_:_:file:line:)-6s1gq``
 - ``receive(_:timeout:_:file:line:)``
 - ``finish(timeout:file:line:)``
 - ``TestStoreTask``
 
 ### Accessing state
 
-While the most common way of interacting with a test store's state is via its ``send(_:_:file:line:)-3pf4p`` and ``receive(_:timeout:_:file:line:)`` methods, you may also access it directly throughout a test.
+While the most common way of interacting with a test store's state is via its ``send(_:_:file:line:)-6s1gq`` and ``receive(_:timeout:_:file:line:)`` methods, you may also access it directly throughout a test.
 
 - ``state``
 

Sources/ComposableArchitecture/TestStore.swift

@@ -220,7 +220,7 @@ public final class TestStore<State, Action, ScopedState, ScopedAction, Environme
 
   /// The current state.
   ///
-  /// When read from a trailing closure assertion in ``send(_:_:file:line:)-3pf4p`` or
+  /// When read from a trailing closure assertion in ``send(_:_:file:line:)-6s1gq`` or
   /// ``receive(_:timeout:_:file:line:)``, it will equal the `inout` state passed to the closure.
   public var state: State {
     self.reducer.state
@@ -229,8 +229,7 @@ public final class TestStore<State, Action, ScopedState, ScopedAction, Environme
   /// The timeout to await for in-flight effects.
   ///
   /// This is the default timeout used in all methods that take an optional timeout, such as
-  /// ``send(_:_:file:line:)-3pf4p``, ``receive(_:timeout:_:file:line:)`` and
-  /// ``finish(timeout:file:line:)``.
+  /// ``receive(_:timeout:_:file:line:)`` and ``finish(timeout:file:line:)``.
   public var timeout: UInt64
 
   private var _environment: Box<Environment>
@@ -931,7 +930,7 @@ extension TestStore {
   }
 }
 
-/// The type returned from ``TestStore/send(_:_:file:line:)-3pf4p`` that represents the lifecycle
+/// The type returned from ``TestStore/send(_:_:file:line:)-6s1gq`` that represents the lifecycle
 /// of the effect started from sending an action.
 ///
 /// You can use this value in tests to cancel the effect started from sending an action: