From abd6c5cbc9cd44af3f0aea4df79acb51db7669b2 Mon Sep 17 00:00:00 2001
From: leonardo federico <leonardo.fed@gmail.com>
Date: Mon, 19 Sep 2016 16:22:19 +0200
Subject: [PATCH]

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

diff --git a/README.md b/README.md
index 7ce742b..c9873d8 100644
--- a/README.md
+++ b/README.md
@@ -627,7 +627,7 @@ application’s data to AWS without losing any data and within the given timefra
 A) Copy the data to Amazon S3 using multiple threads and multi-part upload for large files over the
 weekend, and work in parallel with your developers to reconfigure the replicated application environment
 to leverage Amazon S3 to serve the engineering files.<br>
-<code>B) Sync the application data to Amazon S3 starting a week before the migration, on Friday morning perform</span>
+<span style="color:#4caf50;">B) Sync the application data to Amazon S3 starting a week before the migration, on Friday morning perform</span>
 a final sync, and copy the entire data set to your AWS file server after the sync completes.</code></br>
 C) Copy the application data to a 1-TB USB drive on Friday and immediately send overnight, with Saturday
 delivery, the USB drive to AWS Import/Export to be imported as an EBS volume, mount the resulting EBS