docs: fixed broken and old links

README.md

@@ -24,7 +24,7 @@ The most recent documentation can be found here:
 ZKsync Era is distributed under the terms of either
 
 - Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or <http://www.apache.org/licenses/LICENSE-2.0>)
-- MIT license ([LICENSE-MIT](LICENSE-MIT) or <https://opensource.org/blog/license/mit/>)
+- MIT license ([LICENSE-MIT](LICENSE-MIT) or <https://opensource.org/license/mit>)
 
 at your option.
 
@@ -33,8 +33,8 @@ at your option.
 - [Website](https://zksync.io/)
 - [GitHub](https://github.com/matter-labs)
 - [ZK Credo](https://github.com/zksync/credo)
-- [Twitter](https://twitter.com/zksync)
-- [Twitter for Developers](https://twitter.com/zkSyncDevs)
+- [Twitter](https://x.com/zksync)
+- [Twitter for Developers](https://x.com/zkSyncDevs)
 - [Discord](https://join.zksync.dev/)
 - [Mirror](https://zksync.mirror.xyz/)
 - [Youtube](https://www.youtube.com/@zkSync-era)

docs/src/guides/development.md

@@ -245,7 +245,7 @@ You must provide:
 - In case of Etherscan verification, you must also provide:
   - Your Etherscan API key, either by passing it as an argument or setting `ETHERSCAN_API_KEY`
 
-For more information check [Foundry's documentation](https://book.getfoundry.sh/reference/forge/forge-verify-contract).
+For more information check [Foundry's documentation](https://getfoundry.sh/forge/reference/verify-contract/).
 
 ## How to generate the `genesis.yaml` file
 

docs/src/guides/setup-dev.md

@@ -240,7 +240,7 @@ Go to the zksync folder and run `nix develop`. After it finishes, you are in a s
 ## Foundry ZKsync
 
 ZKSync depends on Foundry ZKsync (which is is a specialized fork of Foundry, tailored for ZKsync). Please follow this
-[installation guide](https://foundry-book.zksync.io/getting-started/installation) to get started with Foundry ZKsync.
+[installation guide](https://foundry-book.zksync.io/introduction/installation/) to get started with Foundry ZKsync.
 
 Foundry ZKsync can also be used for deploying smart contracts. For commands related to deployment, you can pass flags
 for Foundry integration.

docs/src/specs/blocks_batches.md

@@ -40,9 +40,9 @@ as the container for executing the program and handling the transactions within
 Most blockchains use factors like time and gas usage to determine when a block should be closed or sealed. However, our
 case is a bit more complex because we also need to consider prover capacity and limits related to publishing to L1.
 
-The decision of when to seal the block is handled by the code in the [conditional_sealer][conditional_sealer] module. It
+The decision of when to seal the block is handled by the code in the [conditional_sealer](https://github.com/matter-labs/zksync-era/blob/c577d867cc3081b4ce12c59351e0a32c2fdfe241/core/node/state_keeper/src/seal_criteria/conditional_sealer.rs) module. It
 maintains a list of `SealCriterion` and at the time of writing this article, [we have 9 reasons to seal the
-block][reasons_for_sealing], which include:
+block](https://github.com/matter-labs/zksync-era/blob/c577d867cc3081b4ce12c59351e0a32c2fdfe241/core/node/state_keeper/src/seal_criteria/mod.rs), which include:
 
 - Transaction slots limit (currently set to 750 transactions in `StateKeeper`'s config - `transaction_slots`).
 - Gas limit (currently set to `MAX_L2_TX_GAS_LIMIT` = 80M).

docs/src/specs/prover/overview.md

@@ -1,7 +1,7 @@
 # Intro to ZKsync’s ZK
 
 This page is specific to our cryptography. For a general introduction, please read:
-[https://docs.zksync.io/build/developer-reference/rollups.html](https://docs.zksync.io/build/developer-reference/rollups.html)
+[https://docs.zksync.io/zksync-protocol/rollup](https://docs.zksync.io/zksync-protocol/rollup)
 
 As a ZK rollup, we want everything to be verified by cryptography and secured by Ethereum. The power of ZK allows for
 transaction compression, reducing fees for users while inheriting the same security.
@@ -58,6 +58,6 @@ is described in more detail in
 The process of turning code into constraints is called arithmetization. Our arithmetization is based on a variation of
 “Plonk”. The details are abstracted away from the circuits, but if you’d like to learn more, read about Plonk in
 [Vitalik’s blog](https://vitalik.eth.limo/general/2019/09/22/plonk.html) or the
-[Plonky2 paper](https://github.com/mir-protocol/plonky2/blob/main/plonky2/plonky2.pdf).
+[Plonky2 paper](https://github.com/0xPolygonZero/plonky2/blob/5d9da5a65bbcba2c66eb29c035090eb2e9ccb05f/plonky2/plonky2.pdf).
 
 More details of our proving system can be found in the [Redshift Paper](https://eprint.iacr.org/2019/1400.pdf).

prover/docs/src/00_intro.md

@@ -36,7 +36,7 @@ We'll cover how the components work further in documentation.
 [cp]: https://github.com/matter-labs/zksync-era/tree/main/prover/crates/bin/circuit_prover
 [pc]: https://github.com/matter-labs/zksync-era/tree/main/prover/crates/bin/proof_fri_compressor
 [pdh]: https://github.com/matter-labs/zksync-era/tree/main/core/node/proof_data_handler
-[pjm]: https://github.com/matter-labs/zksync-era/tree/main/prover/crates/bin/prover-job-monitor
+[pjm]: https://github.com/matter-labs/zksync-era/tree/main/prover/crates/bin/prover_job_monitor
 [vkg]: https://github.com/matter-labs/zksync-era/tree/main/prover/crates/bin/vk_setup_data_generator_server_fri
 [pcli]: https://github.com/matter-labs/zksync-era/tree/main/prover/crates/bin/prover_cli
 [mc]: https://github.com/matter-labs/zksync-era/tree/main/core/node/metadata_calculator