From d518952ece39795960b733fcf2471d845caf42d7 Mon Sep 17 00:00:00 2001
From: KaranveerB <52545097+KaranveerB@users.noreply.github.com>
Date: Sat, 15 Jun 2024 13:48:33 -0700
Subject: [PATCH] Fix typo in RPC

---
 e2e/rpc.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/e2e/rpc.rst b/e2e/rpc.rst
index 9749f1e..0b8a5d4 100644
--- a/e2e/rpc.rst
+++ b/e2e/rpc.rst
@@ -170,7 +170,7 @@ that networks are not perfect channels. Two such functions are:
 -  Support large message sizes through fragmentation and reassembly
 
 An RPC protocol might “define this problem away” by choosing to run on
-top of a reliable protocol like TCP, but in many cases, the RCP protocol
+top of a reliable protocol like TCP, but in many cases, the RPC protocol
 implements its own reliable message delivery layer on top of an
 unreliable substrate (e.g., UDP/IP). Such an RPC protocol would likely
 implement reliability using acknowledgments and timeouts, similarly to