From ed4e6465d641efff9ad93d38fbf1ad2d0995f633 Mon Sep 17 00:00:00 2001
From: NagyZoltanPeter <113987313+NagyZoltanPeter@users.noreply.github.com>
Date: Thu, 20 Jun 2024 14:34:39 +0200
Subject: [PATCH] Changed SERVICE_UNAVAILABLE to NO_PEERS_TO_RELAY according to
 review arguments

---
 standards/core/lightpush.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/standards/core/lightpush.md b/standards/core/lightpush.md
index a779074..d3c702f 100644
--- a/standards/core/lightpush.md
+++ b/standards/core/lightpush.md
@@ -53,12 +53,11 @@ If they are unable to do so for some reason, they SHOULD return an error code in
 |--------|------|------|
 | SUCCESS  | 200 | Successfull push, response's relay_peer_count holds the number of peers the message is pushed.    |
 | BAD_REQUEST | 400   | Wrong request payload.    |
-| NO_PEERS_TO_RELAY | 404 | Service node has no relay peers.   |
 | PAYLOAD_TOO_LARGE | 413 | Message exceeds certain size limit, it can depend on network configuration, see status_desc for details.  |
 | UNSUPPORTED_TOPIC | 421 | Requested push on pubsub_topic is not possible as the service node does not support it. |
 | TOO_MANY_REQUESTS | 429 | DOS protection prevented this request as the current request exceeds the configured request rate. |
 | INTERNAL_SERVER_ERROR  | 500 | status_desc holds explanation of the error.  |
-| SERVICE_UNAVAILABLE | 503 | Lightpush service not available  |
+| NO_PEERS_TO_RELAY | 503 | Lightpush service not available as node has no relay peers. |
 
 > The list of error codes are not complete and can be extended in the future.