trilitech · timothymcmackin · Dec 19, 2024 · Jan 21, 2025 · Jan 27, 2025 · Jan 27, 2025
diff --git a/docs/architecture/governance/amendment-history.md b/docs/architecture/governance/amendment-history.md
@@ -5,7 +5,7 @@ last_update:
   date: 6 June 2024
 ---
 
-As presented in [Governance](/architecture/governance), the Tezos blockchain is constantly evolving, through new amendments.
+As presented in [Governance](/architecture/governance), the Tezos blockchain is constantly evolving through new amendments.
 
 These approved amendments form the history of the Tezos protocol:
 
@@ -231,7 +231,7 @@ For more information, see the blog post from [Nomadic Labs](https://research-dev
 Paris's main changes are:
 
 * [10-second block time](https://research-development.nomadic-labs.com/10-second-blocktime.html): Lower latency and faster finality on layer 1 without compromising decentralization or security.
-* [Data availability layer](https://research-development.nomadic-labs.com/paris-announcement.html#the-dal-activates-on-mainnet-boosting-smart-rollups-capacity): Boosting throughput and scalability of Smart Rollups.
+* [Data Availability Layer](https://research-development.nomadic-labs.com/paris-announcement.html#the-dal-activates-on-mainnet-boosting-smart-rollups-capacity): Boosting throughput and scalability of Smart Rollups.
 It enables Tezos Layer 1 to attest the publication of data living outside Layer 1 blocks, increasing by orders of magnitude the bandwidth of data attested by the Layer 1.
 * [Adaptive issuance, staking, and adaptive slashing](https://research-development.nomadic-labs.com/adaptive-issuance-paris.html): A major overhaul of Tezos Proof-of-Stake, adapting the economics of tez to fit better with real-world usage, and to increase the chain security. The proposed mechanism ties the protocol’s regular issuance of tez to the ratio of staked tez over the total supply, in order to nudge the staked fund ratio towards a protocol-defined target.
 * [Further proof-of-stake refinements](https://research-development.nomadic-labs.com/paris-announcement.html#further-proof-of-stake-refinements): Simplified computation and faster updates of consensus rights.

diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md
@@ -46,7 +46,7 @@ Smart Rollups are limited to information from these sources:
 
 - The Smart Rollup inbox, which contains messages from layer 1 to all rollups
 - The reveal data channel, which allows Smart Rollups to request information from outside sources
-- The [Data availability layer](/architecture/data-availability-layer)
+- The [Data Availability Layer](/architecture/data-availability-layer)
 
 These are the only sources of information that rollups can use.
 In particular, Smart Rollup nodes cannot communicate directly with each other; they do not have a peer-to-peer communication channel like layer 1 nodes.

diff --git a/docs/developing/information/block-explorers.md b/docs/developing/information/block-explorers.md
@@ -14,7 +14,7 @@ You can think of it as a window into the blockchain world, allowing you to obser
 
 Cryptocurrency users and developers use such a tool to view the status of past or present transactions.
 
-Some of the most basic information available on blockchain explorers includes (but are not limited to):
+Some of the most basic information available on blockchain explorers includes (but is not limited to):
 
 * **Block feed**: This allows you to view all the confirmed and pending blocks on the blockchain.
 * **Transaction feed**: The transaction feed displays all the most recent and pending transactions.

diff --git a/docs/developing/testnets.md b/docs/developing/testnets.md
@@ -108,7 +108,7 @@ curl https://teztnets.com/teztnets.json | jq '.[] | select(.human_name == "Weekl
 You can use the response to set environment variables like the RPC endpoint, as in this code:
 
 ```bash
-curl https://teztnets.xyz/teztnets.json | jq '.[] | select(.human_name == "Weeklynet")' > weeklynet.json
+curl https://teztnets.com/teztnets.json | jq '.[] | select(.human_name == "Weeklynet")' > weeklynet.json
 export WEEKLYNET_ENDPOINT=$(jq -r .rpc_url weeklynet.json)
 export WEEKLYNET_COMMIT=$(jq -r .git_ref weeklynet.json)
 export DOCKER_IMAGE=$(jq -r .docker_build weeklynet.json)

diff --git a/docs/tutorials.mdx b/docs/tutorials.mdx
@@ -137,7 +137,7 @@ These tutorials are intended for developers who are familiar with Tezos and want
   title="Implement a file archive with the DAL"
   emoji="🗃️"
   href="/tutorials/build-files-archive-with-dal"
-  description="Learn how to build a file archive with a Smart Rollup and the data availability layer"
+  description="Learn how to build a file archive with a Smart Rollup and the Data Availability Layer"
   link="Start tutorial"
 />
 

diff --git a/docs/tutorials/smart-rollup.md b/docs/tutorials/smart-rollup.md
@@ -130,15 +130,15 @@ TODO Could we install some of the tools in the docker container instead of makin
 - AR (macOS only)
 
    To compile to WebAssembly on macOS, you need to use the LLVM archiver.
-   If you've used Homebrew to install LLVM, you can configure it to use the archiver by running this command:
+   If you used Homebrew to install LLVM, you can configure it to use the archiver by running this command:
 
    ```bash
    export AR="$(brew --prefix llvm)/bin/llvm-ar"
    ```
 
 - WebAssembly Toolkit
 
-   The the [WebAssembly Toolkit (`wabt`)](https://github.com/WebAssembly/wabt) provides tooling for reducing (or _stripping_) the size of WebAssembly binaries (with the `wasm-strip` command) and conversion utilities between the textual and binary representations of WebAssembly (including the `wat2wasm` and `wasm2wat` commands).
+   The [WebAssembly Toolkit (`wabt`)](https://github.com/WebAssembly/wabt) provides tooling for reducing (or _stripping_) the size of WebAssembly binaries (with the `wasm-strip` command) and conversion utilities between the textual and binary representations of WebAssembly (including the `wat2wasm` and `wasm2wat` commands).
 
    Most distributions ship a `wabt` package, which you can install with the appropriate command for your operating system:
 
@@ -168,7 +168,7 @@ TODO Could we install some of the tools in the docker container instead of makin
 
    To verify that `wabt` is installed, run the command `wasm-strip --version` and verify that the version is at least 1.0.31.
    If not, you can download this version directly and extract its files: https://github.com/WebAssembly/wabt/releases/tag/1.0.31.
-   Then, whenever you have to use `wasm-strip`, you can use `.<path_to_wabt_1.0.31>/bin/wasm-strip` instead.
+   Then, whenever you have to use `wasm-strip`, you can use `<path_to_wabt_1.0.31>/bin/wasm-strip` instead.
 
 ## Tutorial application
 

diff --git a/docs/unity/connecting-accounts.md b/docs/unity/connecting-accounts.md
@@ -48,7 +48,7 @@ The SDK supports three types of wallets:
 ## Connecting to Beacon wallets
 
 Unity applications can connect to Beacon wallets by showing a QR code that the user scans with a wallet app or by opening that app directly through the Beacon protocol.
-For an example of this method, see [Quickstart](./quickstart).
+For an example of this method, see [Quickstart](/unity/quickstart).
 
 This method for connecting follows these general steps:
 

diff --git a/docs/unity/managing-tokens.md b/docs/unity/managing-tokens.md
@@ -31,7 +31,7 @@ FA2 tokens can be fungible tokens or non-fungible tokens, which makes the standa
 
 To create and work with FA2 tokens you must deploy an FA2-compatible smart contract.
 For examples of FA2 contracts, see [Sample smart contracts](/smart-contracts/samples).
-You can also use the tutorial [Create a fungible token with the SmartPy FA2 library](/smart-contracts/samples) to walk through the process of creating, customizing, and deploying an FA2 contract.
+You can also use the tutorial [Create a fungible token with the SmartPy FA2 library](/tutorials/smartpy-fa2-fungible) to walk through the process of creating, customizing, and deploying an FA2 contract.
 
 :::note