Extra fixes

Author: Ahmad Bitar

docs/About/architecture.md

@@ -16,16 +16,16 @@ Each of the components in our architecture serves a specific purpose:
 
 ### Components of Taiko Stack
 
-- Taiko Prover: Part of the Taiko Client, generates proofs for the rollup [
-  ([Taiko documentation](https://github.com/taiko-eth/taiko))
+- Taiko Prover: Part of the Taiko Client, generates state transition proofs for the rollup
 
-- Taiko Driver: Part of the Taiko Client, handles the rollup ([Taiko documentation](https://github.com/taiko-eth/taiko))
+- Taiko Driver: Part of the Taiko Client, handles following the rollup
 
-- Taiko Proposer: Part of the Taiko Client, proposes the rollup ([Taiko documentation]( https://github.com/taiko-eth/taiko))
+- Taiko Proposer: Part of the Taiko Client, proposes new blocks to the rollup
 
 ## How is Surge different from the Taiko Stack
 
-We customized the implementation of the Taiko stack to remove token dependencies and provide a more secure and transparent experience.
+We customized the implementation of the Taiko stack to remove token dependencies and allowed utilizing Ether for use as a bond in block proposal.
+
 Performance improevements were made by swapping out the execution client from TaikoGeth to using the NMC [(NMC documentation) https://github.com/NethermindEth/nethermind].
 
 Time-Locked owner: We modified the multisig implementation to have a 45 day timelock to be compliant with Stage2 requirements set forth by L2Beat
@@ -36,9 +36,4 @@ Disabled pausing of protocol and peripheral contracts: The owner cannot pause th
 
 2/3 proof verifier as the sole proof verifier: We have three proof systems: SGX, SP1, Risc0. At least 2 of 3 of the provers must agree on a state transition for the transition to be accepted.
 
-## Goals
-
-- Be Stage 2 from launch
-- Provide Gigagas performance
-- Be maximally ethereum aligned by being based
-- Enable seamless composability with L1 and other rollups
+Disabled contestatino window as we only have one proving system and no other tiers. This makes Surge a ZkRollup and not an Optimistic one.

docs/intro.md

@@ -8,9 +8,9 @@ Surge is a maximally aligned, high-performance Ethereum rollup built on modified
 
 ## What is Surge?
 
-Surge is a novel high-performance, and censorship-resistant Ethereum rollup meant as a technical showcase that is designed to be:
+Surge is a high-performance, and censorship-resistant Ethereum rollup template meant as a technical showcase that is designed to be:
 
-- A based rollup with maximum Ethereum alignment
+- based with maximum Ethereum alignment
 - Stage 2 from launch
 - Provide Gigagas performance
 - Censorship resistant
@@ -22,12 +22,6 @@ Surge is a novel high-performance, and censorship-resistant Ethereum rollup mean
 
 Learn about the [Surge Architecture](./About/architecture)
 
-## Roadmap
-
-- Surge Testnet Alpha will be rolled out anchoring on Holesky
-- Surge Testnet will be rolled out anchoring on Hoodi
-- Surge Mainnet will be rolled out anchoring on Ethereum Mainnet
-
 ## Deploying your DApp on surge
 
 Follow our [DApp Deployment Guideline](./Guides/deploy-dapps/deploy-on-surge)
@@ -38,12 +32,12 @@ Follow the [Running Surge](./Guides/running-surge) guide
 
 ## Key Features
 
-- Stage 2 from Launch
 - Uses ETH as a gas token
 - Gigagas Per Second gas throughput
 - ZK proving system with multiple proving options
 - Cross-layer composability support (Coming soon)
 - Open source & Maximally Ethereum Aligned
+- Owner multisig have a 45 days timelock on any action to allow users ample time to exit with their funds.
 
 ## Goals