wip

Author: mbrandonw

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

@@ -8,7 +8,7 @@ any reducer.
 Dependencies in an application are the types and functions that need to interact with outside 
 systems that you do not control. Classic examples of this are API clients that make network requests
 to servers, but also seemingly innocuous things such as `UUID` and `Date` initializers, and even
-schedulers and clocks, can be thought of as dependencies.
+clocks, can be thought of as dependencies.
 
 By controlling the dependencies our features need to do their job we gain the ability to completely
 alter the execution context a feature runs in. This means in tests and Xcode previews you can 

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

@@ -273,8 +273,8 @@ going to be received, but after waiting around for a small amount of time no act
 This is because our timer is on a 1 second interval, and by default
 ``TestStore/receive(_:timeout:_:file:line:)`` only waits for a fraction of a second. This is
 because typically you should not be performing real time-based asynchrony in effects, and instead
-using a controlled entity, such as a scheduler or clock, that can be sped up in tests. We will
-demonstrate this in a moment, so for now let's increase the timeout:
+using a controlled entity, such as a clock, that can be sped up in tests. We will demonstrate this 
+in a moment, so for now let's increase the timeout:
 
 ```swift
 await store.receive(.timerTick, timeout: .seconds(2)) {
@@ -403,7 +403,6 @@ dependencies, read the <doc:DependencyManagement> article.
 [Testing-effects]: #Testing-effects
 [Designing-dependencies]: #Designing-dependencies
 [Unimplemented-dependencies]: #Unimplemented-dependencies
-[gh-combine-schedulers]: http://github.com/pointfreeco/combine-schedulers
 [gh-xctest-dynamic-overlay]: http://github.com/pointfreeco/xctest-dynamic-overlay
 [tca-examples]: https://github.com/pointfreeco/swift-composable-architecture/tree/main/Examples
 [gh-swift-clocks]: http://github.com/pointfreeco/swift-clocks

Sources/ComposableArchitecture/ReducerProtocol.swift

@@ -97,8 +97,8 @@
   ///
   /// > Note: This sample emulates a timer by performing an infinite loop with a `Task.sleep`
   /// inside. This is simple to do, but is also inaccurate since small imprecisions can accumulate.
-  /// It would be better to inject a Combine scheduler into the feature and use its async-friendly
-  /// `timer` method. Read the <doc:DependencyManagement> and <doc:Testing> articles for more
+  /// It would be better to inject a clock into the feature so that you could use its `timer`
+  /// method. Read the <doc:DependencyManagement> and <doc:Testing> articles for more
   /// information.
   ///
   /// That is the basics of implementing a feature as a conformance to ``ReducerProtocol``. There are