Fix Advanced move to Concepts

Author: v0-e

vocs-docs/docs/pages/advanced/full-node-streaming/example.mdx renamed to vocs-docs/docs/pages/concepts/advanced/full-node-streaming/example.mdx

@@ -2,7 +2,7 @@
 
 [Indexer-based orderbook streaming](/interaction/data/watch-orderbook), due to the increased latency introduced by the Indexer, can cause issues like more outdated orders or a crossed orderbook.
 In a full node, the orderbook available will be more up-to-date and should be preferred over the Indexer-based solution.
-This requires a full node with [gRPC streaming enabled](/advanced/full-node-streaming).
+This requires a full node with [gRPC streaming enabled](/concepts/advanced/full-node-streaming).
 
 :::note
 While more up-to-date than the Indexer, the orderbook state can vary slightly between nodes due to dYdX's offchain orderbook design.

vocs-docs/docs/pages/advanced/full-node-streaming/index.mdx renamed to vocs-docs/docs/pages/concepts/advanced/full-node-streaming/index.mdx

@@ -4,7 +4,7 @@ Optimizing your full node helps keep it online, up to date, and operating quickl
 ## Prerequisites
 You need a running, non-validating full node that is connected to a network. 
 
-- If you created a system service for your node by following the instructions on the previous page, [Set Up a Full Node](/advanced/running-node/setup), start your node with the following command:
+- If you created a system service for your node by following the instructions on the previous page, [Set Up a Full Node](/concepts/advanced/running-node/setup), start your node with the following command:
   ```bash
   stystemctl start dydxprotocold
   ```
@@ -27,7 +27,7 @@ Specify a list of healthy, stable nodes that you trust. Your node prioritizes co
 ### Save a List of Persistent Peers
 You can save a list of healthy, stable nodes in the `persistent_peers` field of your `config.toml` file.
 
