Move links to octez.tezos.com/docs

Author: timothymcmackin

docs/architecture.md

@@ -38,7 +38,7 @@ Nodes reach consensus on the next block before adding it to the chain.
 
 As shown in the diagram, the data inside a Tezos block includes the hash of the previous block in the chain and many operations, such as transactions that transfer tez or call smart contracts.
 Blocks also include operations that are necessary for the management of the chain, including nodes' attestations that blocks are valid, called _consensus operations_, and votes on changes to the protocol, called _voting operations_.
-For more information on the operations that can be included in blocks, see [Blocks and operations](https://tezos.gitlab.io/alpha/blocks_ops.html) in the Octez documentation.
+For more information on the operations that can be included in blocks, see [Blocks and operations](https://octez.tezos.com/docs/active/blocks_ops.html) in the Octez documentation.
 
 ### Tezos clients and servers
 

docs/architecture/bakers.md

@@ -87,6 +87,6 @@ To start delegating and staking, use the app at https://stake.tezos.com.
 
 To start baking, use our [tutorial for bakers](/tutorials/join-dal-baker).
 
-For more information about the different options to participate to the Tezos network (baking, staking, or delegating), see [Running Octez](https://tezos.gitlab.io/introduction/howtorun.html) in the Octez documentation.
+For more information about the different options to participate to the Tezos network (baking, staking, or delegating), see [Running Octez](https://octez.tezos.com/docs/introduction/howtorun.html) in the Octez documentation.
 
 To learn more about baking and the related concepts, see [Node and Baking](https://opentezos.com/node-baking/baking/introduction/) on opentezos.com.

docs/architecture/data-availability-layer.md

@@ -14,7 +14,7 @@ For a tutorial on how to use the DAL, see [Implement a file archive with the DAL
 
 The DAL depends on individual people running nodes, just like Tezos layer 1.
 
-- If you are already a Tezos baker, you can add a DAL node to your setup with the instructions in [Running a DAL attester node](https://tezos.gitlab.io/shell/dal_run.html).
+- If you are already a Tezos baker, you can add a DAL node to your setup with the instructions in [Running a DAL attester node](https://octez.tezos.com/docs/shell/dal_run.html).
 - For step-by-step instructions on running a DAL node, accessible to anyone, see [Join the DAL as a baker in 5 steps](/tutorials/join-dal-baker).
 
 ## How the DAL works
@@ -156,4 +156,4 @@ if 0 < bytes_read {
 
 ## Reference
 
-For more information about the DAL, see [DAL overview](https://tezos.gitlab.io/shell/dal_overview.html) in the Octez documentation.
+For more information about the DAL, see [DAL overview](https://octez.tezos.com/docs/shell/dal_overview.html) in the Octez documentation.

docs/architecture/governance.md

@@ -79,5 +79,5 @@ At the end of the Adoption period, Mainnet automatically enables the new protoco
 
 ## References
 
-- [The Amendment (and Voting) Process](https://tezos.gitlab.io/active/voting.html) in the Octez documentation
+- [The Amendment (and Voting) Process](https://octez.tezos.com/docs/active/voting.html) in the Octez documentation
 - [Amending Tezos](https://medium.com/tezos/amending-tezos-b77949d97e1e) on Medium

docs/architecture/governance/amendment-history.md

@@ -26,7 +26,7 @@ In order to meet these requirements, the software that nodes run is structured a
 
 Nodes cooperate with clients and with each other through an [RPC interface](#the-rpc-interface).
 
-The Octez suite, which is an implementation of the Tezos node and other executables, instantiates these principles in the [Octez software architecture](https://tezos.gitlab.io/shell/the_big_picture.html).
+The Octez suite, which is an implementation of the Tezos node and other executables, instantiates these principles in the [Octez software architecture](https://octez.tezos.com/docs/shell/the_big_picture.html).
 
 For instructions on running a node, see the tutorial [Run a Tezos node in 5 steps](/tutorials/join-dal-baker).
 
@@ -79,7 +79,7 @@ Tezos nodes act as servers and accept HTTP requests from clients and other nodes
 
 Tezos RPC uses JSON to send and receive data, but it does not adhere to the JSON-RPC specification.
 
-All the RPCs served by the Tezos node are described as an OpenAPI specification at [Octez Node RPCs](https://tezos.gitlab.io/api/openapi.html#octez-node) in the Octez documentation.
+All the RPCs served by the Tezos node are described as an OpenAPI specification at [Octez Node RPCs](https://octez.tezos.com/docs/api/openapi.html#octez-node) in the Octez documentation.
 
 ### Public and private RPC nodes
 

docs/architecture/nodes.md

@@ -20,7 +20,7 @@ In this way, multiple nodes can run the same rollup and each node can verify the
 
 For a tutorial on Smart Rollups, see [Deploy a Smart Rollup](/tutorials/smart-rollup).
 
-For reference on Smart Rollups, see [Smart Optimistic Rollups](https://tezos.gitlab.io/active/smart_rollups.html) in the Octez documentation.
+For reference on Smart Rollups, see [Smart Optimistic Rollups](https://octez.tezos.com/docs/active/smart_rollups.html) in the Octez documentation.
 
 This diagram shows a high-level view of how Smart Rollups interact with layer 1:
 
@@ -212,7 +212,7 @@ When a commitment includes layer 1 transactions, these transactions go into the
 
 After the commitment is cemented, clients can trigger transactions in the outbox with the Octez client `execute outbox message` command.
 When they trigger a transaction, it runs like any other call to a smart contract.
-For more information, see [Triggering the execution of an outbox message](https://tezos.gitlab.io/shell/smart_rollup_node.html?highlight=triggering) in the Octez documentation.
+For more information, see [Triggering the execution of an outbox message](https://octez.tezos.com/docs/shell/smart_rollup_node.html#triggering-the-execution-of-an-outbox-message) in the Octez documentation.
 
 ### Bailout process
 
@@ -222,7 +222,7 @@ Nodes that post commitments cannot stop immediately without risking their bonds
 For this reason, nodes can switch to bailout mode to prepare to shut down without risking their bonds.
 In bailout mode, nodes defend their existing commitments without posting new commitments.
 When their final commitment is cemented, they can shut down safely.
-For more information about node modes, see [Smart rollup node](https://tezos.gitlab.io/shell/smart_rollup_node.html) in the Octez documentation.
+For more information about node modes, see [Smart rollup node](https://octez.tezos.com/docs/shell/smart_rollup_node.html) in the Octez documentation.
 
 ## Examples
 

docs/architecture/smart-rollups.md

@@ -21,7 +21,7 @@ You can verify that a contract follows the FA1.2 standard by running the followi
 octez-client check contract $CONTRACT_ADDRESS implements fa1.2
 ```
 
-The Octez client also supports other interactions with FA1.2 contracts, such as transferring tokens or checking balances, as described at [FA1.2 support](https://tezos.gitlab.io/user/fa12.html) in the Octez documentation.
+The Octez client also supports other interactions with FA1.2 contracts, such as transferring tokens or checking balances, as described at [FA1.2 support](https://octez.tezos.com/docs/user/fa12.html) in the Octez documentation.
 
 ## Allowances
 

docs/architecture/tokens/FA1.2.md

@@ -59,7 +59,7 @@ See https://taqueria.io/.
 To test smart contracts and dApps, you can use these test environments:
 
 - Test networks behave like Tezos Mainnet but have differences that make it easier to test on them, such as faucets that provide free tokens and reduced block times for faster testing.
-- Sandbox environments like [Flextesa](https://tezos.gitlab.io/flextesa/) run Tezos nodes locally on your computer in a sandbox mode.
+- Sandbox environments like Flextesa and Tezbox run Tezos nodes locally on your computer in a sandbox mode; see [Using a local sandbox](/developing/sandbox).
 - You can also set up your own private test network.
 
 For more information about test environments, see [Testing on testnets](/developing/testnets) and [Using a local sandbox](/developing/sandbox).

docs/developing.md

@@ -15,5 +15,5 @@ Developers use the Octez client for many tasks, including:
 Other parts of Octez allow you to host, manage, and monitor nodes, bake blocks, and host RPC nodes.
 
 This documentation is an overview of the Octez client for Tezos smart contract and dApp developers.
-For more detailed information, see the [Octez documentation](https://tezos.gitlab.io/) and opentezos.com.
-For system requirements, see the documentation for the latest release of the Octez suite here: https://tezos.gitlab.io/releases/latest.html.
+For more detailed information, see the [Octez documentation](https://octez.tezos.com/docs/) and opentezos.com.
+For system requirements, see the documentation for the latest release of the Octez suite here: https://octez.tezos.com/docs/releases/latest.html.