fix: zkstack prover update plus a few misc things

content/10.zk-stack/20.running/20.using-a-local-zk-chain.md

@@ -1,5 +1,5 @@
 ---
-title: Using a local ZK chain
+title: Using a local ZK Chain
 description:
 ---
 
@@ -26,14 +26,14 @@ or any other wallet with funds, to deposit into your ZK chain via the bridge.
 Once you have the accounts with funds on the L1 base layer, you can do a deposit via the bridge to your ZK chain,
 and start interacting with your ZK chain using the L2 funded account.
 
-## Using your ZK chain
+## Using your chain RPC
 
 Your server contains both HTTPS as well as WebSocket (WS) RPC services that are fully web3 compatible (and contain some extra ZK Stack functionalities).
 Learn more on the [API reference page](/zksync-protocol/api).
 
-### ZKsync CLI
+## Using zksync-cli
 
-[zksync-cli](/zksync-era/tooling/zksync-cli) allows you to easily interact and develop applications on your ZK chain.
+[ZKsync CLI](/zksync-era/tooling/zksync-cli) allows you to easily interact and develop applications on your ZK chain.
 When executing any command with ZKsync CLI, you can specify RPC urls for both L1 and L2.
 Your local server contains RPCs for both.
 An example deposit command via the bridge would look like:
@@ -44,7 +44,7 @@ zksync-cli bridge deposit --rpc=http://localhost:3050 --l1-rpc=http://localhost:
 
 You can save the chain configurations for your ZK chain with ZKsync CLI by [adding a new configuration](/zksync-era/tooling/zksync-cli/configuring-chains).
 
-## Setting up the Portal
+## Using the Portal
 
 The [Portal](https://github.com/matter-labs/dapp-portal) module is a web-app that allows you to:
 
@@ -64,7 +64,7 @@ ecosystem directory. You can edit this file to configure the portal app if neede
 You can now navigate to the portal web-app. By default, portal frontend starts on
 `http://localhost:3030`, you can configure the port in `apps.yaml` file.
 
-## Setting up a Block Explorer
+## Using a Block Explorer
 
 A block explorer is a web-app that lets you view and inspect transactions, blocks,
 contracts and more. A [free open source block explorer](https://github.com/matter-labs/block-explorer) is available for your ZK chain.

content/10.zk-stack/20.running/40.proving.md

@@ -8,15 +8,37 @@ description:
 With the default configuration, your ZK chain is not running a prover, and has a DummyExecutor contract,
 which mainly “accepts” that a batch is executed without proof. This enables you to test it with much lower hardware requirements.
 
-To enable the prover, run the `zkstack prover init` command. It will guide you through the necessary configuration.
-
-There are two options for running the Boojum prover: in GPU, or in CPU.
+When enabling the Boojum prover, there are two options for running it: in GPU, or in CPU.
 
 ::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
 **Running a prover is not required** for deploying a testnet. The requirements below are only necessary if you want to enable the prover.
 ::
 
-### Requirements for GPU Prover
+### Prover dependencies
+
+Ensure you have installed:
+
+- [gcloud](https://cloud.google.com/sdk/docs/install)
+- [wget](https://www.gnu.org/software/wget/)
+- [cmake](https://apt.kitware.com/)
+- [nvcc (CUDA toolkit)](https://developer.nvidia.com/cuda-downloads)
+
+Refer to the [prover docs](https://github.com/matter-labs/zksync-era/blob/main/prover/docs/02_setup.md) for more
+information.
+
+### Running the prover
+
+To initialize the prover, first use the init command:
+
+`zkstack prover init`
+
+It will guide you through the necessary configuration.
+
+Then to run the prover the prover:
+
+`zkstack prover run`
+
+### Requirements for GPU prover
 
 The docker compose file assumes you will be running all components in the same machine. The current minimum requirements for a low TPS scenario are:
 
@@ -25,7 +47,7 @@ The docker compose file assumes you will be running all components in the same m
 - 64 GB of RAM
 - 300 GB of Disk Space (SSD preferred)
 
-### Requirements for CPU Prover
+### Requirements for CPU prover
 
 The docker compose file assumes you will be running all components in the same machine.
 The current minimum requirements for a low TPS scenario are:

content/10.zk-stack/20.running/_dir.yml

@@ -1 +1 @@
-title: Running a ZK chain
+title: Running a ZK Chain

cspell-config/cspell-dev.txt

@@ -115,3 +115,5 @@ applyl
 zbin
 scaleb
 chainid
+nvcc
+CUDA