From 414c8f1c4c8126b18641f8b6c102c5bdffffc359 Mon Sep 17 00:00:00 2001 From: VolodymyrBg Date: Sat, 11 Jan 2025 02:08:28 +0200 Subject: [PATCH] Fix typos (#1832) * Update modular-meetup-toolkit.md * Update arbitrum-deploy.md * Update arbitrum-full-node.md * Update blobstream-proof-queries.md * Update how-to-stake-tia.md --- community/modular-meetup-toolkit.md | 2 +- how-to-guides/arbitrum-deploy.md | 2 +- how-to-guides/arbitrum-full-node.md | 2 +- how-to-guides/blobstream-proof-queries.md | 2 +- learn/how-to-stake-tia.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/community/modular-meetup-toolkit.md b/community/modular-meetup-toolkit.md index 7b1d4119801..f3a8efb66bc 100644 --- a/community/modular-meetup-toolkit.md +++ b/community/modular-meetup-toolkit.md @@ -32,7 +32,7 @@ help you plan and execute your meetups effectively. - [Sample presentation - run a light node](https://docs.google.com/presentation/d/1fV7OYUdW4kafkZcgHwFenFWDbSIwkk0R6BnSKrAV-Hc/edit#slide=id.g20713cce7c2_1_0) - Summary: - This is an overview presentation goes over running a Celestia light node. + This is an overview presentation that goes over running a Celestia light node. You can find existing video presentations for this here: - The sample presentation covers: 1. What is a Celestia light node? diff --git a/how-to-guides/arbitrum-deploy.md b/how-to-guides/arbitrum-deploy.md index 8d80e1820ff..d96400d538c 100644 --- a/how-to-guides/arbitrum-deploy.md +++ b/how-to-guides/arbitrum-deploy.md @@ -184,7 +184,7 @@ root of your cloned `orbit-setup-script` repository. ### Step 7: Pick an L2 RPC URL for the Batch Poster In order for the Batch Poster, which is responsible for posting batches of data, to -subscribe to Blobstream's smart contract events, the node most use a WebSocket +subscribe to Blobstream's smart contract events, the node must use a WebSocket connection, since an HTTP one will not support subscriptions. This RPC URL is different from the `parent-chain.connection.url` object used in the node config, and is not necessary when running a full node. WebSocket (WSS) URLs which are diff --git a/how-to-guides/arbitrum-full-node.md b/how-to-guides/arbitrum-full-node.md index d9e038ff40b..e2e22d7a02f 100644 --- a/how-to-guides/arbitrum-full-node.md +++ b/how-to-guides/arbitrum-full-node.md @@ -1,5 +1,5 @@ --- -description: A guide on how to run a full node or validating full node on your Orbit rollup. +description: A guide on how to run a full node or validate a full node on your Orbit rollup. --- # Running a full node and/or validator diff --git a/how-to-guides/blobstream-proof-queries.md b/how-to-guides/blobstream-proof-queries.md index e03d8881967..cf16b6410e7 100644 --- a/how-to-guides/blobstream-proof-queries.md +++ b/how-to-guides/blobstream-proof-queries.md @@ -766,7 +766,7 @@ If we take the example blob that was submitted in the [`RollupInclusionProofs.t.sol`](https://github.com/celestiaorg/blobstream-contracts/blob/3a552d8f7bfbed1f3175933260e6e440915d2da4/src/lib/verifier/test/RollupInclusionProofs.t.sol#L64-L65), we can convert it to bytes using the `abi.encode(...)` as done for [this variable](https://github.com/celestiaorg/blobstream-contracts/blob/3a552d8f7bfbed1f3175933260e6e440915d2da4/src/lib/verifier/test/RollupInclusionProofs.t.sol#L384-L402). -This can be gotten from the above result of the +This can be obtained from the above result of the [transaction inclusion proof](#2-transaction-inclusion-proof) query in the field `data`. diff --git a/learn/how-to-stake-tia.md b/learn/how-to-stake-tia.md index 5e77d33772c..976cb7a94a6 100644 --- a/learn/how-to-stake-tia.md +++ b/learn/how-to-stake-tia.md @@ -86,7 +86,7 @@ On the following screen choose a validator of your choice, enter the desired amount, and click `Review`. Following that, review the transaction details and select `Stake`, -then wait for the transaction to finalize. +then wait for the transaction to be finalized. ![Keplr1](/img/leap/leap2.gif)