Merge pull request #473 from ProvableHQ/fix/installation-dead-link

d0cd · web-flow · commit e916349c6209 · 2025-04-03T08:46:16.000-07:00
Fixing dead links
diff --git a/archive/advanced/dive-into-avm/00_overview.md b/archive/advanced/dive-into-avm/00_overview.md
@@ -18,7 +18,7 @@ It was formalised and implemented in the Aleo Network as [ARC-0002](https://gith
 
 ## **AVM’s Architecture and Design**
 
-The AVM is virtual machine that operates on a last-in, first-out (LIFO) principle where data is stacked and the most recently added data is the first to be accessed or removed. This design is conducive to the execution of complex arithmetic circuits that are essential for the privacy-preserving features of Aleo. The AVM's architecture is designed to support the execution of private applications by leveraging zero-knowledge proofs. It uses Leo (high-level programming language), which compiles down into an intermediate representation known as AVM opcodes. These opcodes are then used to construct the R1CS, which are essential for generating zero-knowledge proofs. Check the full list [here](https://docs.leo-lang.org/aleo/opcodes/)
+The AVM is virtual machine that operates on a last-in, first-out (LIFO) principle where data is stacked and the most recently added data is the first to be accessed or removed. This design is conducive to the execution of complex arithmetic circuits that are essential for the privacy-preserving features of Aleo. The AVM's architecture is designed to support the execution of private applications by leveraging zero-knowledge proofs. It uses Leo (high-level programming language), which compiles down into an intermediate representation known as AVM opcodes. These opcodes are then used to construct the R1CS, which are essential for generating zero-knowledge proofs. Check the full list [here](https://developer.aleo.org/guides/aleo/opcodes)
 
 The AVM architecture can be broken down into several key components and characteristics:
 
diff --git a/archive/create-aleo-app/02_create_aleo_app_full.md b/archive/create-aleo-app/02_create_aleo_app_full.md
@@ -277,7 +277,7 @@ Congratulations on becoming a Leo contributor! 🎉
 
 2. You also installed [Leo](https://docs.leo-lang.org/leo/), our statically-typed programming language built for writing private applications.
 
-3. You executed `helloworld` using WASM, which called on in-browser resources to use [snarkVM](https://docs.leo-lang.org/aleo/), the data execution layer. It is used to compile Leo programs and execute them locally off-chain. All Leo programs eventually become Aleo instructions via Aleo’s compiler during the execution phase of snarkVM. 
+3. You executed `helloworld` using WASM, which called on in-browser resources to use [snarkVM](https://github.com/ProvableHQ/snarkVM), the data execution layer. It is used to compile Leo programs and execute them locally off-chain. All Leo programs eventually become Aleo instructions via Aleo’s compiler during the execution phase of snarkVM. 
 
 4. You also executed `helloworld` locally in your terminal using `leo execute`, which similarly uses local computational resources to compile your Leo program using snarkVM.
 
diff --git a/archive/src/learn/zkcloud/snarkos_build_guide.md b/archive/src/learn/zkcloud/snarkos_build_guide.md
@@ -184,4 +184,4 @@ OPTIONS:
 2. Sign a message with your private key using `snarkos account sign --raw -m "Message" --private-key-file=<PRIVATE_KEY_FILE>`
 3. Verify your signature with `snarkos account verify --raw -m "Message" -s sign1SignatureHere -a aleo1YourAccountAddress`
 
-Note, using the `--raw` flag with the command will sign plaintext messages as bytes rather than [Aleo](https://docs.leo-lang.org/aleo/language#data-types-and-values) values such as `1u8` or `100field`.
+Note, using the `--raw` flag with the command will sign plaintext messages as bytes rather than [Aleo](https://docs.leo-lang.org/language/data_types) values such as `1u8` or `100field`.
diff --git a/archive/testnet/getting_started/04_developer_toolkit.md b/archive/testnet/getting_started/04_developer_toolkit.md
@@ -139,10 +139,10 @@ This section refers to the guide created by GitHub [here](https://docs.github.co
 
 Check out the following resources:
 
-- [Our developer docs](https://docs.leo-lang.org/getting_started/)
+- [Our developer docs](https://docs.leo-lang.org/getting_started/installation)
 - See the SDK in action at [provable.tools](https://www.provable.tools/)
 - Play around with Leo in the browser with [Leo Playground](https://play.leo-lang.org/)
-- Learn Leo syntax, functions, and best practices with the [Leo's language guide](https://docs.leo-lang.org/leo/language)
+- Learn Leo syntax, functions, and best practices with the [Leo's language guide](https://docs.leo-lang.org/language/overview)
 - Deploy and Execute Leo applications on-chain with our [Deploy and Execute Demo](https://docs.leo-lang.org/testnet/getting_started/deploy_execute_demo)
 <!-- markdown-link-check-disable -->
 - See Aleo's testnet live and other Leo developer's applications via an explorer such as [Haruka's Program Registry](https://explorer.hamp.app/programs) or [aleo.network](https://www.aleo.network/).
diff --git a/documentation/guides/02_debuggin.md b/documentation/guides/02_debuggin.md
@@ -6,7 +6,7 @@ sidebar_label: Debuggin' Out
 
 `leo debug` is a powerful tool that developers can use to interactively step through executions and track down bugs. In this workshop, we'll use the Leo debugger to explore and gain a deeper understanding of a variety of programs. You will also build up the skills to adeptly use the debugger in your development work.
 
-**This tutorial assumes that you are already familiar with Leo. If you'd like a refresher, see the [Developer Docs](https://docs.leo-lang.org/getting_started)**.
+**This tutorial assumes that you are already familiar with Leo. If you'd like a refresher, see the [Developer Docs](https://docs.leo-lang.org/getting_started/installation)**.
 
 We're always looking to improve Leo's developer experience. If you have any feedback, please feel free to [file](https://github.com/ProvableHQ/leo/issues/new/choose) an issue!
 
diff --git a/documentation/leo_by_example/01_auction.md b/documentation/leo_by_example/01_auction.md
@@ -36,7 +36,7 @@ The auction is conducted in a series of stages.
 
 ## How to Run
 
-Follow the [Leo Installation Instructions](https://docs.leo-lang.org/leo/installation).
+Follow the [Leo Installation Instructions](https://docs.leo-lang.org/getting_started/installation).
 
 This auction program can be run using the following bash script. Locally, it will execute Leo program functions to conduct, bid, and close a three party auction.
 
diff --git a/documentation/leo_by_example/02_basic_bank.md b/documentation/leo_by_example/02_basic_bank.md
@@ -39,7 +39,7 @@ There are, of course, ways to write a version of this application without these
 
 ## How to Run
 
-Follow the [Leo Installation Instructions](https://docs.leo-lang.org/leo/installation).
+Follow the [Leo Installation Instructions](https://docs.leo-lang.org/getting_started/installation).
 
 This basic bank program can be run using the following bash script. Locally, it will execute Leo program functions to issue, deposit, and withdraw tokens between a bank and a user.
 
diff --git a/documentation/leo_by_example/03_vote.md b/documentation/leo_by_example/03_vote.md
@@ -20,7 +20,7 @@ Proposal information and voting results are revealed using the public `mapping`
 
 ## How to Run
 
-Follow the [Leo Installation Instructions](https://docs.leo-lang.org/leo/installation).
+Follow the [Leo Installation Instructions](https://docs.leo-lang.org/getting_started/installation).
 
 This vote program can be run using the following bash script. Locally, it will execute Leo program functions to create proposals, create tickets, and make votes.
 
diff --git a/documentation/leo_by_example/04_token.md b/documentation/leo_by_example/04_token.md
@@ -11,7 +11,7 @@ A transparent & shielded custom token in Leo.
 
 ## How to Run
 
-Follow the [Leo Installation Instructions](https://docs.leo-lang.org/leo/installation).
+Follow the [Leo Installation Instructions](https://docs.leo-lang.org/getting_started/installation).
 
 This token program can be run using the following bash script. Locally, it will execute Leo program functions to mint and transfer tokens publicly and privately.
 
diff --git a/documentation/leo_by_example/05_tictactoe.md b/documentation/leo_by_example/05_tictactoe.md
@@ -30,7 +30,7 @@ The game board is represented by a struct called `Board`, which contains three `
 
 ## How to Run
 
-Follow the [Leo Installation Instructions](https://docs.leo-lang.org/leo/installation).
+Follow the [Leo Installation Instructions](https://docs.leo-lang.org/getting_started/installation).
 
 This tictactoe program can be run using the following bash script. Locally, it will execute Leo program functions to create and play a game of Tic Tac Toe.
 
diff --git a/documentation/leo_by_example/06_battleship.md b/documentation/leo_by_example/06_battleship.md
@@ -47,7 +47,7 @@ This application was translated into Leo from the [zk-battleship](https://github
 
 ## How to Run
 
-Follow the [Leo Installation Instructions](https://docs.leo-lang.org/leo/installation).
+Follow the [Leo Installation Instructions](https://docs.leo-lang.org/getting_started/installation).
 
 This battleship program can be run using the following bash script. Locally, it will execute Leo program functions to create the board, place ships, and play a game of battleship.
 
diff --git a/documentation/sdk/create-leo-app/01_create_leo_app.md b/documentation/sdk/create-leo-app/01_create_leo_app.md
@@ -207,7 +207,7 @@ git push -u origin main
 
 2. You also installed [Leo](https://docs.leo-lang.org/leo/), our statically-typed programming language built for writing private applications. Using Leo, you can write, build, compile, and execute Leo programs locally.
 
-3. We provided the `helloworld` Leo program already pre-compiled into Aleo instructions and then executed it locally using WASM + web workers, which was an abstraction on snarkVM’s capabilities. [snarkVM](https://docs.leo-lang.org/aleo/) is the data execution layer. It is used to compile Leo programs and execute them locally off-chain. All Leo programs eventually become Aleo instructions via Aleo’s compiler during the execution phase of snarkVM. 
+3. We provided the `helloworld` Leo program already pre-compiled into Aleo instructions and then executed it locally using WASM + web workers, which was an abstraction on snarkVM’s capabilities. [snarkVM](https://github.com/ProvableHQ/snarkVM) is the data execution layer. It is used to compile Leo programs and execute them locally off-chain. All Leo programs eventually become Aleo instructions via Aleo’s compiler during the execution phase of snarkVM. 
 
 4. Similarly, we deployed the `helloworld` program, again using the WASM + web workers abstraction layer but you can also deploy programs on-chain using [snarkOS](https://docs.leo-lang.org/testnet/getting_started/deploy_execute/#deploy), the data availability layer or blockchain / distributed ledger.
 
diff --git a/documentation/sdk/typescript/00_sdk_overview.md b/documentation/sdk/typescript/00_sdk_overview.md
@@ -130,9 +130,9 @@ Aleo programs provide the ability for users to make any input or output of a pro
 was run correctly. Keeping program inputs and outputs private allows developers to build privacy into their applications.
 
 Zero-Knowledge programs are written in one of two languages:
-1. [Leo](https://docs.leo-lang.org/leo/language): A high level, developer friendly language for developing
+1. [Leo](https://docs.leo-lang.org/language/overview): A high level, developer friendly language for developing
    zero knowledge programs.
-2. [Aleo Instructions](https://docs.leo-lang.org/aleo/): A low level language that provides developers fine
+2. [Aleo Instructions](https://developer.aleo.org/guides/aleo/aleo): A low level language that provides developers fine
    grained control over the execution flow of zero knowledge programs. Leo programs are compiled into Aleo Instructions
    under the hood.
 
@@ -166,7 +166,7 @@ function hello:
 The SDK provides the ability to execute Aleo Instructions programs %100 client-side within the browser.
 
 The `ProgramManager` object encapsulates the functionality for executing programs and making zero knowledge proofs about
-them. Under the hood it uses cryptographic code compiled from [snarkVM](https://docs.leo-lang.org/aleo) into WebAssembly.
+them. Under the hood it uses cryptographic code compiled from [snarkVM](https://github.com/ProvableHQ/snarkVM) into WebAssembly.
 JavaScript bindings to this WebAssembly code allows execution of programs in zero knowledge fully within the browser
 without requiring any external communication with the internet. Users interested in lower level details on how this is
 achieved can visit the [aleo-wasm](https://github.com/ProvableHQ/sdk/tree/testnet3/wasm) crate.
diff --git a/documentation/sdk/wasm/00_wasm_installation.md b/documentation/sdk/wasm/00_wasm_installation.md
@@ -32,7 +32,7 @@ Functionality exposed by this crate includes:
 * Aleo primitives such as `Records`, `Programs`, and `Transactions` and their associated helper methods
 * A `ProgramManager` object that contains methods for authoring, deploying, and interacting with Aleo programs
 
-More information on these concepts can be found at the [Aleo Developer Hub](https://docs.leo-lang.org/concepts).
+More information on these concepts can be found at the [Aleo Developer Hub](https://developer.aleo.org/concepts/fundamentals/accounts/).
 
 <!-- markdown-link-check-disable -->
 ## Usage
