From 18ad649648a1d6685d6e10580ab4a4e4df77ee14 Mon Sep 17 00:00:00 2001
From: "Alex D. Torres" <59746256+alexDtorres@users.noreply.github.com>
Date: Fri, 24 Dec 2021 11:54:51 -0600
Subject: [PATCH] Fix typo in 'Documentation' section of README (#473)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 82bf8272f..5da0ad24d 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ MVC, MVP, MVI, MVVM and VIPER are architecture patterns. RIBs is a framework. Wh
 
 There are some other novel things about RIBs. However, these could also be implemented with other MV*/VIPER frameworks. These are:
 - **Cross-platform approach**, allowing iOS and Android architecture to stay in sync.
-- **Tooling to for easier adoption** on larger apps or teams. Tooling we are open sourcing includes IDE plugins for code generation and static code analysis.
+- **Tooling for easier adoption** on larger apps or teams. Tooling we are open sourcing includes IDE plugins for code generation and static code analysis.
 - **Strong opinions about how state should be communicated**, using DI and Rx. Each RIB defines its dependencies and what dependencies it needs from its parent. Parent components that fulfill a child’s parent dependencies are provided to child Builders as a constructor dependency to allow for hierarchical DI scoping. This means that information is communicated via these dependencies up and down the tree.
 
 ## Usage