From e95a124c4b48be0adca878f585710f2159ce7ca6 Mon Sep 17 00:00:00 2001
From: crcgenesys <89788904+crcgenesys@users.noreply.github.com>
Date: Mon, 11 Nov 2024 16:27:05 -0500
Subject: [PATCH] More linter updates...

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

diff --git a/README.md b/README.md
index c1be3d3..4ee79bf 100644
--- a/README.md
+++ b/README.md
@@ -2,5 +2,5 @@
 
 This Genesys Cloud Developer Blueprint explains how to deploy a Microsoft Power Virtual Agent (VA) bot to answer your customer queries through web messaging and Messenger. The blueprint also provides the solution for using a third-party bot that Genesys Cloud does not support as a strategic vendor. The solution uses the Genesys Bot Connector that provides the API and acts as the link between Genesys Cloud and the bot. In this solution, the bot interpreter application created using AWS Lambda functions acts in between Genesys Cloud and Microsoft Power VA. The application receives the utterances from the Messenger through Genesys Bot Connector. It changes the format of the request before sending out an HTTP request to Microsoft Power VA for Natural Language Understanding (NLU). It also converts the response message received from Microsoft Power VA to match the postUtterance API that is provided by the Genesys Bot Connector.
 
-![Web Messaging with Genesys Bot Connector and Microsoft Power VA](blueprint/images/bot-wm-aws.png "Web Messaging with Genesys Bot Connector and Microsoft Power VA")
+![Web Messaging with Genesys Bot Connector and Microsoft Power VA](blueprint/images/overview.png "Web Messaging with Genesys Bot Connector and Microsoft Power VA")