Fix typos in Articles (pointfreeco#60)

* Fix typos in Articles

* Update Sources/SwiftUINavigation/Documentation.docc/Articles/DestructuringViews.md

Co-authored-by: Stephen Celis <[email protected]>

Author: Jager-yoo

README.md

@@ -96,7 +96,7 @@ it's as simple as adding it to a `dependencies` clause in your `Package.swift`:
 
 ``` swift
 dependencies: [
-  .package(url: "https://github.com/pointfreeco/swiftui-navigation", from: "0.4.1")
+  .package(url: "https://github.com/pointfreeco/swiftui-navigation", from: "0.4.5")
 ]
 ```
 

Sources/SwiftUINavigation/Documentation.docc/Articles/AlertsDialogs.md

@@ -25,7 +25,7 @@ class FeatureModel: ObservableObject {
 }
 ```
 
-Then, when you need to show an alert you can hydate the alert state with a title, message and
+Then, when you need to show an alert you can update the alert state with a title, message and
 buttons:
 
 ```swift
@@ -107,7 +107,7 @@ This works because all of the types for describing an alert are `Equatable`, inc
 Sometimes it is not optimal to model the alert as an optional. In particular, if a feature can
 navigate to multiple, mutually exclusive screens, then an enum is more appropriate.
 
-In such a case 
+In such a case:
 
 
 ```swift

Sources/SwiftUINavigation/Documentation.docc/Articles/DestructuringViews.md

@@ -117,7 +117,7 @@ The "pattern" for the ``IfCaseLet`` is expressed by what is known as a "[case pa
 A case path is like a key path, except it is specifically tuned for abstracting over the
 shape of enums rather than structs. A key path abstractly bundles up the functionality of getting 
 and setting a property on a struct, whereas a case path bundles up the functionality of "extracting"
-a value from an enum and "embedding" a value into an enum. They are an indispensible tool for 
+a value from an enum and "embedding" a value into an enum. They are an indispensable tool for 
 transforming bindings.
 
 ### Switch and CaseLet

Sources/SwiftUINavigation/Documentation.docc/Articles/WhatIsNavigation.md

@@ -214,7 +214,7 @@ In order to isolate a specific case of an enum we must make use of our [CasePath
 library. A case path is like a key path, except it is specifically tuned for abstracting over the
 shape of enums rather than structs. A key path abstractly bundles up the functionality of getting 
 and setting a property on a struct, whereas a case path bundles up the functionality of "extracting"
-a value from an enum and "embedding" a value into an enum. They are an indispensible tool for 
+a value from an enum and "embedding" a value into an enum. They are an indispensable tool for 
 transforming bindings.
 
 Similar APIs are defined for popovers, covers, and more.