Restore original meaning

One change from #1638 changed the original meaning, so let's revert that.

Author: stephencelis

Sources/ComposableArchitecture/ReducerProtocol.swift

@@ -115,7 +115,7 @@
   ///
   /// At most one of these requirements should be implemented. If a conformance implements both
   /// requirements, only ``reduce(into:action:)-8yinq`` will be called by the ``Store``. If your
-  /// reducer assembles a body from other reducers _and_ has additional business logic, it needs to
+  /// reducer assembles a body from other reducers _and_ has additional business logic it needs to
   /// layer onto the feature, introduce this logic into the body instead, either with ``Reduce``:
   ///
   /// ```swift
@@ -205,7 +205,7 @@
     /// > Important: if your reducer implements the ``reduce(into:action:)-8yinq`` method, it will
     /// > take precedence over this property, and only ``reduce(into:action:)-8yinq`` will be called
     /// > by the ``Store``. If your reducer assembles a body from other reducers and has additional
-    /// > business logic, it needs to layer into the system, introduce this logic into the body
+    /// > business logic it needs to layer into the system, introduce this logic into the body
     /// > instead, either with ``Reduce``, or with a separate, dedicated conformance.
     @ReducerBuilder<State, Action>
     var body: Body { get }
@@ -227,7 +227,7 @@
   ///
   /// At most one of these requirements should be implemented. If a conformance implements both
   /// requirements, only ``reduce(into:action:)-8yinq`` will be called by the ``Store``. If your
-  /// reducer assembles a body from other reducers _and_ has additional business logic, it needs to
+  /// reducer assembles a body from other reducers _and_ has additional business logic it needs to
   /// layer onto the feature, introduce this logic into the body instead, either with ``Reduce``:
   ///
   /// ```swift
@@ -315,7 +315,7 @@
     /// > Important: if your reducer implements the ``reduce(into:action:)-8yinq`` method, it will
     /// > take precedence over this property, and only ``reduce(into:action:)-8yinq`` will be called
     /// > by the ``Store``. If your reducer assembles a body from other reducers and has additional
-    /// > business logic, it needs to layer into the system, introduce this logic into the body
+    /// > business logic it needs to layer into the system, introduce this logic into the body
     /// > instead, either with ``Reduce``, or with a separate, dedicated conformance.
     @ReducerBuilder<State, Action>
     var body: Body { get }