Skip to content

Commit ace5794

Browse files
0xLucca0xlukem
andauthored
Apply suggestions from code review
Co-authored-by: Lucas Malizia <[email protected]>
1 parent 8cd0e42 commit ace5794

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -115,7 +115,7 @@ To define your chain specification:
115115

116116
2. Edit the `plain_chain_spec.json` file:
117117

118-
- Update the `name`, `id` and `protocolId` fields to unique values for your parachain
118+
- Update the `name`, `id`, and `protocolId` fields to unique values for your parachain
119119
- Change `para_id` and `parachainInfo.parachainId` fields to the parachain ID you obtained previously. Make sure to use a number without quotes
120120
- Modify the `balances` field to specify the initial balances for your accounts in SS58 format
121121
- Insert the account IDs and session keys in SS58 format generated for your collators in the `collatorSelection.invulnerables` and `session.keys` fields
@@ -210,7 +210,7 @@ polkadot-omni-node --collator \
210210
--rpc-port 9988
211211
```
212212
213-
In this example, the first `--port` setting specifies the port for the collator node and the second `--port` specifies the embedded relay chain node port. The first `--rpc-port` setting specifies the port you can connect to the collator. The second `--rpc-port` specifies the port for connecting to the embedded relay chain.
213+
In this example, the first `--port` setting specifies the port for the collator node, and the second `--port` specifies the embedded relay chain node port. The first `--rpc-port` setting specifies the port you can connect to the collator. The second `--rpc-port` specifies the port for connecting to the embedded relay chain.
214214
215215
Insert your generated session key into your collator keystore. Run the following command replacing `INSERT_SECRET_PHRASE` and `INSERT_PUBLIC_KEY_HEX_FORMAT` with the values from the session key you generated in the [Generate Customs Keys for Your Collator](#generate-customs-keys-for-your-collator) section:
216216

tutorials/polkadot-sdk/parachains/zero-to-hero/obtain-coretime.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,13 +35,13 @@ Once the above is complete, obtaining coretime is the last step to enable your p
3535
There are two extrinsics which allow you to place orders for on-demand coretime:
3636

3737
- [**`onDemand.placeOrderAllowDeath`**](https://paritytech.github.io/polkadot-sdk/master/polkadot_runtime_parachains/on_demand/pallet/dispatchables/fn.place_order_allow_death.html){target=\_blank} - will [reap](https://wiki.polkadot.network/docs/learn-accounts#existential-deposit-and-reaping){target=\_blank} the account once the provided funds run out
38-
- [**`onDemand.placeOrderKeepAlive`**](https://paritytech.github.io/polkadot-sdk/master/polkadot_runtime_parachains/on_demand/pallet/dispatchables/fn.place_order_keep_alive.html){target=\_blank} - includes a check which will **not** reap the account if the provided funds will run out, ensuring the account is kept alive
38+
- [**`onDemand.placeOrderKeepAlive`**](https://paritytech.github.io/polkadot-sdk/master/polkadot_runtime_parachains/on_demand/pallet/dispatchables/fn.place_order_keep_alive.html){target=\_blank} - includes a check that will **not** reap the account if the provided funds run out, ensuring the account is kept alive
3939

4040
To produce a block in your parachain, navigate to Polkadot.js Apps and ensure you're connected to the Paseo relay chain. Then, access the [**Developer > Extrinsics**](https://polkadot.js.org/apps/#/extrinsics){target=\_blank} tab and execute the `onDemand.placeOrderAllowDeath` extrinsic from the account that registered the `ParaID`. For this example, `maxAmount` is set to `1000000000000` (this value may vary depending on the network conditions), and `paraId` is set to `4518`:
4141

4242
![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/obtain-coretime/obtain-coretime-9.webp)
4343

44-
With each successful on-demand extrinsic, the parachain will produce a new block. You can verify this by checking the logs of the collator. If the extrinsic is successful, you should see output similar to the following:
44+
With each successful on-demand extrinsic, the parachain will produce a new block. You can verify this by checking the collator logs. If the extrinsic is successful, you should see output similar to the following:
4545

4646
--8<-- 'code/tutorials/polkadot-sdk/parachains/zero-to-hero/obtain-coretime/obtain-coretime-1.html'
4747

tutorials/polkadot-sdk/parachains/zero-to-hero/set-up-a-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ This tutorial requires two essential tools:
4343

4444
This installs the `chain-spec-builder` binary.
4545

46-
- [**Polkadot Omni Node**](https://crates.io/crates/polkadot-omni-node/0.4.0){target=\_blank} - is a white-labeled binary, released as a part of Polkadot SDK that can act as the collator of a parachain in production, with all the related auxillary functionalities that a normal collator node has: RPC server, archiving state, etc. Moreover, it can also run the wasm blob of the parachain locally for testing and development.
46+
- [**Polkadot Omni Node**](https://crates.io/crates/polkadot-omni-node/0.4.0){target=\_blank} - is a white-labeled binary, released as a part of Polkadot SDK that can act as the collator of a parachain in production, with all the related auxiliary functionalities that a normal collator node has: RPC server, archiving state, etc. Moreover, it can also run the wasm blob of the parachain locally for testing and development.
4747

4848
To install it, run the following command:
4949

0 commit comments

Comments
 (0)