From fd96b1bb4c1126b2d27e98e4b8886afcb3392a4c Mon Sep 17 00:00:00 2001
From: Gospodin Bodurov <gospodin@bodurov.net>
Date: Tue, 27 Aug 2019 09:21:34 +0300
Subject: [PATCH] Add clarification

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

diff --git a/README.md b/README.md
index a0bf4e8..372515f 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ Better approach is to use Public(Certificates)/Private keys encryption scheme wh
 
 ## Workflows
 - If user clicks on the Vereign App directly then Vereign App opens Vereign dashboard web app in Custom Chrome Tab/IOS View Controller (cookies and local storage are shared with native Browser)
-- If user uses the 3rd Party App workflow, then slightly modified IETF prosposed workflow is executed. Only Vereign App has Oauth2 secret key and it is transferred to the server using the standard IETF approach.
+- If user uses the 3rd Party App workflow, then slightly modified IETF prosposed workflow is executed. Only Vereign App has Oauth2 secret key and it is transferred to the server using the standard IETF approach. Again Custom Chrome Tab/IOS View Controller is used (cookies and local storage are shared with native Browser)
 
 ## Projects used
 - https://github.com/openid/AppAuth-Android - We are wrapping this library with Flutter Android wrapper
-- 
GitLab