Update README.md

Author: marcilio

README.md

@@ -12,7 +12,7 @@ This project provides a reusable Lambda function (Connector Lambda) that can be
 
 The figure below illustrates the problem being addressed. On the left-side (A) you see a state machine with three states called ```state-1```, ```state-2```, and ```state-3```. These states could be represented by Lambda functions (state machine tasks) or EC2 workers (state machine activities). You're trying to add these Lambdas to a new state machine but their inputs/outputs don't match up. For example, ```state-1``` produces a red cicle while ```state-2``` expects a green square and ```state-3``` expects a red triangle as inputs. 
 
- On the right-hand side (B) you can see how the Connector Lambdas can be used to transform ```state-1```'s output to match the expected inputs of ```state-2``` and ```state-3```. Two Connector states are shown, both of which are backed up by the same Lambda function. Notice that the Connector states use different tranformation Jinja2 templates specified by you. That is, your tranformation code is not scattered through your Lambdas but instead placed into templates that can be easily understood and managed.
+ On the right-hand side (B) you can see how the Connector Lambdas (blue ellipses ```Transform 1-2``` and ```Transform 1-3```) can be used to transform ```state-1```'s output to match the expected inputs of ```state-2``` and ```state-3```. Two Connector states are shown, both of which are backed up by the same Lambda function. Notice that the Connector states use different tranformation Jinja2 templates specified by you. That is, your tranformation code is not scattered through your Lambdas but instead placed into templates that can be easily understood and managed.
 
 ![approach-overview](/doc/aws-step-functions-connector-overview.png)