From daabf15c125dd57fdf4ccb9df3fc0e5118c158ec Mon Sep 17 00:00:00 2001 From: panditdhamdhere Date: Sat, 20 Dec 2025 11:03:40 +0530 Subject: [PATCH] docs: fix typos, grammar, and formatting issues Fixed spelling errors, grammar issues, and formatting inconsistencies across all documentation files. --- connect-brave-wallet-to-getblock.md | 4 ++-- getting-started/monitoring-and-analytics.md | 2 +- ...-model-context-protocol-with-getblock-api-endpoints.md | 2 +- ...al-time-hyperliquid-whale-tracker-bot-with-getblock.md | 2 +- ...ols-on-solana-dexes-with-getblocks-yellowstone-grpc.md | 8 ++++---- ...-mints-in-real-time-with-getblocks-yellowstone-grpc.md | 6 +++--- 6 files changed, 12 insertions(+), 12 deletions(-) diff --git a/connect-brave-wallet-to-getblock.md b/connect-brave-wallet-to-getblock.md index b86ef68..4cb9805 100644 --- a/connect-brave-wallet-to-getblock.md +++ b/connect-brave-wallet-to-getblock.md @@ -80,7 +80,7 @@ If the network of interest is already present, such as with Ethereum, click on t
Exploring Brave Wallet network accounts
-Look at the **RPC URLs** settings fro Ethereum: usually, a default Brave Wallet endpoint is present here. As every wallet user connects to it by default, it’s overloaded and insecure. That’s why a custom RPC URL is essential for Web3 activities. +Look at the **RPC URLs** settings for Ethereum: usually, a default Brave Wallet endpoint is present here. As every wallet user connects to it by default, it’s overloaded and insecure. That’s why a custom RPC URL is essential for Web3 activities. {% endstep %} {% step %} @@ -139,7 +139,7 @@ Voila—the free and highly secure Polygon zkEVM node endpoint is ready. Copy the access token and go to the Brave settings. Add the new RPC URLs field and paste the access token. -
Adding GetBlock zkEVM endpoint to Brave Wallet’
+
Adding GetBlock zkEVM endpoint to Brave Wallet
{% endstep %} {% endstepper %} diff --git a/getting-started/monitoring-and-analytics.md b/getting-started/monitoring-and-analytics.md index 745158b..8f34589 100644 --- a/getting-started/monitoring-and-analytics.md +++ b/getting-started/monitoring-and-analytics.md @@ -30,7 +30,7 @@ Customize the data view by **parameters** or by **access** **tokens** using the Select the time period, protocol name, networks (mainnet/testnet), region, and API interfaces to analyze the data by parameters. -
How to track your blokchain API usage

The Statistics tab shows more in-depth and customizable data analysis for your endpoints

+
How to track your blockchain API usage

The Statistics tab shows more in-depth and customizable data analysis for your endpoints

All data is displayed through infographics, including: diff --git a/guides/basic-level-model-context-protocol-with-getblock-api-endpoints.md b/guides/basic-level-model-context-protocol-with-getblock-api-endpoints.md index fac7a58..08d9a2c 100644 --- a/guides/basic-level-model-context-protocol-with-getblock-api-endpoints.md +++ b/guides/basic-level-model-context-protocol-with-getblock-api-endpoints.md @@ -605,7 +605,7 @@ https://go.getblock.us/7hys368hus... ``` {% endtab %} -{% tab title="Signapore" %} +{% tab title="Singapore" %} ```bash https://go.getblock.asia/f782e8ec54.... ``` diff --git a/guides/build-a-real-time-hyperliquid-whale-tracker-bot-with-getblock.md b/guides/build-a-real-time-hyperliquid-whale-tracker-bot-with-getblock.md index 69b7674..652979b 100644 --- a/guides/build-a-real-time-hyperliquid-whale-tracker-bot-with-getblock.md +++ b/guides/build-a-real-time-hyperliquid-whale-tracker-bot-with-getblock.md @@ -71,7 +71,7 @@ Keep your endpoint safe, as it contains an access token Create the following files to have a basic structure for your project: ```bash -├── index.js // Main apllication +├── index.js // Main application └── .env // Environment variables └── .gitignore // Git ignore file ``` diff --git a/guides/monitoring-liquidity-pools-on-solana-dexes-with-getblocks-yellowstone-grpc.md b/guides/monitoring-liquidity-pools-on-solana-dexes-with-getblocks-yellowstone-grpc.md index b5926b3..ab01088 100644 --- a/guides/monitoring-liquidity-pools-on-solana-dexes-with-getblocks-yellowstone-grpc.md +++ b/guides/monitoring-liquidity-pools-on-solana-dexes-with-getblocks-yellowstone-grpc.md @@ -113,15 +113,15 @@ Ensure you securely store both the base endpoint and the access token. You'll ne 1. Create a directory for your project -```javascript +```bash mkdir pool-monitor cd pool-monitor -npm init-y +npm init -y ``` 2. Install Dependencies: -```javascript +```bash npm install @triton-one/yellowstone-grpc bs58@5.0.0 ``` @@ -203,7 +203,7 @@ What this does: ```javascript // GetBlock Configuration const ENDPOINT = "https://go.getblock.io"; // Your region's endpoint -const TOKEN = process.env.GETBLOCK_TOKEN; ; // Your generated token +const TOKEN = process.env.GETBLOCK_TOKEN; // Your generated token ``` What this does: diff --git a/guides/tracking-pump.fun-token-mints-in-real-time-with-getblocks-yellowstone-grpc.md b/guides/tracking-pump.fun-token-mints-in-real-time-with-getblocks-yellowstone-grpc.md index 490cbe3..1cf2509 100644 --- a/guides/tracking-pump.fun-token-mints-in-real-time-with-getblocks-yellowstone-grpc.md +++ b/guides/tracking-pump.fun-token-mints-in-real-time-with-getblocks-yellowstone-grpc.md @@ -133,10 +133,10 @@ GetBlock provides a single TLS endpoint - you don't need to configure different 1. Create a directory for your project -``` +```bash mkdir pumpfun-monitor cd pumpfun-monitor -npm init-y +npm init -y ``` 2. Install Dependencies: @@ -159,7 +159,7 @@ What these packages do: Create the following files to have a basic structure for your project: ```bash -├── pumpfun-monitor.js // Main apllication +├── pumpfun-monitor.js // Main application └── .env // Environment variables └── .gitignore // Git ignore file ```