From d9f4f438bab8e82556cfc4e0a3f6c1d088692b36 Mon Sep 17 00:00:00 2001
From: Marcus Wentz <52706599+MarcusWentz@users.noreply.github.com>
Date: Fri, 29 Sep 2023 21:40:08 -0400
Subject: [PATCH] docs(website): proposer + prover private key format and
 status log command to find errors (#14862)

Co-authored-by: Roger <50648015+RogerLamTd@users.noreply.github.com>
---
 .../website/pages/docs/guides/enable-a-proposer.mdx  | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/packages/website/pages/docs/guides/enable-a-proposer.mdx b/packages/website/pages/docs/guides/enable-a-proposer.mdx
index 046ccc9643..fb800dc283 100644
--- a/packages/website/pages/docs/guides/enable-a-proposer.mdx
+++ b/packages/website/pages/docs/guides/enable-a-proposer.mdx
@@ -80,13 +80,21 @@ If you are not running a local prover, then you can specify a prover from the [p
 
 ### Check proposer status logs
 
-Run this command to verify you have some proposer logs:
+To see if your proposer is running correctly or has errors run:
+
+```sh
+docker compose logs -f taiko_client_proposer
+```
+
+### See proposed blocks
+
+When you run:
 
 ```sh
 docker compose logs -f taiko_client_proposer | egrep "Propose transactions succeeded"
 ```
 
-You should see a log if you have proposed a block: `📝 Propose transactions succeeded`.
+if your proposer successfully proposed a block, your logs should show: `📝 Propose transactions succeeded`.
 
 You can check all commands to see proposer logs in the [node runner manual](/docs/manuals/node-runner-manual#view-client-proposer-logs).