cli: update add bridge command instructions (#17)

Author: aashutoshrathi

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

@@ -1,11 +1,11 @@
-# `add-bridge` [Deploy a bridge and register with AppInbox]
+# `add bridge` [Deploy a bridge and register with AppInbox]
 
-The `add-bridge` command is used to set the Bridge contract in your AppInbox on-chain. This is helpful as the AppInbox only accepts ticket requests for L1 to L2 bridging from the known Bridge contract. 
+The `add bridge` command is used to set the Bridge contract in your AppInbox on-chain. This is helpful as the AppInbox only accepts ticket requests for L1 to L2 bridging from the known Bridge contract. 
 
 ## Usage
 
 ```bash
-npx @stackr/cli@latest add-bridge
+npx @stackr/cli@latest add bridge
 ```
 
 ## Output

docs/pages/build/cli/introduction.mdx

@@ -26,10 +26,10 @@ USAGE
   $ stackr [COMMAND]
 
 COMMANDS
-  add-bridge  Set the bridge address to the AppInbox contract of your MRU
+  init      Init an MRU from templates
   compile   Compile yours Stackr State Machines to portable WASM modules.
   deploy    Deploy your MRU to Vulcan
+  add       Sets the bridge or hook address to the AppInbox contract of your MRU
   help      Display help for stackr.
-  init      Init an MRU from templates
   register  Register your MicroRollup with Stackr
 ```

docs/pages/build/plugins/bridging.mdx

@@ -69,7 +69,7 @@ Next up, you need to update the `AppInbox` to know which `Bridge` contract to ac
 
 Run the CLI command:
 ```bash [terminal]
-npx @stackr/cli add-bridge
+npx @stackr/cli add bridge
 ```
 
 You'll be prompted with the bridge address: