chore: fix some typos

Basics/deploy_injected/README.md

@@ -1,6 +1,6 @@
 1. If you don't have a browser wallet like **MetaMask** download and install one now. 
 
-2. Click the MetaMask icon in your browser. Sign in and choose the Ephemery test network. You might need to update your wallet's settings so that you can see **test networks**.  Alternatively, you can go to Remix's Deploy & Run transation module and in the ENVIRONMENT section select Ephemery.
+2. Click the MetaMask icon in your browser. Sign in and choose the Ephemery test network. You might need to update your wallet's settings so that you can see **test networks**.  Alternatively, you can go to Remix's Deploy & Run transaction module and in the ENVIRONMENT section select Ephemery.
 
 3. Getting test ETH for public test networks is often annoying.  Ephemery is a public network that is refreshed monthly, so getting test ETH should be painless.  Here is a link to some <a href="https://github.com/ephemery-testnet/ephemery-resources?tab=readme-ov-file#faucets" target="_blank">Ephemery faucets</a>.
 

Multisig-Tutorial/4-multisig-transactions/transactions.md

@@ -11,7 +11,7 @@ We have new modifiers in this iteration of the contract. Let's examine them one
 On line 28, we have a struct called `Transaction`. We store the struct members: `to`, `value`, `data`, `executed`, and `numConfirmations` in individual variables.
 
 ## Mapping of Confirmations
-On line 37, we have a mapping called `isConfirmed`. This mapping is used to keep track of the confirmations of each transaction. It maps the transaction's index to a mapping of an owner addresse to a boolean value. The boolean value indicates whether this owner has confirmed the transaction.
+On line 37, we have a mapping called `isConfirmed`. This mapping is used to keep track of the confirmations of each transaction. It maps the transaction's index to a mapping of an owner addresses to a boolean value. The boolean value indicates whether this owner has confirmed the transaction.
 
 ## Transactions Array
 On line 39, we have an array called `transactions`. The array is used to store all the transactions submitted to the multi-signature wallet.

SolidityBeginnerCourse/control-flow-loops/loops_test.sol

@@ -12,6 +12,6 @@ contract MyTest {
   function checkFunction() public {
     Assert.equal(foo.count(), 0, "Count should be initially 0.");
     foo.loop();
-    Assert.equal(foo.count(), 9, "Count should be 9 after executing the loop funcion.");
+    Assert.equal(foo.count(), 9, "Count should be 9 after executing the loop function.");
   }
 }

SolidityBeginnerCourse/transactions-sending-ether/sendingEther.md

@@ -25,7 +25,7 @@ An example of `send()` can be seen in the `SendEther` contract (line 41).
 * Forwards the maximum amount of gas, but this is adjustable
 
 An example of `call()` can be seen in the `SendEther` contract (line 48).
-`Call()` is currently recommended if you are transfering Ether.
+`Call()` is currently recommended if you are transferring Ether.
 
 The reason `transfer()` and `send()` were introduced was to guard against *reentry attacks* by limiting the forwarded gas to 2300, which would be insufficient to make a reentrant call that can modify storage.