From 49ebd398fcd0b79f2a332426ea0540de4548cc8d Mon Sep 17 00:00:00 2001
From: timmy <126319815+TIM56887@users.noreply.github.com>
Date: Sun, 3 Nov 2024 18:30:06 +0800
Subject: [PATCH] Update README.adoc

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

diff --git a/README.adoc b/README.adoc
index c840791..2d20e96 100644
--- a/README.adoc
+++ b/README.adoc
@@ -350,7 +350,7 @@ So far, you have a web-based service that handles the core operations that invol
 * Merely using `GET`, `POST`, and so on is not REST.
 * Having all the CRUD operations laid out is not REST.
 
-In fact, what we have built so far is better described as *RPC* (*Remote Procedure Call*), because there is no way to know how to interact with this service. If you published this today, you wouldd also have to write a document or host a developer's portal somewhere with all the details.
+In fact, what we have built so far is better described as *RPC* (*Remote Procedure Call*), because there is no way to know how to interact with this service. If you published this today, you would also have to write a document or host a developer's portal somewhere with all the details.
 
 This statement of Roy Fielding's may further lend a clue to the difference between *REST* and *RPC*: