From 787a615c9a99fe395c7413bcef694054026ddedd Mon Sep 17 00:00:00 2001
From: DevScript <thebhandariprakash@gmail.com>
Date: Mon, 23 Oct 2023 09:59:44 +1100
Subject: [PATCH] gRPC: move text above gRPC diagram (#25)

Update README.md  to move text above the gRPC diagram.

---------

Co-authored-by: PrakashB <prakash.bhandari@bigtincan.com>
---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index b5bad47..64feb25 100644
--- a/README.md
+++ b/README.md
@@ -169,14 +169,14 @@ GraphQL can aggregate multiple REST requests into one query. GraphQL server orga
 
 ### How does gRPC work?
 
-<p>
-  <img src="images/grpc.jpg">
-</p>
-
 RPC (Remote Procedure Call) is called “**remote**” because it enables communications between remote services when services are deployed to different servers under microservice architecture. From the user’s point of view, it acts like a local function call.
 
 The diagram below illustrates the overall data flow for **gRPC**.
 
+<p>
+  <img src="images/grpc.jpg">
+</p>
+
 Step 1: A REST call is made from the client. The request body is usually in JSON format.
 
 Steps 2 - 4: The order service (gRPC client) receives the REST call, transforms it, and makes an RPC call to the payment service. gRPC encodes the **client stub** into a binary format and sends it to the low-level transport layer.