deploy node set up instructions

Author: kmurphypolygon

docs/cdk/get-started/deploy-validium/node/prerequisites.md

@@ -21,7 +21,7 @@
 | `make` | 3.80.0 | https://www.gnu.org/software/make/ |
 | `docker` | 24.0.0 | https://docs.docker.com/engine/install/ |
 | `pip3` | 20.0.0 | https://pip.pypa.io/en/stable/installation/ |
-| `python3` | 3.8.0 | https://www.python.org/downloads/ |
+| [For testing] `python3` | 3.8.0 | https://www.python.org/downloads/ |
 | [For testing] `polycli` | 0.1.39 | https://github.com/maticnetwork/polygon-cli/tree/main |
 
 1. Create a `version-check.sh` file and copy and paste the script below. 

docs/cdk/get-started/deploy-validium/node/set-up.md

@@ -28,87 +28,92 @@
     cd ~/cdk-validium
     ```
 
-## 1. Downloading cdk-validium-node, cdk-data-availability, and cdk-bridge-service
+## Download `cdk-validium-node`, `cdk-data-availability`, and `cdk-bridge-service`
 
-Now clone the `0.0.3` release of `cdk-validium-node`. 
+1. Clone the `0.0.3` release of `cdk-validium-node`. 
 
-```bash
-git clone --depth 1 --branch v0.0.3 https://github.com/0xPolygon/cdk-validium-node.git
-```
+    ```bash
+    git clone --depth 1 --branch v0.0.3 https://github.com/0xPolygon/cdk-validium-node.git
+    ```
 
-We also must download and extract version `0.0.3` of `cdk-data-availability.` The release file is available here:
+2. Download and extract version `0.0.3` of `cdk-data-availability` as a tar.gz file. 
 
-[Untitled Database](https://www.notion.so/b329e3b1511943ae979cc2b4c73a35e8?pvs=21)
+    !!! info
+        The release file is available here: [Untitled Database](https://www.notion.so/b329e3b1511943ae979cc2b4c73a35e8?pvs=21)
 
-Downloading `cdk-validium-contracts` as a ***`tar.gz`*** and extracting
+    ```bash
+    curl -L -o cdk-data-availability.tar.gz https://github.com/0xPolygon/cdk-data-availability/archive/refs/tags/v0.0.3.tar.gz
+    \tar -xzf cdk-data-availability.tar.gz
+    ```
 
-```bash
-~/cdk-validium % curl -L -o cdk-data-availability.tar.gz https://github.com/0xPolygon/cdk-data-availability/archive/refs/tags/v0.0.3.tar.gz
-\tar -xzf cdk-data-availability.tar.gz
-```
+3. Finally, download the `cdk-bridge-service` release `0.3.1`. The release file can be found here:
 
-Finally, the `cdk-bridge-service` release `0.3.1`. The release file can be found here:
+    ```bash
+    curl -L -o cdk-bridge-service.tar.gz https://github.com/0xPolygonHermez/zkevm-bridge-service/archive/refs/tags/v0.3.1.tar.gz
+    \tar -xzf cdk-bridge-service.tar.gz
+    ```
 
-```bash
-curl -L -o cdk-bridge-service.tar.gz https://github.com/0xPolygonHermez/zkevm-bridge-service/archive/refs/tags/v0.3.1.tar.gz
-\tar -xzf cdk-bridge-service.tar.gz
+    You should see three new directories in `cdk-validium/`: 
 
