From b464a8b8f9d486205b1aa5582d58120efa3be533 Mon Sep 17 00:00:00 2001 From: Mike MacCana Date: Mon, 30 Sep 2024 16:20:55 +1000 Subject: [PATCH] Prettier --- docs/advanced/confirmation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/advanced/confirmation.md b/docs/advanced/confirmation.md index eb698b009..b26144204 100644 --- a/docs/advanced/confirmation.md +++ b/docs/advanced/confirmation.md @@ -341,8 +341,8 @@ of the cluster state with one of the following methods: 1. Fetch your RPC node's highest processed slot by using the [`getSlot`](/docs/rpc/http/getSlot.mdx) RPC API with the `processed` commitment level and then call the - [`getMaxShredInsertSlot`](/docs/rpc/http/getMaxShredInsertSlot.mdx) RPC API to - get the highest slot that your RPC node has received a “shred” of a block + [`getMaxShredInsertSlot`](/docs/rpc/http/getMaxShredInsertSlot.mdx) RPC API + to get the highest slot that your RPC node has received a “shred” of a block for. If the difference between these responses is very large, the cluster is producing blocks far ahead of what the RPC node has processed. 2. Call the `getLatestBlockhash` RPC API with the `confirmed` commitment level