From 4c2fec6f409e45e97433f5c2ca9948da47d45dfd Mon Sep 17 00:00:00 2001
From: BradyBromley <51128276+BradyBromley@users.noreply.github.com>
Date: Sun, 13 Oct 2019 13:09:15 -0700
Subject: [PATCH] Changed wording to be more concise in README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 86469953e..feae85e4e 100644
--- a/README.md
+++ b/README.md
@@ -12,8 +12,8 @@ Rewriting Plaid using [Android Architecture Components](https://developer.androi
 
 ### Background
 
-Plaid was written with one big goal: showcase material design in Android in a real application. While Plaid successfully achieved its goal, from an architecture point of view, it lacks all features that would make it a modular, scalable, testable and maintainable app: with UI logic in Android classes, no tests and only one module. 
-Plaid represents a great real world app example: it provides a fairly complex set of functionalities, it has technical debt, it has features that have to be dealt with as APIs are being removed.
+Plaid was written with one big goal: showcase material design in Android in a real application. Plaid achieved its goal, but from an architecture point of view it lacks features that would make it a modular, scalable, testable and maintainable app: with UI logic in Android classes, no tests and only one module. 
+Plaid represents a great real world app example: it provides a fairly complex set of functionalities, it has technical debt, and it has features that have to be dealt with as APIs are being removed.
 All of these problems are encountered by many projects in the Android community and therefore, make Plaid a suitable showcase for all the advantages that architecture components bring. 
 
 #### More information