-```
-Now we have three new directories in *`cdk-validium/`* named ***`cdk-data-availability-0.0.3`, `cdk-validium-node` and `zkevm-bridge-service-0.3.1`***
+    - `cdk-data-availability-0.0.3`
+    - `cdk-validium-node`
+    - `zkevm-bridge-service-0.3.1`
 
-## 2. Preparing the environment
+## Prepare the environment
 
-We will begin our setup in the node directory.
+Navigate to the node directory we cloned at the previous step: `cdk-validium-node/`.
 
-Navigate into the node directory we cloned from the previous step***`cdk-validium-node/`***
+    ```bash
+    cd cdk-validium-node/
+    ```
 
-```bash
-~/cdk-validium % cd cdk-validium-node/
-```
+## Set up the database
 
-### Setup the database
+1. Run the docker command below to start an instance of the `psql` database. The database is used for many of the services, such as the node, prover, DAC, and bridge service.
 
-Run the docker command to start an instance of the `psql` database. The database is used for many of the services, such as the node, prover, DAC, and bridge service.
+    ```bash
+    docker run -e POSTGRES_USER=cdk_user -e POSTGRES_PASSWORD=cdk_password -e POSTGRES_DB=postgres -p 5432:5432 postgres:15
+    ```
 
-```bash
-docker run -e POSTGRES_USER=cdk_user -e POSTGRES_PASSWORD=cdk_password -e POSTGRES_DB=postgres -p 5432:5432 postgres:15
-```
+    !!! note "Port is in use"
+        If you are unable to start the process because a port is in use, check the processes occupying the port then kill those processes.
 
-*note: if you are unable to start the process because port is in use, check the processes occupying the port then kill the processes*
+        ```bash
+        sudo lsof -t -i:5432
+        kill -9 <PID>
+        ```
 
-```bash
-sudo lsof -t -i:5432
-kill -9 <PID>
-```
+2.  Use the following command to validate the setup (`\q` to exit).
 
-Once you have postgres running, validate you have the following setup correctly:
+    ```bash
+    PGPASSWORD=cdk_password psql -h localhost -U cdk_user -d postgres -p 5432
+    #=> \q
+    ```
 
-- an admin account called: `cdk_user` with a password of `cdk_password`
-- postgres server running on `localhost:5432`
+    You should have: 
 
-You can use the following command to validate the steps, `\q` to exit:
+    - An admin account called: `cdk_user` with a password of `cdk_password`.
+    - A postgres server running on `localhost:5432`.
 
-```bash
-PGPASSWORD=cdk_password psql -h localhost -U cdk_user -d postgres -p 5432
-#=> \q
-```
+## Provision the database
 
-### Provision the database
+The `cdk-validium-node` directory contains a script called `single_db_server.sql` that provisions all the databases required for the prover, state, and pool to operate. 
 
-The `cdk-validium-node` directory contains a script called `single_db_server.sql` that provisions all the databases required for the prover, state, and pool to operate. Run the script to provision all the necessary databases and schemas that will be used for both the prover and node:
+1. Run the script to provision all the necessary databases and schemas used for the prover and node:
 
-```bash
-~/cdk-validium/cdk-validium-node % PGPASSWORD=cdk_password psql -h localhost -U cdk_user -d postgres -p 5432 -a -q -f ./db/scripts/single_db_server.sql
-```
+    ```bash
+    cd /cdk-validium/cdk-validium-node
+    PGPASSWORD=cdk_password psql -h localhost -U cdk_user -d postgres -p 5432 -a -q -f ./db/scripts/single_db_server.sql
+    ```
 
-In addition to the provisions required for the prover and node, another provision is needed for the Data Availability Committee (DAC). We can set this up now for use later.
+2. In addition to the provisions required for the Data Availability Committee (DAC). We can set this up now to use later.
 
-```bash
-PGPASSWORD=cdk_password psql -h localhost -U cdk_user -d postgres -p 5432 -c "CREATE DATABASE committee_db;"
-```
+    ```bash
+    PGPASSWORD=cdk_password psql -h localhost -U cdk_user -d postgres -p 5432 -c "CREATE DATABASE committee_db;"
+    ```
 
-Finally, we will provision a database for our bridge service, which we will setup last in this guide.
+3. Finally, provision a database for the bridge service.
 
-```bash
-PGPASSWORD=cdk_password psql -h localhost -U cdk_user -d postgres -p 5432 -c "CREATE DATABASE bridge_db;"
-```
+    ```bash
+    PGPASSWORD=cdk_password psql -h localhost -U cdk_user -d postgres -p 5432 -c "CREATE DATABASE bridge_db;"
+    ```