Fix typos and capitalization errors

docs/.vitepress/config.mts

@@ -49,7 +49,7 @@ export default defineConfig({
 
     socialLinks: [
       { icon: "github", link: "https://github.com/astriaorg" },
-      { icon: "twitter", link: "https://twitter.com/AstriaOrg" },
+      { icon: "x", link: "https://x.com/AstriaOrg" },
     ],
   },
   vite: {

docs/developer/astria-go/astria-go-config.md

@@ -1,6 +1,6 @@
 # `astria-go` Configuration
 
-Config for the `astria-go` CLI can be broken out into the following catagories:
+Config for the `astria-go` CLI can be broken out into the following categories:
 
 - [CLI TUI/devrunner](#tui-config)
 - [Services](#service-config) and [networks](#devrunner-networks-config) run by

docs/developer/deployment-charts.md

@@ -45,7 +45,7 @@ just wait-for-ingress-controller
 just deploy astria-local
 
 # Deploys a geth rollup chain + faucet + blockscout + ingress
-# w/ defaults running against local network, along with a bridge withdawer.
+# w/ defaults running against local network, along with a bridge withdrawer.
 # NOTE - default values can be found in `helm/rollup/values.yaml`
 just deploy rollup
 

docs/overview/bridging.md

@@ -8,7 +8,7 @@ With the Astria Sequencing Layer, transaction data touches three different
 chains: the sequencer chain, the data availability chain, and the rollup chain.
 Each of these requires a fee payment for DoS prevention. If each chain requires
 a different token for fee payment, this causes a poor UX. Many rollups built on
-Ethereum allows for bridged ETH to be used to pay fees, alleviating UX concerns,
+Ethereum allow for bridged ETH to be used to pay fees, alleviating UX concerns,
 as users only need to obtain one, widely-available token (ETH).
 
 We can do something similar with the sequencer network. Assuming the data
@@ -26,10 +26,10 @@ ability to derive deposit transactions from the sequencer or DA network. In
 general, rollup deposits work as follows:
 
 On the L1, tokens are transferred to some escrow account/contract.
-the rollup consensus node, which derives the L2 transactions from L1 data, sees
+The rollup consensus node, which derives the L2 transactions from L1 data, sees
 these deposits, and includes a corresponding “deposit” transaction in the next
 L2 block, which is a distinct transaction type.
-the L2 node executes these deposit transactions, minting synthetic funds on the
+The L2 node executes these deposit transactions, minting synthetic funds on the
 L2 to the respective account.
 A rollup on Astria would have to implement something like this to bridge from
 the sequencer/DA to it.