diff --git a/Sources/FuturedArchitecture/Architecture/ComponentModel.swift b/Sources/FuturedArchitecture/Architecture/ComponentModel.swift
index c10426f..97e0a55 100644
--- a/Sources/FuturedArchitecture/Architecture/ComponentModel.swift
+++ b/Sources/FuturedArchitecture/Architecture/ComponentModel.swift
@@ -1,8 +1,8 @@
 import Foundation
 
-/// `ComponentModel` is an analogy to `ViewModel`. Each *compoenent model* should have
+/// `ComponentModel` is an analogy to `ViewModel`. Each *component model* should have
 /// it's own protocol which uses the `ComponentModel` protocol as it's requirement. This allows us
-/// to create a Mock implementations of compoenent models and allow for simpler and more scalable
+/// to create a Mock implementations of component models and allow for simpler and more scalable
 /// SwiftUI Previews.
 ///
 /// As is eluded to by `ComponentModel`, each component model has two main competencies:
diff --git a/Sources/FuturedArchitecture/Architecture/DataCache.swift b/Sources/FuturedArchitecture/Architecture/DataCache.swift
index ee8459f..2aab19e 100644
--- a/Sources/FuturedArchitecture/Architecture/DataCache.swift
+++ b/Sources/FuturedArchitecture/Architecture/DataCache.swift
@@ -6,7 +6,7 @@ import Foundation
 /// An Application should contain one shared application-wide cache, but each
 /// coordinator may also create a private data cache.
 ///
-/// The data from data chache should be taken as a subscription and modified
+/// The data from data cache should be taken as a subscription and modified
 /// only via provided `update` methods. As a general rule, value types should
 /// be used as a `Model`.
 ///