From cd7dfe9cec707c7624b72440649107092754146f Mon Sep 17 00:00:00 2001
From: KeisukeYamashita <19yamashita15@gmail.com>
Date: Mon, 20 Jan 2020 17:49:09 +0900
Subject: [PATCH]  fix(doc): remove newline in Orca notification description

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

diff --git a/README.md b/README.md
index bbbdc71e0..e6fc41c73 100644
--- a/README.md
+++ b/README.md
@@ -24,8 +24,7 @@ The following high level diagram shows how events flow through `echo`:
 5. `orca` sends events to `echo` when:
     - a stage is starting/completed so `echo` can send notifications if any are defined on the stage
     - a pipeline (or orchestration) is starting/completed so `echo` can send notification as above
-    - a manual judgement stage is reached - a notifcation from 
-    - the user has clicked the page button on the application page
+    - a manual judgement stage is reached - a notifcation from the user has clicked the page button on the application page
 
 6. `echo` uses external services (e.g. email/slack) to send notifications.  
     Notifications can either be a result of an event received by `echo` (e.g. stage completed which has a notification on completion), or a specific notification request from another service (e.g. orca will send a notifcation for Manual Judgement stage)