From c53174dc56dd1049669d5721eea3ecd08d7afe14 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Wed, 17 Nov 2021 07:11:48 +0000 Subject: [PATCH] Fixup processed docs (#21316) (#21317) (cherry picked from commit 6546c3cbaec843d49bb717d38a8f41663284b2ea) Co-authored-by: Tyera Eulberg --- docs/src/developing/clients/jsonrpc-api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/developing/clients/jsonrpc-api.md b/docs/src/developing/clients/jsonrpc-api.md index b17291b214..a2dacfd8d4 100644 --- a/docs/src/developing/clients/jsonrpc-api.md +++ b/docs/src/developing/clients/jsonrpc-api.md @@ -158,8 +158,8 @@ recognized this block as finalized - It does not count votes on descendants of a block, only direct votes on that block. - This confirmation level also upholds "optimistic confirmation" guarantees in release 1.3 and onwards. -- `"processed"` - the node will query its most recent block. Note that the block -may not be complete. +- `"processed"` - the node will query its most recent block. Note that the block +may still be skipped by the cluster. For processing many dependent transactions in series, it's recommended to use `"confirmed"` commitment, which balances speed with rollback safety.