-Request a list of healthy peers for your deployment from a [Live Peer Node](/advanced/resources#live-peer-node-providers) provider.
+Request a list of healthy peers for your deployment from a [Live Peer Node](/concepts/advanced/resources#live-peer-node-providers) provider.
 
 From the list of healthy peers that you retrieve from peer node provider, choose any 5 for your node to query for the latest state. Add a comma-separated list of those peer addresses to the `persistent_peers` field in your `config.toml`, like in the following example:
 
@@ -40,7 +40,7 @@ persistent_peers=83c299de2052db247f08422b6592e1383dd7a104@136.243.36.60:23856,1c
 ### Replace Your Address Book File
 As an alternative to persistent peers, you can replace your node's local address book with the latest address book from a trusted provider. The address book file contains the latest connection information for peers from that provider.
 
-Download an up-to-date `addrbook.json` file for your deployment from an [Address Book](/advanced/resources#address-book-providers) provider. 
+Download an up-to-date `addrbook.json` file for your deployment from an [Address Book](/concepts/advanced/resources#address-book-providers) provider. 
 
 Save it in your `/.dydxprotocol/config` directory, replacing the existing `addrbook.json` file.
 
@@ -54,7 +54,7 @@ You can speed up the re-syncing process significantly by providing your node wit
 ### Configure Your Node's State Sync Setting
 You can use state sync, a configuration setting that allows your node to retrieve a snapshot from the network, to ensure that your node can be restored quickly if it falls out of sync.
 
-To use state sync for quick recovery in case your node falls out of sync, follow the instructions for your deployment from a [State Sync](/advanced/resources#state-sync-service) service.
+To use state sync for quick recovery in case your node falls out of sync, follow the instructions for your deployment from a [State Sync](/concepts/advanced/resources#state-sync-service) service.
 
 :::info
 Cosmos SDK 0.40 release will include automatic support for state sync, and developers only need to enable it in their applications to make use of it. Replace above with a procedure.
@@ -63,7 +63,7 @@ Cosmos SDK 0.40 release will include automatic support for state sync, and devel
 ### Save a Snapshot on Your System
 As an alternative to state sync, you can use a snapshot that you have saved on your node's system to restore your node if it falls out of sync.
 
-To save a snapshot on your system for quick recovery in case your node falls out of sync, install a snapshot for your deployment from a [Snapshot Service](/advanced/resources#snapshot-service).
+To save a snapshot on your system for quick recovery in case your node falls out of sync, install a snapshot for your deployment from a [Snapshot Service](/concepts/advanced/resources#snapshot-service).
 
 ## Configure a Pruning Strategy
 To reduce the amount of storage your node requires, dYdX recommends the following pruning setting, configured in your `app.toml` file:

vocs-docs/docs/pages/advanced/network-constants.mdx renamed to vocs-docs/docs/pages/concepts/advanced/network-constants.mdx

@@ -16,7 +16,7 @@ To set up a full node, you can either:
 Save the script with an `.sh` extension in your `$HOME` directory. Edit the script, replacing default values in fields such `VERSION` and `CHAIN-ID` with your own. Run the script with the following commands:
 
 :::note
-To find the current version of the [dYdX Foundation](https://www.dydx.foundation/) mainnet, see the recommended protocol version on [mintscan.io](https://www.mintscan.io/dydx/parameters). To find network constants such as chain IDs, see the [Network Configuration](/advanced/network-constants) section of the documentation.
+To find the current version of the [dYdX Foundation](https://www.dydx.foundation/) mainnet, see the recommended protocol version on [mintscan.io](https://www.mintscan.io/dydx/parameters). To find network constants such as chain IDs, see the [Network Configuration](/concepts/advanced/network-constants) section of the documentation.
 :::
 
 ```bash
@@ -105,7 +105,7 @@ dydxprotocold init --chain-id=dydx-mainnet-1 my-node
 ```
 
 :::note
-See the [Network Configuration](/advanced/network-constants) section of the documentation for chain IDs and other network constants.
+See the [Network Configuration](/concepts/advanced/network-constants) section of the documentation for chain IDs and other network constants.
 :::
 
 When you initialize your node, `dydxprotocold` returns your default node configuration in JSON.
@@ -114,7 +114,7 @@ When you initialize your node, `dydxprotocold` returns your default node configu
 A seed node acts as an address book and helps your node join the network. To update `config.toml` with a list of seed nodes, run the following command:
 
 :::note
-Check the [Resources](/advanced/resources#seed-nodes) page for an up-to-date list of seed nodes for the network to which you want to connect.
+Check the [Resources](/concepts/advanced/resources#seed-nodes) page for an up-to-date list of seed nodes for the network to which you want to connect.
 :::
 
 ```bash
@@ -171,7 +171,7 @@ To download and extract the snapshot contents to the default dydxprotocol home d
 cd $HOME/.dydxprotocol
 ```
 
-Next, find a provider for your use case on the [Snapshot Service](/advanced/resources#snapshot-service) page. Use the provider's instructions to download the snapshot into your `$HOME/.dydxprotocol` directory.
+Next, find a provider for your use case on the [Snapshot Service](/concepts/advanced/resources#snapshot-service) page. Use the provider's instructions to download the snapshot into your `$HOME/.dydxprotocol` directory.
 
 > For example, if you are connecting to `dydx-mainnet-1`, you may use the provider [Polkachu](https://polkachu.com/tendermint_snapshots/dydx). In most cases, you can run `wget <snapshot-web-address>`.
 
@@ -260,4 +260,4 @@ When your full node's latest block is the same as the network's latest block, yo
 ::::
 
 ## Next Steps
-When your full node is up to date with the network, you can use it to read live data and configure additional settings. Learn more on the [Optimizing Your Full Node](/advanced/running-node/optimize) and [Full Node Streaming](/advanced/full-node-streaming) pages.
+When your full node is up to date with the network, you can use it to read live data and configure additional settings. Learn more on the [Optimizing Your Full Node](/concepts/advanced/running-node/optimize) and [Full Node Streaming](/concepts/advanced/full-node-streaming) pages.