From c4d661e6e9a24aab073dba4aee84b52e35d82082 Mon Sep 17 00:00:00 2001 From: xiaobei0715 <1505929057@qq.com> Date: Fri, 27 Dec 2024 21:31:23 +0800 Subject: [PATCH] chore: fix incorrect quotation marks --- community/modular-meetup-toolkit.md | 8 ++++---- how-to-guides/arbitrum-integration.md | 2 +- how-to-guides/bridge-node.md | 6 +++--- how-to-guides/ethereum-fallback.md | 2 +- how-to-guides/light-node.md | 2 +- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/community/modular-meetup-toolkit.md b/community/modular-meetup-toolkit.md index 7b1d4119801..0b4d6f75195 100644 --- a/community/modular-meetup-toolkit.md +++ b/community/modular-meetup-toolkit.md @@ -15,7 +15,7 @@ help you plan and execute your meetups effectively. - [Brand kit](https://company-223625.frontify.com/d/JoSwaZS4Mjpj/guidelines) 1. Includes logo files, color schemes, typography, icons and illustrations -## Sample “Introduction to Modularity” workshop presentation +## Sample ＂Introduction to Modularity＂ workshop presentation - [Sample presentation - introduction to modularity](https://docs.google.com/presentation/d/1R4bkWgU2nql1chwVwND4seREHbKzugl0-Xr88w3QdIQ/edit#slide=id.g1b629412475_0_0) - Summary: This is an overview presentation on Modular blockchains and @@ -28,7 +28,7 @@ help you plan and execute your meetups effectively. 5. Sovereign Rollups 6. Q&A session -## Sample “Run a Celestia light node” workshop presentation +## Sample ＂Run a Celestia light node＂ workshop presentation - [Sample presentation - run a light node](https://docs.google.com/presentation/d/1fV7OYUdW4kafkZcgHwFenFWDbSIwkk0R6BnSKrAV-Hc/edit#slide=id.g20713cce7c2_1_0) - Summary: @@ -43,7 +43,7 @@ help you plan and execute your meetups effectively. 6. Best practices for maintaining a light node 7. Q&A session -## Sample “Deploy a Sovereign Rollup” workshop presentation +## Sample ＂Deploy a Sovereign Rollup＂ workshop presentation - [Sample presentation - deploy a sovereign rollup](https://docs.google.com/presentation/d/163yP8lQ28k-xfL3jcdX2cfO-3zg8e63AOuHeHxde3vk/edit#slide=id.g20713cce7c2_1_596) - Summary: This is an overview presentation on deploying a sovereign rollup @@ -56,7 +56,7 @@ help you plan and execute your meetups effectively. 4. Setting up a sovereign rollup: hardware and software requirements 5. Q&A session -## Sample “Modular Meetup Introduction” workshop presentation +## Sample ＂Modular Meetup Introduction＂ workshop presentation - [Sample presentation - modular meetup introduction](https://docs.google.com/presentation/d/1HIOKwnCRylofo4sp5I93hsfY3DKWbmXxfvMdoiIk-3I/edit?usp=sharing) - The sample presentation covers: diff --git a/how-to-guides/arbitrum-integration.md b/how-to-guides/arbitrum-integration.md index 52b0dddb6b4..29ebb819034 100644 --- a/how-to-guides/arbitrum-integration.md +++ b/how-to-guides/arbitrum-integration.md @@ -90,7 +90,7 @@ The [@celestiaorg/nitro](https://github.com/celestiaorg/nitro) integration [uses the same fallback mechanism](https://github.com/celestiaorg/nitro/blob/f01968eb3d4e19329e9c92b050e98a8e5772f1f2/arbnode/batch_poster.go#L845-L857). [More information can be found on the Ethereum fallback mechanisms for Celestia](./ethereum-fallback.md), -which enables Ethereum L2s (or L3s) to “fall back” to using Ethereum +which enables Ethereum L2s (or L3s) to ＂fall back＂ to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta. diff --git a/how-to-guides/bridge-node.md b/how-to-guides/bridge-node.md index 06891fe147e..299412439fe 100644 --- a/how-to-guides/bridge-node.md +++ b/how-to-guides/bridge-node.md @@ -12,12 +12,12 @@ Bridge nodes connect the data availability layer and the consensus layer. A Celestia bridge node has the following properties: -1. Import and process “raw” headers & blocks from a trusted core process +1. Import and process ＂raw＂ headers & blocks from a trusted core process (meaning a trusted RPC connection to a celestia-core node) in the Consensus network. Bridge nodes can run this core process internally (embedded) or simply connect to a remote endpoint. Bridge nodes also have the option of being an active validator in the consensus network. -2. Validate and erasure code the “raw” blocks +2. Validate and erasure code the ＂raw＂ blocks 3. Supply block shares with data availability headers to light nodes in the DA network. ![bridge-node-diagram](/img/nodes/BridgeNodes.png) @@ -40,7 +40,7 @@ From an implementation perspective, Bridge nodes run two separate processes: - **celestia-node** augments the above with a separate libp2p network that serves data availability sampling requests. The team sometimes refers to - this as the “halo” network. + this as the ＂halo＂ network. ## Hardware requirements diff --git a/how-to-guides/ethereum-fallback.md b/how-to-guides/ethereum-fallback.md index dc43515c2df..1260e98f4fa 100644 --- a/how-to-guides/ethereum-fallback.md +++ b/how-to-guides/ethereum-fallback.md @@ -11,7 +11,7 @@ prev: # Ethereum fallback Ethereum fallback is a mechanism -that enables Ethereum L2s (or L3s) to “fallback” to using Ethereum +that enables Ethereum L2s (or L3s) to ＂fallback＂ to using Ethereum calldata for data availability in the event of downtime on Celestia Mainnet Beta. This feature is currently supported by Celestia integrations with: diff --git a/how-to-guides/light-node.md b/how-to-guides/light-node.md index b6b9b930ed3..0b51625d12c 100644 --- a/how-to-guides/light-node.md +++ b/how-to-guides/light-node.md @@ -18,7 +18,7 @@ way to interact with Celestia networks. Light nodes have the following behavior: -1. They listen for `ExtendedHeaders`, i.e. wrapped “raw” headers, that notify +1. They listen for `ExtendedHeaders`, i.e. wrapped ＂raw＂ headers, that notify Celestia nodes of new block headers and relevant DA metadata. 2. They perform DAS on the received headers