diff --git a/Projects/3-Advanced/Slack-Archiver.md b/Projects/3-Advanced/Slack-Archiver.md
index 53c70205..fe23dc60 100644
--- a/Projects/3-Advanced/Slack-Archiver.md
+++ b/Projects/3-Advanced/Slack-Archiver.md
@@ -2,26 +2,14 @@
 
 **Tier:** 3-Advanced
 
-Slack is a tool many teams rely on for collaboration not only between
-developers, but also between developers and their users. It's especially
-attractive to Open Source Software (OSS) teams since it supports a highly
-functional free tier.
-
-One problem is the free tier is limited to a maximum of 10K messages. When
-this limit is reached older messages become unavailable since they are
-purged. This is very impactful to active Slack teams and communities since
-older messages quite often hold a great deal of "institutional knowledge"
-that's lost when the message limit is reached.
-
-The Slack Archiver seeks to remedy this situation by extracting the history
-for specific channels to an database or file. Messages could be extracted up to
-the maximum allowed limit of 50 messages per minute for the `channels.history`
-API method. At this rate (tier 4) 86.4K messages could be theoretically
-retrieved per day.
-
-Implementers are cautioned that further research will be required to
-determine the best extraction method to use prior to attempting any
-development of this application.
+Slack is a tool many teams rely on for collaboration not only between developers but also between developers and their users. It's especially attractive to Open Source Software (OSS) teams since it supports a highly functional free tier.
+
+One problem is the free tier is limited to a maximum of 10K messages. When this limit is reached older messages become unavailable since they are purged. This is very impactful to active Slack teams and communities since older messages quite often hold a great deal of "institutional knowledge" that's lost when the message limit is reached.
+
+The Slack Archiver seeks to remedy this situation by extracting the history for specific channels to a database or file. Messages could be extracted up to the maximum allowed limit of 50 messages per minute for the channels. history API method. At this rate (tier 4) 86.4K messages could be theoretically retrieved per day.
+
+Implementers are cautioned that further research will be required to determine the best extraction method to use prior to attempting any development of this application.
+
 
 ## User Stories