Fixes for the 'Basic Usage' to allow project to build and run (#1507)

* fixes for building basic usage section without error

* and code with too many closing braces

* adjust description

* burned by xcode expanding the code

* burned by xcode case indent option

* fixed added spaces

* Apply suggestions from code review

Co-authored-by: Brandon Williams <[email protected]>

Co-authored-by: Rick Naro <[email protected]>
Co-authored-by: Stephen Celis <[email protected]>
Co-authored-by: Brandon Williams <[email protected]>
(cherry picked from commit e726a132929be7a67050e2587b9d2b1532898ba8)

Author: 4 people

README.md

@@ -99,6 +99,8 @@ As a basic example, consider a UI that shows a number along with "+" and "−" b
 To implement this feature we create a new type that will house the domain and behavior of the feature by conforming to `ReducerProtocol`:
 
 ```swift
+import ComposableArchitecture
+
 struct Feature: ReducerProtocol {
 }
 ```
@@ -151,13 +153,13 @@ struct Feature: ReducerProtocol {
         return .none
 
       case .numberFactButtonTapped:
-        return .task { [count = state.count] in 
+        return .task { [count = state.count] in
           await .numberFactResponse(
-            TaskResult { 
+            TaskResult {
               String(
                 decoding: try await URLSession.shared
-                  .data(from: URL(string: "http://numbersapi.com/\(number)/trivia")!).0,
-                using: UTF8.self
+                  .data(from: URL(string: "http://numbersapi.com/\(count)/trivia")!).0,
+                as: UTF8.self
               )
             }
           )
@@ -170,7 +172,6 @@ struct Feature: ReducerProtocol {
       case .numberFactResponse(.failure):
         state.numberFactAlert = "Could not load a number fact :("
         return .none
-      } 
     }
   }
 }
@@ -274,15 +275,19 @@ It is also straightforward to have a UIKit controller driven off of this store.
 Once we are ready to display this view, for example in the app's entry point, we can construct a store. This can be done by specifying the initial state to start the application in, as well as the reducer that will power the application:
 
 ```swift
+import ComposableArchitecture
+
 @main
 struct MyApp: App {
   var body: some Scene {
-    FeatureView(
-      store: Store(
-        initialState: Feature.State(),
-        reducer: Feature()
+    WindowGroup {
+      FeatureView(
+        store: Store(
+          initialState: Feature.State(),
+          reducer: Feature()
+        )
       )
-    )
+    }
   }
 }
 ```