chore: fix some typos in comment

Signed-off-by: pinglanlu <pinglanlu@outlook.com>

Author: pinglanlu

docs/pages/build/cli/add-bridge.mdx

@@ -38,5 +38,5 @@ Enter the address and hit enter.
 Output if it passes all the checks:
 
 ```bash [terminal]
-✔ 🌉 Succesfully added bridge contract to AppInbox
+✔ 🌉 Successfully added bridge contract to AppInbox
 ```

docs/pages/build/cli/verify.mdx

@@ -24,7 +24,7 @@ EXAMPLES
 $ npx @stackr/cli@latest verify
 ```
 
-The AppInbox addresss will be read from the `deployment.json` file otherwise error would be thrown.
+The AppInbox address will be read from the `deployment.json` file otherwise error would be thrown.
 
 Output if it passes all the checks:
 ```bash [terminal]

docs/pages/build/framework/state-machine/genesis-state.mdx

@@ -1,6 +1,6 @@
 # Genesis State [The state at which the state machine starts]
 
-The genesis state is the initial state of the state machine. This state is serialized and stored as the begininng of the rollup inside the `AppInbox` contract.
+The genesis state is the initial state of the state machine. This state is serialized and stored as the beginning of the rollup inside the `AppInbox` contract.
 
 The genesis state is stored in a `genesis-state.json` file in the root of the project. This file is used to initialize the state machine with the initial state. The CLI also uses this file to register the rollup with the `AppInbox` contract.
 

docs/pages/build/guides/tutorials/counter.mdx

@@ -268,7 +268,7 @@ export { stackrConfig };
 
 ## Define the Rollup
 
-Once we are done with the state machine, we can define the rollup using the `MicroRollup` class from the SDK which includes all the neccessary components to run the state machine.
+Once we are done with the state machine, we can define the rollup using the `MicroRollup` class from the SDK which includes all the necessary components to run the state machine.
 
 The rollup takes 2 parameters: