From 542d4c1c0d39b8e8f98888f9db8e3bcc83ba24d7 Mon Sep 17 00:00:00 2001 From: umutbozdag Date: Sun, 22 Oct 2023 20:56:50 +0300 Subject: [PATCH] fix wrong naming in How does gRPC work? section (#28) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2dccf1c..bdad1d6 100644 --- a/README.md +++ b/README.md @@ -179,7 +179,7 @@ The diagram below illustrates the overall data flow for **gRPC**. 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. gPRC encodes the **client stub** into a binary format and sends it to the low-level transport layer. +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. Step 5: gRPC sends the packets over the network via HTTP2. Because of binary encoding and network optimizations, gRPC is said to be 5X faster than JSON.