From 3da399ef7708fd58ead863ed925751abfa753232 Mon Sep 17 00:00:00 2001
From: FabijanC <fabijan.corak@gmail.com>
Date: Tue, 4 Jul 2023 15:16:23 +0200
Subject: [PATCH] Fix blocks-on-demand docs [skip ci]

---
 page/docs/guide/blocks.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/page/docs/guide/blocks.md b/page/docs/guide/blocks.md
index a0d2c9053..b5d591007 100644
--- a/page/docs/guide/blocks.md
+++ b/page/docs/guide/blocks.md
@@ -24,7 +24,8 @@ Response:
 
 ### Create a block on demand
 
-If you start Devnet with `--blocks-on-demand` CLI option, all transactions will be pending and stored in a pending block (targetable via block ID `"pending"`).
+If you start Devnet with the `--blocks-on-demand` CLI option, all valid transactions will be stored in a pending block (targetable via block ID `"pending"`). Since Devnet v0.5.5, the status of these transactions is no longer pending, but accepted. The status of the block is pending.
+
 To create a block on demand, send a `POST` request to `/create_block`. This will convert the pending block to the latest block (targetable via block ID `"latest"`), giving it a block hash and a block number. All subsequent transactions will be stored to a new pending block.
 
 In case of demanding block creation with no pending transactions, a new empty block will be generated.