From d87e7bc8e5c7e5187b71a9dd054d3c3aa621078d Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Mon, 19 Feb 2024 16:51:13 +0100 Subject: [PATCH] Fix typos (#35234) * fix typos * fix typo * fix typos * fix typo --- cli/src/cluster_query.rs | 4 ++-- docs/src/proposals.md | 2 +- docs/src/validator/geyser.md | 2 +- geyser-plugin-manager/src/geyser_plugin_manager.rs | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/cli/src/cluster_query.rs b/cli/src/cluster_query.rs index a5162e9498..87dc35810d 100644 --- a/cli/src/cluster_query.rs +++ b/cli/src/cluster_query.rs @@ -161,7 +161,7 @@ impl ClusterQuerySubCommands for App<'_, '_> { .takes_value(true) .value_name("BLOCKHASH") .validator(is_hash) - .help("Query fees for BLOCKHASH instead of the the most recent blockhash"), + .help("Query fees for BLOCKHASH instead of the most recent blockhash"), ), ) .subcommand( @@ -233,7 +233,7 @@ impl ClusterQuerySubCommands for App<'_, '_> { Arg::with_name("print_accounts") .long("print-accounts") .takes_value(false) - .help("Print list of non-circualting account addresses"), + .help("Print list of non-circulating account addresses"), ), ) .subcommand( diff --git a/docs/src/proposals.md b/docs/src/proposals.md index 61bd657ff3..0835a33852 100644 --- a/docs/src/proposals.md +++ b/docs/src/proposals.md @@ -37,7 +37,7 @@ To submit a new design proposal for Solana: Once a design proposal has been accepted, the PR will be merged into the `master` branch of the Solana repo. This also signifies the maintainers support your plan of attack. > **NOTE:** The merging of the PR will **automatically** create a link in the "Accepted Proposals" table of contents sidebar. -> Once approved, continue to submit PRs that implement the proposal. When the implementation reveals the need for tweaks to the proposal, be sure to update the "accepted proposal" document and have these change reviewed by the same approving maintainers. +> Once approved, continue to submit PRs that implement the proposal. When the implementation reveals the need for tweaks to the proposal, be sure to update the "accepted proposal" document and have these changes reviewed by the same approving maintainers. ### After Implemented diff --git a/docs/src/validator/geyser.md b/docs/src/validator/geyser.md index a8a29d10dd..7698563037 100644 --- a/docs/src/validator/geyser.md +++ b/docs/src/validator/geyser.md @@ -442,7 +442,7 @@ The following are the tables in the Postgres database When a validator lacks sufficient compute power, the overhead of saving the account data can cause it to fall behind the network especially when all accounts or a large number of accounts are selected. The node hosting the -PostgreSQL database need to be powerful enough to handle the database loads +PostgreSQL database needs to be powerful enough to handle the database loads as well. It has been found using GCP n2-standard-64 machine type for the validator and n2-highmem-32 for the PostgreSQL node is adequate for handling transmitting all accounts while keeping up with the network. In addition, it is diff --git a/geyser-plugin-manager/src/geyser_plugin_manager.rs b/geyser-plugin-manager/src/geyser_plugin_manager.rs index 02792525ad..a15f9e1318 100644 --- a/geyser-plugin-manager/src/geyser_plugin_manager.rs +++ b/geyser-plugin-manager/src/geyser_plugin_manager.rs @@ -304,10 +304,10 @@ pub enum GeyserPluginManagerRequest { #[derive(thiserror::Error, Debug)] pub enum GeyserPluginManagerError { - #[error("Cannot open the the plugin config file")] + #[error("Cannot open the plugin config file")] CannotOpenConfigFile(String), - #[error("Cannot read the the plugin config file")] + #[error("Cannot read the plugin config file")] CannotReadConfigFile(String), #[error("The config file is not in a valid Json format")]