From 6a0041544babca5afe53ecc200c04934666bf5d0 Mon Sep 17 00:00:00 2001
From: NagyZoltanPeter <113987313+NagyZoltanPeter@users.noreply.github.com>
Date: Tue, 17 Sep 2024 11:18:51 +0200
Subject: [PATCH] Fixing typos and namings on review findings

---
 standards/core/peer-exchange.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/standards/core/peer-exchange.md b/standards/core/peer-exchange.md
index de321cb..ed1901b 100644
--- a/standards/core/peer-exchange.md
+++ b/standards/core/peer-exchange.md
@@ -94,12 +94,12 @@ Responders, MUST include a `status` in the response in any case and possible des
 
 | Result | Code | Note |
 |--------|------|------|
-| SUCCESS  | 200 | Successfull request-respond. In response the answer must contain `PeerExchangeResponse`  |
-| BAD_REQUEST | 400   | Wrong request payload. It must only contain `reques` field.  |
-| BAD_RESPOND | 401   | Wrong respond payload. If success it must contain `respond` and `response_status` fields. If failure, only `response_status` is set.  |
+| SUCCESS  | 200 | Successfull request-respond.  |
+| BAD_REQUEST | 400   | Wrong request payload. It must only contain `request` field.  |
+| BAD_RESPONSE | 401   | Wrong response payload. If success it must contain `response` and `status` fields. If failure, only `status` is set.  |
 | TOO_MANY_REQUESTS | 429 | DOS protection prevented this request as the current request exceeds the configured request rate. |
 | SERVICE_UNAVAILABLE  | 503 | Request cannot be served, either issue on Responder side or having no suitable peer to issue request.  |
-| DIAL_FAILRE | 599 | Requester side problem calling PeerExchange peer. |
+| DIAL_FAILURE | 599 | Requester side problem calling PeerExchange peer. |
 
 ## Implementation Suggestions