Docs rectify typographical inaccuracies

blog/2024-01-24-goerli.md

@@ -14,7 +14,7 @@ tags: [goerli]
 
 ### Monitoring [Jan 25, 2024 - 12:00 PT]
 
-- **Actions:** We successfully deployed the fixes yesterday, and are continuing to monitor the results for an additional day. We don’t expect users to face any further issues, and can resume normal operations for partial and full withdrawals from EigenPods on Goerli testnet.
+- **Actions:** We successfully deployed the fixes yesterday, and are continuing to monitor the results for an additional day. We don’t expect users to face any further issues, and can resume normal operations for partial and full withdrawals from EigenPods on the Goerli testnet.
 
 - **Additional Support:** If you are still encountering issues with EigenPod withdrawals (partial or full), please raise your issue via the [EigenLayer Discord](https://discord.gg/eigenlayer) #support-restakers channel.
 
@@ -30,7 +30,7 @@ tags: [goerli]
 
 - **Safety of User Assets:** We assure all users that all funds on Goerli and mainnet have been safe and secure throughout the incident. There has been no impact on mainnet operations.
 
-- **Actions:** We have successfully deployed the fixes, and are monitoring the results. We don’t expect users to face any further issues, and can resume normal operations for partial and full withdrawals from EigenPods on Goerli testnet.
+- **Actions:** We have successfully deployed the fixes, and are monitoring the results. We don’t expect users to face any further issues, and can resume normal operations for partial and full withdrawals from EigenPods on the Goerli testnet.
 
 - **Next Update**: Jan 25, 2024 - 12:00 PT
 

blog/2024-02-01-goerli.md

@@ -12,7 +12,7 @@ tags: [goerli]
 
 ### Monitoring [Feb 07, 2024 - 16:30 PT]
 
-- **Actions:** We identified some scalability bottlenecks that led to this incident. We deployed fixes this week, restored normal opertation, and are continuing to monitor our service. We don’t expect users to face any further issues, and can resume normal operations of partial and full withdrawals from EigenPods on Goerli testnet.
+- **Actions:** We identified some scalability bottlenecks that led to this incident. We deployed fixes this week, restored normal operation, and are continuing to monitor our service. We don’t expect users to face any further issues, and can resume normal operations of partial and full withdrawals from EigenPods on Goerli testnet.
 
 - **Additional Support:** If you are still encountering issues with EigenPod withdrawals (partial or full), please raise your issue via the [EigenLayer Discord](https://discord.gg/eigenlayer) #support-restakers channel.
 

blog/2024-02-16-eigenda-goerli.md

@@ -13,7 +13,7 @@ tags: [goerli,eigenda]
 
 ### Monitoring [Feb 16, 2024 - 15:30 PT]
 
-- **Actions:** We identified the root cause that resulted in this incident with the Churner service. We have successfully deployed the fixes, and are continuing to monitor the service. We don’t expect operators to face any further issues related to opting-in of EigenDA, and can resume normal operations on Goerli testnet.
+- **Actions:** We identified the root cause that resulted in this incident with the Churner service. We have successfully deployed the fixes, and are continuing to monitor the service. We don’t expect operators to face any further issues related to opting-in to EigenDA, and can resume normal operations on Goerli testnet.
 
 - **Additional Support:** If you (EigenLayer operators) are still encountering issues with the EigenDA opt-in functionality, please raise your issue via the [EigenLayer Discord](https://discord.gg/eigenlayer) #support-operators channel.
 

docs/eigenda/integrations-guides/dispersal/api-error-codes.md

@@ -43,7 +43,7 @@ This table summarizes all the current status codes and their mappings to HTTP co
 | "blob size cannot exceed 2 MiB"                                                                      | InvalidArgument (400)  | This error occurs when the size of the blob data exceeds the maximum allowed size of 2 MiB.                                 |
 | "blob size must be greater than 0"                                                                   | InvalidArgument (400)  | This error occurs when the size of the blob data is zero.                                                                   |
 | "number of custom_quorum_numbers must not exceed 256"                                                | InvalidArgument (400)  | This error occurs when the number of custom quorum numbers provided in the request exceeds 256.                             |
-| "number of custom_quorum_numbers must not exceed number of quorums"                                  | InvalidArgument (400)  | This error occurs when the number of custom quorum numbers provided in the request exceeds the total number of quorums.     |
+| "number of custom_quorum_numbers must not exceed the number of quorums"                                  | InvalidArgument (400)  | This error occurs when the number of custom quorum numbers provided in the request exceeds the total number of quorums.     |
 | "custom_quorum_numbers must be in range [0, 254], but found %d"                                      | InvalidArgument (400)  | This error occurs when a custom quorum number is outside the valid range of [0, 254].                                       |
 | "custom_quorum_numbers must be in range [0, \<quorum count>], but found %d"                          | InvalidArgument (400)  | This error occurs when a custom quorum number is outside the valid range of [0, QuorumCount-1].                             |
 | "custom_quorum_numbers must not contain duplicates"                                                  | InvalidArgument (400)  | This error occurs when the custom quorum numbers contain duplicate values.                                                  |

docs/eigenda/integrations-guides/dispersal/blob-metering-and-rate-limits.md

@@ -24,7 +24,7 @@ network and can be found on the network's description.
 
 ## Encoded System Throughput
 
-The total volume of data per unit time written to EigenDA operator set is known
+The total volume of data per unit of time written to EigenDA operator set is known
 as the Encoded System Throughput (ECS). The "encoded" part denotes that this
 data is not the raw input data that was sent to the disperser by the client.
 Rather the encoded data is an extended version of the input data which is

docs/eigenda/integrations-guides/dispersal/blob-serialization-requirements.md

@@ -62,7 +62,7 @@ ERROR:
   Message: rpc error: code = InvalidArgument desc = encountered an error to convert a 32-bytes into a valid field element, please use the correct format where every 32bytes(big-endian) is less than 21888242871839275222246405745257275088548364400416034343698204186575808495617
 ```
 
-The simplest way to resovlve this until we have a dedicated EigenDA CLI is to
+The simplest way to resolve this until we have a dedicated EigenDA CLI is to
 use the `kzgpad` utility documented in the [tutorial](./cli-guide.md):
 
 ```bash

docs/eigenda/integrations-guides/dispersal/cli-guide.md

@@ -59,7 +59,7 @@ Example request:
 # Download the EigenDA repo via gh client or wget
 $ gh repo clone Layr-Labs/eigenda
 # Change your working directory to the eigenda folder in order to point to the
-# protobuf defintions correctly
+# protobuf definitions correctly
 $ cd eigenda
 
 $ grpcurl \

docs/eigenda/integrations-guides/dispersal/overview.md

@@ -31,7 +31,7 @@ graph TD;
     C -->|15 days elapses since dispersal finalization| D[Blob Expired];
 ```
 
-The Disperser offers an asynchrounous API for dispersing blobs, where clients should poll the `GetBlobStatus()` endpoint with the dispersal request ID they received from calling one of the two disperse endpoints until the disperser reports the blob as successfully dispersed and finalized.
+The Disperser offers an asynchronous API for dispersing blobs, where clients should poll the `GetBlobStatus()` endpoint with the dispersal request ID they received from calling one of the two disperse endpoints until the disperser reports the blob as successfully dispersed and finalized.
 
 ## Endpoints