From ec2ee855d402545b3610daa8b36ef79ca50dbac8 Mon Sep 17 00:00:00 2001
From: Julian Insua <jii.julious@gmail.com>
Date: Mon, 1 Aug 2022 04:19:21 -0300
Subject: [PATCH] Update gRPC deffinition (#1368)

* Update gRPC deffinition

I thought that some high-level definition of this would be nice.

* Update content/roadmaps/101-backend/content/109-apis/103-grpc.md

Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>
---
 content/roadmaps/101-backend/content/109-apis/103-grpc.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/roadmaps/101-backend/content/109-apis/103-grpc.md b/content/roadmaps/101-backend/content/109-apis/103-grpc.md
index ce7bea057..8df3c06c0 100644
--- a/content/roadmaps/101-backend/content/109-apis/103-grpc.md
+++ b/content/roadmaps/101-backend/content/109-apis/103-grpc.md
@@ -2,6 +2,8 @@
 
 gRPC is a high-performance, open source universal RPC framework
 
+RPC stands for Remote Procedure Call, there's an ongoing debate on what the g stands for. RPC is a protocol that allows a program to execute a procedure of another program located on another computer. The great advantage is that the developer doesn’t need to code the details of the remote interaction. The remote procedure is called like any other function. But the client and the server can be coded in different languages.
+
 <ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <BadgeLink colorScheme='blue' badgeText='Official Website' href='https://grpc.io/'>gRPC Website</BadgeLink>
 <BadgeLink colorScheme='blue' badgeText='Docs' href='https://grpc.io/docs/'>gRPC Docs</BadgeLink>