From a665e5174a8f07af7967ab003c3e21401808bbe8 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Wed, 17 Feb 2021 17:16:27 -0800 Subject: [PATCH] =?UTF-8?q?Network=20Mode=E2=86=92P2P=20Mode?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../references/rippled-api/api-conventions/error-formatting.md | 2 +- .../rippled-api/api-conventions/response-formatting.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/references/rippled-api/api-conventions/error-formatting.md b/content/references/rippled-api/api-conventions/error-formatting.md index afabb74943..d461993d7a 100644 --- a/content/references/rippled-api/api-conventions/error-formatting.md +++ b/content/references/rippled-api/api-conventions/error-formatting.md @@ -102,7 +102,7 @@ For other errors that returned with HTTP status code 200 OK, the responses are f All methods can potentially return any of the following values for the `error` code: - `amendmentBlocked` - The server is [amendment blocked](amendments.html#amendment-blocked) and needs to be updated to the latest version to stay synced with the XRP Ledger network. -- `failedToForward` - ([Reporting Mode][] servers only) The server tried to forward this request to a Network Mode server, but the connection failed. +- `failedToForward` - ([Reporting Mode][] servers only) The server tried to forward this request to a P2P Mode server, but the connection failed. - `invalid_API_version` - The server does not support the [API version number](request-formatting.html#api-versioning) from the request. - `jsonInvalid` - (WebSocket only) The request is not a proper JSON object. - JSON-RPC returns a 400 Bad Request HTTP error in this case instead. diff --git a/content/references/rippled-api/api-conventions/response-formatting.md b/content/references/rippled-api/api-conventions/response-formatting.md index 0222634523..9021eeb4ce 100644 --- a/content/references/rippled-api/api-conventions/response-formatting.md +++ b/content/references/rippled-api/api-conventions/response-formatting.md @@ -13,7 +13,7 @@ The fields of a successful response include: | `result` | Object | The result of the query; contents vary depending on the command. | | `warning` | String | _(May be omitted)_ If this field is provided, the value is the string `load`. This means the client is approaching the [rate limiting](rate-limiting.html) threshold where the server will disconnect this client. | | `warnings` | Array | _(May be omitted)_ If this field is provided, it contains one or more **Warnings Objects** with important warnings. For details, see [API Warnings](#api-warnings). [New in: rippled 1.5.0][] | -| `forwarded` | Boolean | _(May be omitted)_ If `true`, this request has been forwarded from a [Reporting Mode][] server to a Network Mode server because the request requires data that is not available in Reporting Mode. The default is `false`. | +| `forwarded` | Boolean | _(May be omitted)_ If `true`, this request and response have been forwarded from a [Reporting Mode][] server to a P2P Mode server (and back) because the request requires data that is not available in Reporting Mode. The default is `false`. | ## Example Successful Response