From 5be6f0c4a529e41435490ae4436e2dfef17cc509 Mon Sep 17 00:00:00 2001
From: raedwards <39269273+raedwards@users.noreply.github.com>
Date: Wed, 16 May 2018 14:17:56 +0200
Subject: [PATCH] Update alpakka.md

---
 radar/2017-10-01/alpakka.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/radar/2017-10-01/alpakka.md b/radar/2017-10-01/alpakka.md
index 013ae4b..651ff0f 100644
--- a/radar/2017-10-01/alpakka.md
+++ b/radar/2017-10-01/alpakka.md
@@ -7,13 +7,13 @@ quadrant:   languages-and-frameworks
 
 When using [Akka Streams](/languages-and-frameworks/akka-streams.html) to build
 reactive data transformation services you usually need to connect to several
-different services like FTP, S3 buckets, AMQP brokers or different databases.
+different services such as FTP, S3 buckets, AMQP brokers or different databases.
 
 [Alpakka](https://developer.lightbend.com/docs/alpakka/current/) provides
 integration building blocks for Akka Streams to access these services in a
-reactive fashion and also contains transformations for working with XML, CSV or
+reactive fashion and contains transformations for working with XML, CSV or
 JSON structured data.
 
-Akka Streams and Alpakka combined enables us to build small reactive
-integration services with minimal resource consumption and good performance and
-are good alternative to bigger ESB solutions or integration tools.
\ No newline at end of file
+Combined, Akka Streams and Alpakka enable us to build small reactive
+integration services with minimal resource consumption and good performance, and
+are a good alternative to larger ESB solutions or integration tools.