Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: several typos of various value #1838

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions community/foundation-delegation-program.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ for at least 1 month before application deadline
validator or on Mocha testnet if not) that is connected and reporting
to the Celestia Labs [OTEL collector](../how-to-guides/celestia-node-metrics.md)
(for new applicants - on testnet, so that we can evaluate performance)
* Not jailed or slashed in the 6 months before application deadline
* Not jailed or slashed in the 6 months before the application deadline
* Not associated with an exchange or custodian
* Not in the top 10 validators by delegation power, unless it enters the
top 10 as a result of the Foundation’s delegation under this program
Expand All @@ -87,11 +87,11 @@ of emergency upgrades and fixes

Not adhering to any of the criteria above will automatically disqualify your
application, and violating any of the criteria after you have received
delegation will result in withdrawal of the delegation. A participant
delegation will result in the withdrawal of the delegation. A participant
who loses stake due to being jailed by the protocol may reapply to the
program after 2 cohort periods.

Applicants are also expected to have reviewed Celestia docs and recommended
Applicants are also expected to have reviewed Celestia's docs and recommended
guides on devops and monitoring setups.

Other optional but important criteria:
Expand Down
6 changes: 3 additions & 3 deletions community/modular-meetup-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ to help aid you in your journey to organize a Modular Meetup.
to raise awareness about the meetup.
7. Confirm speakers, including their availability, presentation topics,
and technical requirements. If you are working from a Speaker List,
please reach out to Nat for any support needed on coordination with speakers.
please reach out to Nat for any support needed in coordination with speakers.
8. Arrange any necessary equipment, such as microphones, projectors, and whiteboards.
9. Plan and arrange refreshments, if applicable.
10. Prepare and print any required materials, like agendas, name tags,
Expand Down Expand Up @@ -68,7 +68,7 @@ to help aid you in your journey to organize a Modular Meetup.

These are provided guidelines for different components of kickstarting
a Modular Meetup to help you get started on the logistics of organizing
a meetup. A lot of those guidelines are thanks to the wonderful write ups
a meetup. A lot of those guidelines are thanks to the wonderful write-ups
in [Ethereum Meetup Support Program](https://emsp.gitbook.io/ethereum-meetup-support-program/meetup-kit)
and [Elastic Community Organizer Guides](https://www.elastic.co/community/usergroupguide).

Expand Down Expand Up @@ -163,7 +163,7 @@ for organizing successful Modular Meetups for Celestia.
meetup group or speaking at other events before launching a
new group. This approach will help spread the word about your
planned Modular Meetup and gauge interest. Speakers are covered
in the following section with a reference to Speaker List offered
in the following section with a reference to the Speaker List offered
by the Modular Meetup program.
3. Establish connections with other user groups:
- Forge relationships with other tech-focused meetup groups to
Expand Down
2 changes: 1 addition & 1 deletion how-to-guides/blobstream-x-deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ WALLET_TYPE=PRIVATE_KEY
# The private key of the deployer account
PRIVATE_KEY=
# The address of the succinct fee vault contract. Set it to an example address
# if you don't want to use a vault like: 0x0000000000000000000000000000000000000001
# if you don't want to use a vault-like: 0x0000000000000000000000000000000000000001
SUCCINCT_FEE_VAULT_12345=
```

Expand Down
4 changes: 2 additions & 2 deletions how-to-guides/quick-start.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,7 @@ Feeling creative? Post your favorite quote and [share it on Twitter](https://x.c
celestia blob submit 0x71756f746573 '"Simplicity is the ultimate sophistication." -Leonardo da Vinci'
```

Once you run this command, you'll see a height and data committment in the response. This means your data has been successfully posted to the network!
Once you run this command, you'll see a height and data commitment in the response. This means your data has been successfully posted to the network!

```bash
{
Expand All @@ -191,7 +191,7 @@ Once you run this command, you'll see a height and data committment in the respo
To retrieve the data you posted, use the following command:

```bash
celestia blob get [height] [namespace] [committment]
celestia blob get [height] [namespace] [commitment]
```

In this example, you'll use the height and commitment from the response above:
Expand Down