Skip to content

Commit c27f996

Browse files
authored
Update deploy-t1-prover.md
- Heading sentence casing - Minor phrasing suggestions
1 parent b224d1c commit c27f996

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

docs/learn/type-1-prover/deploy-t1-prover.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
This document provides guidelines on how to run Polygon Type-1 prover, specifically for proving transactions, but with the option to test full blocks of less than 4M gas.
22
So, it is similar to [`eth-proof`](https://github.com/wborgeaud/eth-proof) but for transaction proofs.
33

4-
## Quick Start
4+
## Quick start
55

66
There are two ways to run this prover. The simplest way to get started is
77
to use the `in-memory` runtime of
@@ -52,7 +52,7 @@ is the _last_ transaction hash in the block.
5252
Once you've successfully generated a witness, you're ready to start
5353
proving either with the `in-memory` run time or the `amqp` runtime.
5454

55-
### In Memory Proving
55+
### In-memory proving
5656

5757
Running the prover with the `in-memory` setup requires no setup. You
5858
can attempt to generate a proof with a command like this.
@@ -78,7 +78,7 @@ state root of the preceding block. You can adjust the `--num-workers`
7878
flag based on the number of available compute resources. As a rule of
7979
thumb, you'd probably want at least 8 cores per worker.
8080

81-
### AMQP Proving
81+
### AMQP proving
8282

8383
Proving in a distributed compute environment depends on an AMQP
8484
server. We're not going to cover the setup of RabbitMQ, but assuming
@@ -100,11 +100,10 @@ MEMORY_CIRCUIT_SIZE="17..30" \
100100
paladin-worker --runtime amqp --amqp-uri=amqp://localhost:5672
101101
```
102102

103-
This will start the worker and have it await tasks. Depending on the
104-
size of your machine, you may be able to run several workers on the
103+
This will start the worker and have it await tasks. Depending on your machine's system capacity, you can run several workers on the
105104
same operating system. An example [systemd
106105
service](https://github.com/0xPolygonZero/eth-tx-proof/blob/jhilliard/deployment/deploy/paladin-worker@.service) is included. Once that
107-
service is installed, you could enable and start 16 workers on the
106+
service is installed, you'll be able to enable up to 16 workers on the
108107
same VM like this:
109108

110109
```bash

0 commit comments

Comments
 (0)