fixing more broken links

Author: sbvegan

pages/builders/chain-operators/features/alt-da-mode.mdx

@@ -44,7 +44,7 @@ You should use at least the following compatible op\* versions when running your
   *   Celestia's docs on how to run the [Celestia DA server](https://github.com/celestiaorg/op-plasma-celestia/blob/main/README.md)
   *   EigenDA's docs on how to run the [EigenDA DA server](https://github.com/Layr-Labs/op-plasma-eigenda/blob/main/README.md)
   *   Avail's docs on how to run the [AvailDA DA Server](https://docs.availproject.org/docs/build-with-avail/Optimium/op-stack/op-stack#setup-avail-da-server)
-  *   0gDA's docs on how to run the [0gDA DA Server](https://github.com/0glabs/0g-da-op-plasma/blob/op0g/README.md)
+  *   0gDA's docs on how to run the [0gDA DA Server](https://github.com/0glabs/0g-da-op-plasma)
   *   Near DA's docs on how to run the [Near DA Server](https://github.com/Nuffle-Labs/data-availability/blob/84b484de98f58a91bf12c8abe8df27f5e753f63a/docs/OP-Alt-DA.md)
 
   ### Configure Your `op-node`
@@ -224,6 +224,6 @@ After making these changes, your system should be properly configured to use the
 
 ## Next Steps
 
-*   Additional questions? See the FAQ section in the [Alt-DA Mode Explainer](/stack/bet/alt-da-mode#faqs).
+*   Additional questions? See the FAQ section in the [Alt-DA Mode Explainer](/stack/beta-features/alt-da-mode#faqs).
 *   For more detailed info on Alt-DA Mode, see the [specs](https://specs.optimism.io/experimental/alt-da.html).
 *   If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions).

pages/builders/notices/fp-changes.mdx

@@ -17,7 +17,7 @@ If you experience difficulty at any stage of this process, please reach out to [
 
 **ALL** withdrawals that are not finalized before the Fault Proofs upgrade executes will need to be reproven after the upgrade is complete.
 
-  *   Reproving simply requires that you execute the [withdrawal proving flow](https://docs.optimism.io/stack/transactions/withdrawal-flow) again.
+  *   Reproving simply requires that you execute the [withdrawal proving flow](/stack/transactions/withdrawal-flow) again.
   *   Withdrawals prior to the Fault Proofs upgrade must wait a 7-day challenge period before finalization. As a result, any withdrawal initiated less than 7 days before the upgrade cannot be finalized before the upgrade is executed. You may want to consider waiting until after the upgrade is complete to begin a withdrawal during this 7-day window.
 </Callout>
 

pages/stack/transactions/withdrawal-flow.mdx

@@ -95,11 +95,6 @@ The Chugsplash Proxy operates differently than standard proxies. During a withdr
 *   **No Cause for Concern**: Although Etherscan highlights these reverts, they do not affect the final success of the transaction.
 *   **User Assurance**: If you encounter these reverts during a withdrawal transaction, rest assured that the withdrawal will still finalize as expected.
 
-For more information about the withdrawal process and how it works on Optimism, refer to the following resources:
-
-*   [Smart Contracts Overview](https://docs.optimism.io/stack/rollup/smart-contracts)
-*   [Withdrawal Flow](https://docs.optimism.io/stack/transactions/withdrawal-flow#withdrawal-initiating-transaction)
-
 ### Offchain processing
 
 1.  A user calls the SDK's [`CrossDomainMessenger.finalizeMessage()`](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/packages/sdk/src/cross-chain-messenger.ts#L1473-L1493) with the hash of the L1 message.