From 7f3cd3da5dd1a1c2be8a0cdf5d13f3a2f57ff96e Mon Sep 17 00:00:00 2001
From: xiaolou86 <20718693+xiaolou86@users.noreply.github.com>
Date: Fri, 27 Oct 2023 11:23:01 +0800
Subject: [PATCH] chore: fix typos

---
 docs/errors.md                                            | 4 ++--
 packages/indexer-cli/src/commands/indexer/rules/delete.ts | 2 +-
 packages/indexer-cli/src/commands/indexer/rules/get.ts    | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/errors.md b/docs/errors.md
index 4bd04fcc9..511a66142 100644
--- a/docs/errors.md
+++ b/docs/errors.md
@@ -788,7 +788,7 @@ Allocation amounts must be non-negative numbers. To resolve this issue ensure th
 
 **Summary**
 
-Action was not executed succesfully: contracts paused or operator not authorized.
+Action was not executed successfully: contracts paused or operator not authorized.
 
 **Solution**
 
@@ -842,7 +842,7 @@ Failed to resolve POI: POI not available for deployment at current epoch start b
 
 **Solution**
 
-This error typically indicates a subgraph deployment that is too far behind the chain head to resolve a valid POI for closing the allocation. To succesfully resolve the POI and close the allocation you'll need to wait for the index node to sync the deployment enough to generate a POI for the current epoch start block. If you do not want to wait to sync you may choose to forfeit indexing rewards for the allocation by force closing it with a 0 POI by creating an unallocate or reallocate action item: `graph indexer actions queue unallocate/reallocate <deployment-id> <allocation-id> 0 true`.
+This error typically indicates a subgraph deployment that is too far behind the chain head to resolve a valid POI for closing the allocation. To successfully resolve the POI and close the allocation you'll need to wait for the index node to sync the deployment enough to generate a POI for the current epoch start block. If you do not want to wait to sync you may choose to forfeit indexing rewards for the allocation by force closing it with a 0 POI by creating an unallocate or reallocate action item: `graph indexer actions queue unallocate/reallocate <deployment-id> <allocation-id> 0 true`.
 
 ## IE068
 
diff --git a/packages/indexer-cli/src/commands/indexer/rules/delete.ts b/packages/indexer-cli/src/commands/indexer/rules/delete.ts
index c002a3d13..707dafd84 100644
--- a/packages/indexer-cli/src/commands/indexer/rules/delete.ts
+++ b/packages/indexer-cli/src/commands/indexer/rules/delete.ts
@@ -95,7 +95,7 @@ module.exports = {
       // Since we are not deleting all rules, we must require a protocol network from the user
       if (!protocolNetwork) {
         throw Error(
-          'The --netowrk option must be used when deleting a glboal Indexing Rule',
+          'The --network option must be used when deleting a glboal Indexing Rule',
         )
       }
       const chainAlias = resolveChainAlias(protocolNetwork)
diff --git a/packages/indexer-cli/src/commands/indexer/rules/get.ts b/packages/indexer-cli/src/commands/indexer/rules/get.ts
index c8c3d2b1f..1d7efe120 100644
--- a/packages/indexer-cli/src/commands/indexer/rules/get.ts
+++ b/packages/indexer-cli/src/commands/indexer/rules/get.ts
@@ -62,7 +62,7 @@ module.exports = {
       } else {
         if (!protocolNetwork) {
           throw Error(
-            'The --netowrk option must be used when quering for a single Indexing Rule',
+            'The --network option must be used when quering for a single Indexing Rule',
           )
         }
         const ruleIdentifier = { identifier, protocolNetwork }