Fix tutorial

Author: stephencelis

Sources/ComposableArchitecture/Documentation.docc/Tutorials/MeetTheComposableArchitecture/02-Navigation/02-MultipleDestinations/02-02-02-code-0015.swift

@@ -42,8 +42,8 @@ struct ContactsView: View {
     }
     .alert(
       store: self.store.scope(
-        state: \.$destination.alert,
-        action: \.destination.alert
+        state: \.$alert,
+        action: \.alert
       )
     )
   }

Sources/ComposableArchitecture/Documentation.docc/Tutorials/MeetTheComposableArchitecture/02-Navigation/02-MultipleDestinations/02-02-02-code-0016.swift

@@ -31,18 +31,20 @@ struct ContactsView: View {
       }
     }
     .sheet(
-      store: self.store.scope(state: \.$destination, action: { .destination($0) }),
-      state: \.addContact,
-      action:
+      store: self.store.scope(
+        state: \.$destination.addContact,
+        action: \.destination.addContact
+      )
     ) { addContactStore in
       NavigationStack {
         AddContactView(store: addContactStore)
       }
     }
     .alert(
-      store: self.store.scope(state: \.$destination, action: { .destination($0) }),
-      state: ,
-      action:
+      store: self.store.scope(
+        state: \.$destination.alert,
+        action: \.destination.alert
+      )
     )
   }
 }

Sources/ComposableArchitecture/Documentation.docc/Tutorials/MeetTheComposableArchitecture/02-Navigation/02-MultipleDestinations/02-02-02-code-0017.swift

@@ -241,30 +241,13 @@
 
         @Code(name: "ContactsFeatures.swift", file: 02-02-02-code-0015, previousFile: 02-02-02-code-0015-previous)
       }
-      
-      @Step {
-        The state transformation is responsible for taking a piece of `Destination.State`, which
-        is an enum, and extracting a particular case from it. This can be done with familiar key
-        path syntax because the ``ComposableArchitecture/Reducer()`` macro applies the 
-        `@CasePathable` macro and `@dynamicMemberLookup` to the destination's `State` enum.
-        
-        @Code(name: "ContactsFeatures.swift", file: 02-02-02-code-0016)
-      }
-      
-      @Step {
-        The action transformation is responsible for taking a child action in the 
-        `AddContactFeature` domain and embedding it into the `Destination.Action` enum. This can
-        be done by providing a closure to embed the child action into the destination's action.
-        
-        @Code(name: "ContactsFeatures.swift", file: 02-02-02-code-0017)
-      }
-      
+
       @Step {
         The same can be done for the `alert(store:)` view modifier.
 
-        @Code(name: "ContactsFeatures.swift", file: 02-02-02-code-0018)
+        @Code(name: "ContactsFeatures.swift", file: 02-02-02-code-0016)
       }
-      
+
       That completes the refactor of the reducer and view to use a single piece of optional enum
       state instead using multiple optional values. The application works exactly as it did before,
       but now its domain is more concisely modeled.