Apply all suggestions from closed PRs (#3018)

Applied one-line suggestion from closed PRs from external contributors.

---------

Co-authored-by: AurelienFT <[email protected]>

Author: xgreenx

.github/workflows/scripts/verify_tag.sh

@@ -23,7 +23,7 @@ if [ -z "$MANIFEST" ]; then
     exit 1
 fi
 
-# strip preceeding 'v' if it exists on tag
+# strip preceding 'v' if it exists on tag
 REF=${REF/#v}
 TOML_VERSION=$(cat $MANIFEST | dasel -r toml 'workspace.package.version')
 

README.md

@@ -4,6 +4,7 @@
 [![crates.io](https://img.shields.io/crates/v/fuel-core?label=latest)](https://crates.io/crates/fuel-core)
 [![docs](https://docs.rs/fuel-core/badge.svg)](https://docs.rs/fuel-core/)
 [![discord](https://img.shields.io/badge/chat%20on-discord-orange?&logo=discord&logoColor=ffffff&color=7389D8&labelColor=6A7EC2)](https://discord.gg/xfpK4Pe)
+[![twitter](https://img.shields.io/twitter/follow/fuel_network)](https://x.com/fuel_network)
 
 Fuel client implementation.
 
@@ -23,7 +24,7 @@ Before pushing any changes or creating pull request please run `source ci_checks
 
 ## Building
 
-If you plan to use already pre-compiled binairies you can directly go to [Running a Ignition node](#running-a-ignition-node).
+If you plan to use already pre-compiled binaries you can directly go to [Running a Ignition node](#running-a-ignition-node).
 
 ### System Requirements
 

docs/architecture.md

@@ -13,7 +13,7 @@ about unrelated components, and refactors can easily control their blast radius.
 In a system of shared global traits between modules, any updates to an interface will cause breaking changes
 to the mocks and test harnesses for all consuming modules. This is less than ideal when these domain modules
 don't need to use the new changes. However, in a system where each domain controls its ports, adjusting an
-interface will only affect the port owner and the implementor.
+interface will only affect the port owner and the implementer.
 
 The implementation of "Ports" (aka adapters) referring to other domain modules, should reside in the main fuel-core
 crate. This way, domain modules should never need to take a dependency on each other. This helps to avoid circular

docs/developers/debugging.md

@@ -56,11 +56,11 @@ A key pair can be generated by running the utility binary `fuel-core-keygen`:
 cargo run --bin fuel-core-keygen new
 ```
 
-The resulting key pair printed to the console contains an address and secret. The `secret` can be provided to the `--keypair` argument when running the node.
+The resulting key pair printed to the console contains an address and a secret. The `secret` can be provided to the `--keypair` argument when running the node.
 
 The `--network` argument identifies the name of the network to join. The network name is used during peer discovery. For example, users can specify `--network beta-4` to join the Beta 4 network. Similarly, setting the environment variable `NETWORK="beta-4"` will produce the same result.
 
-For more information about client networking, see the Fuel guide on [running a node](https://docs-hub.vercel.app/guides/running-a-node/).
+For more information about client networking, see the Fuel guide on [running a node](https://docs-hub.vercel.app/docs/node-operator/#running-a-node/).
 
 ## Common Issues
 

docs/fee_calculations.md

@@ -9,7 +9,7 @@ to include an additional cost to op codes that write new data to storage or to
 transactions that add new contracts to the chain.
 
 There are a number of ways we might calculate this value; we have decided to go 
-with a simple calculatoin based on our target storage growth and working
+with a simple calculation based on our target storage growth and working
 backward from there.
 
 #### Pessimistic Estimate

tests/tests/tx/upgrade.rs

@@ -569,6 +569,6 @@ async fn state_transition_bytecode_should_be_queryable_by_its_root_and_version()
     );
     match state_transition_bytecode_by_root.bytecode {
         UploadedBytecode::Completed(bytecode) => assert_eq!(bytecode, WASM_BYTECODE),
-        _ => panic!("bytecode uploade incomplete"),
+        _ => panic!("bytecode uploaded incomplete"),
     };
 }