From 62f52909f31ca0f10abc02ad3ef43b3e53ad1bf6 Mon Sep 17 00:00:00 2001
From: Alex Sharov <AskAlexSharov@gmail.com>
Date: Wed, 27 Apr 2022 12:08:26 +0700
Subject: [PATCH] Update README.md (#3987)

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 47a5781bfa..b855c9f1d8 100644
--- a/README.md
+++ b/README.md
@@ -153,9 +153,9 @@ Erigon can be used as an execution-layer for beacon chain consensus clients (Eth
 relies on availability of receipts - don't prune them: don't add character `r` to `--prune` flag. However, old receipts
  are not needed for Eth2 and you can safely prune them with `--prune.r.before=11184524` in combination with `--prune htc`.
 
-You must run the [JSON-RPC daemon](#json-rpc-daemon) in addition to the Erigon.
+You must enable JSON-RPC by `--http` and add `engine` to `--http.api` list. (Or run the [JSON-RPC daemon](#json-rpc-daemon) in addition to the Erigon)
 
-If beacon chain client on a different device: add `--http.addr 0.0.0.0` (JSON-RPC daemon listen on localhost by default)
+If beacon chain client on a different device: add `--http.addr 0.0.0.0` (JSON-RPC listen on localhost by default)
 .
 
 Once the JSON-RPC daemon is running, all you need to do is point your beacon chain client to `<ip address>:8545`,
-- 
GitLab