chore: fix a large number of spelling issues

docs/new/how-to-guides/sinks/sql/db_out.md

@@ -29,7 +29,7 @@ Consider that you want to dump all the Pump.Fun data decoded with an IDL into yo
 
 Clone the [Pump Fun Substreams GitHub repository](https://github.com/enoldev/pump-fun-substreams).
 
-### Inpsect the Project
+### Inspect the Project
 
 - Observe the `substreams.yaml` file:
 

docs/new/references/old-references/gui.md

@@ -77,7 +77,7 @@ You can see the output of a different module by using the `u` and `i` keys. In t
 
 ### Searching in the Output
 
-To search for a speciifc text in the output:
+To search for a specific text in the output:
 
 1. Press the `/` key.
 2. Introduce the text.

docs/new/references/old-references/running-substreams.md

@@ -20,7 +20,7 @@ substreams run -e mainnet.eth.streamingfast.io:443 \
 The `--start-block` flag specifies the starting block of the Substreams (i.e. at which block the Substreams will start indexing data)
 
 {% hint style="info" %}
-**Note**: In Solana, `--start-block` specifies the **slot**, not the block numnber.
+**Note**: In Solana, `--start-block` specifies the **slot**, not the block number.
 {% endhint %}
 
 ### Substreams `run`

docs/new/tutorials/solana/account-changes.md

@@ -10,7 +10,7 @@ By the end of this tutorial, you will have a working Substreams feed that allows
 Data for Solana account changes is available on a rolling three-month window.
 {% endhint %}
 
-For each Solana Account block, only the latest update per account is recorded, see the [Protobuf Referece](https://buf.build/streamingfast/firehose-solana/file/main:sf/solana/type/v1/account.proto). If an account is deleted, a payload with `deleted == True` is provided. Additionally, events of low importance we're omitted, such as those with the special owner “Vote11111111…” account or changes that do not affect the account data (ex: lamport changes).
+For each Solana Account block, only the latest update per account is recorded, see the [Protobuf Reference](https://buf.build/streamingfast/firehose-solana/file/main:sf/solana/type/v1/account.proto). If an account is deleted, a payload with `deleted == True` is provided. Additionally, events of low importance we're omitted, such as those with the special owner “Vote11111111…” account or changes that do not affect the account data (ex: lamport changes).
 
 {% hint style="success" %} The Account Changes Substreams natively handles a change of ownership upon delete. {% endhint %}
 

docs/new/tutorials/stellar.md

@@ -13,7 +13,7 @@ In this guide, you'll learn how to initialize a Stellar-based Substreams project
 
 2. Running `substreams init` will give you the option to choose between two Stellar project options. Select the one that best fits your requirements:
     - **stellar-minimal**: Creates a simple Substreams that extracts raw Stellar block data and generates corresponding Rust code. This path will start you with the full raw block, you can navigate to the `substreams.yaml` (the manifest) to modify the input.
-    - **stellar-transactions-operations**: Creates a Substreams that extracts and decodes Stellar trasactions or operations using the cached [Stellar Foundational Module](https://substreams.dev/packages/stellar-foundational/v0.3.0). If you choose the index transactions, you will be able to filter by **source account(s)**. If you choose to index operations, you will be able to filter by **operation name**.
+    - **stellar-transactions-operations**: Creates a Substreams that extracts and decodes Stellar transactions or operations using the cached [Stellar Foundational Module](https://substreams.dev/packages/stellar-foundational/v0.3.0). If you choose the index transactions, you will be able to filter by **source account(s)**. If you choose to index operations, you will be able to filter by **operation name**.
 
 {% hint style="info" %}
  The first streamable block for Stellar on Substreams is currently 55,411,000.

reqctx/noopspan.go

@@ -7,7 +7,7 @@ import (
 	"go.opentelemetry.io/otel/trace/noop"
 )
 
-// NoopSpan is an implementation of span that preforms no operations.
+// NoopSpan is an implementation of span that performs no operations.
 type NoopSpan struct{}
 
 func (n *NoopSpan) EndWithErr(e *error) {}

sink/buffer.go

@@ -15,7 +15,7 @@ import (
 // about our internal "fake" finality which happens once enough block
 // has "passed" which is the size of the undo block size
 type blockDataBuffer struct {
-	// data is kept striclty ordered and its ordering must be respected
+	// data is kept strictly ordered and its ordering must be respected
 	// throughout the implementation.
 	//
 	// The array is always fully allocated, but the `dataEmptyAt` determines

sink/manifest.go

@@ -86,7 +86,7 @@ func ReadManifestAndModule(
 		return nil, nil, nil, fmt.Errorf("get output module %q: %w", resolvedOutputModuleName, err)
 	}
 	if module.GetKindStore() != nil {
-		return nil, nil, nil, fmt.Errorf("ouput module %q is of type 'Store'", resolvedOutputModuleName)
+		return nil, nil, nil, fmt.Errorf("output module %q is of type 'Store'", resolvedOutputModuleName)
 	}
 
 	zlog.Info("validating output module type", zap.String("module_name", module.Name), zap.String("module_type", module.Output.Type))

sink/manifest_test.go

@@ -32,15 +32,15 @@ func TestReadManifestAndModule(t *testing.T) {
 			assert.NoError,
 		},
 		{
-			"multile expected type accepted",
+			"multiple expected type accepted",
 			args{"testdata/substreams.yaml", nil, "kv_out", "kv-out,graph-out", false},
 			true,
 			"kv_out",
 			"f0b74c6dc57fa840bf1e7ff526431f9f1b5240d0",
 			assert.NoError,
 		},
 		{
-			"multile expected type accepted, inverted",
+			"multiple expected type accepted, inverted",
 			args{"testdata/substreams.yaml", nil, "graph_out", "kv-out,graph-out", false},
 			true,
 			"graph_out",

sink/sinker.go

@@ -720,7 +720,7 @@ func (s *Sinker) doRequest(
 				}
 			} else {
 				// In the case of dealing with an undo buffer, it's expected that a fork will never
-				// go beyong the first block in the buffer because if it does, `s.buffer.HandleBlockUndoSignal` here
+				// go beyond the first block in the buffer because if it does, `s.buffer.HandleBlockUndoSignal` here
 				// returns an error.
 				//
 				// This means ultimately that we expect to never call the downstream `BlockUndoSignalHandler` function.

sink/sinker_viper.go

@@ -241,7 +241,7 @@ func AddFlagsToSet(flags *pflag.FlagSet, ignore ...FlagInclusionExclusion) {
 // it to create a new Sinker instance.
 //
 // If you want to extract the sink output module's name directly from the Substreams
-// package, if supported by your sink, instead of an actual name for paramater
+// package, if supported by your sink, instead of an actual name for parameter
 // `outputModuleNameArg`, use `sink.InferOutputModuleFromPackage`.
 //
 // The `expectedOutputModuleType` should be the fully qualified expected Protobuf