Merge pull request #3688 from dfinity/core-concepts

Move "Core concepts" pages and revise

docs/developer-docs/cost-estimations-and-examples.mdx

@@ -10,7 +10,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 ## Overview
 
-To get a rough estimate of how much your project may cost, below is a pricing calculator that can be used to estimate the cost of a dapp deployed on ICP. Costs are charged to a canister in cycles, which are fixed against the price of [XDR](/docs/current/concepts/glossary#xdr), where **1 trillion cycles equals 1 XDR**.
+To get a rough estimate of how much your project may cost, below is a pricing calculator that can be used to estimate the cost of a dapp deployed on ICP. Costs are charged to a canister in cycles, which are fixed against the price of [XDR](/docs/current/references/glossary#xdr), where **1 trillion cycles equals 1 XDR**.
 Cycles costs are calculated based on:
 
 - **Messaging**: Calls that are made to a canister's methods. Costs depend on the type of call being sent (query, update, inter-canister, etc.), the size of the message's request and response bytes, and the total number of messages a canister sends and receives.
@@ -27,7 +27,7 @@ Note that query calls are currently free and do not incur a cost.
 
 ## ICP pricing calculator
 
-The calculator below estimates costs in USD, though your project will be charged in [cycles](gas-cost.mdx). Cycles have a fixed cost, where **1 trillion cycles equals 1 [XDR](/docs/current/concepts/glossary#xdr)**. [Learn more about how to obtain cycles](/docs/current/developer-docs/defi/cycles/converting_icp_tokens_into_cycles).
+The calculator below estimates costs in USD, though your project will be charged in [cycles](gas-cost.mdx). Cycles have a fixed cost, where **1 trillion cycles equals 1 [XDR](/docs/current/references/glossary#xdr)**. [Learn more about how to obtain cycles](/docs/current/developer-docs/defi/cycles/converting_icp_tokens_into_cycles).
 
 <iframe
   id="frame-src"

docs/developer-docs/daos/nns/using-the-nns-dapp/nns-dapp-additional-features.mdx

@@ -32,7 +32,7 @@ To view current and past SNS decentralization swaps from the NNS dapp:
 
 ## Deploying and managing canisters from the NNS dapp
 
-You must have **cycles** available to create and manage [<GlossaryTooltip>canisters</GlossaryTooltip>](/docs/current/concepts/glossary#canister).
+You must have **cycles** available to create and manage [<GlossaryTooltip>canisters</GlossaryTooltip>](/docs/current/references/glossary#canister).
 The [NNS dapp](https://nns.ic0.app) provides a convenient way for you to create and manage canisters by enabling you to convert ICP utility tokens into cycles and attach cycles to specific canister identifiers.
 
 To create a new canister:

docs/developer-docs/defi/overview.mdx

@@ -23,7 +23,7 @@ ICP tokens are the network's native utility token. They are used for different a
 
 [ICRC](https://github.com/dfinity/ICRC) stands for `Internet Computer Request for Comments` and is a working group for various topics. ICRC standards can be created for anything, not just token types. Currently, the protocol supports the ICRC token standards ICRC-1, ICRC-2, ICRC-3, and ICRC-7, with several more in the process of being drafted and developed.
 
-[Chain-key](/docs/current/developer-docs/multi-chain/chain-key-tokens/overview) tokens are created using ICP's chain-key cryptography protocols, such as [threshold signing](https://internetcomputer.org/docs/current/concepts/glossary#chain-key). The chain-key tokens ckBTC, ckETH, and ckERC20 use ICRC-1 ledgers that support the ICRC-2 extension. Each chain-key token is deployed on ICP and backed 1:1 with the native token, such as BTC, ETH, or ERC20, locked and kept on their native chain. There are no intermediaries or centralized bridges used for chain-key tokens.
+[Chain-key](/docs/current/developer-docs/multi-chain/chain-key-tokens/overview) tokens are created using ICP's chain-key cryptography protocols, such as [threshold signing](https://internetcomputer.org/docs/current/references/glossary#chain-key). The chain-key tokens ckBTC, ckETH, and ckERC20 use ICRC-1 ledgers that support the ICRC-2 extension. Each chain-key token is deployed on ICP and backed 1:1 with the native token, such as BTC, ETH, or ERC20, locked and kept on their native chain. There are no intermediaries or centralized bridges used for chain-key tokens.
 
 The older token standards, [DIP-20](https://github.com/Psychedelic/DIP20) and [DIP-721](https://github.com/Psychedelic/DIP721), are designed to resemble the Ethereum ERC-20 and ERC-721 standards respectively. While some projects on ICP still use DIP-20 and DIP-721, the new ICRC-2 and ICRC-7 standards are designed to provide a newer, alternative standard for each.
 

docs/developer-docs/gas-cost.mdx

@@ -34,7 +34,7 @@ A [freezing threshold](/docs/current/developer-docs/smart-contracts/maintain/set
 
 ## Units and fiat value
 
-The price of cycles is fixed against the price of [XDR](/docs/current/concepts/glossary#xdr), where **1 trillion cycles equals 1 XDR**. As of December 18, 2023, the exchange rate for 1 XDR = $1.336610. The exchange rate for USD/XDR may vary. Learn more about [XDR exchange rates](https://www.imf.org/external/np/fin/data/rms_sdrv.aspx).
+The price of cycles is fixed against the price of [XDR](/docs/current/references/glossary#xdr), where **1 trillion cycles equals 1 XDR**. As of December 18, 2023, the exchange rate for 1 XDR = $1.336610. The exchange rate for USD/XDR may vary. Learn more about [XDR exchange rates](https://www.imf.org/external/np/fin/data/rms_sdrv.aspx).
 
 The following table shows units of cycles and the respective fiat values:
 

docs/developer-docs/identity/verifiable-credentials/relying-party.mdx

@@ -311,7 +311,7 @@ When the actual credential decoded, the following info is returned:
 
 To verify the two JWT signatures, verify the signature of the `id_alias` signed by the identity provider, and the signature of the actual credential signed by the issuer. Both are found when you decode the received JWT.
 
-These signatures are [canister signatures](https://internetcomputer.org/docs/current/concepts/glossary#canister-signature) and there is an example on [how to verify those in the Internet Identity repository](https://github.com/dfinity/internet-identity/blob/2ae06956f9cabc048b8536b29b9f861092958515/src/vc_util/src/lib.rs#L193).
+These signatures are [canister signatures](https://internetcomputer.org/docs/current/references/glossary#canister-signature) and there is an example on [how to verify those in the Internet Identity repository](https://github.com/dfinity/internet-identity/blob/2ae06956f9cabc048b8536b29b9f861092958515/src/vc_util/src/lib.rs#L193).
 
 ### Semantic verification
 

docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx

@@ -11,7 +11,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 One common way that blockchain networks can enable cross-chain workflows is by 'wrapping' tokens. A wrapped token typically represents an underlying asset on a different blockchain, such as wrapped Bitcoin deployed on Ethereum. Traditional wrapped tokens involve an intermediary that needs to be trusted.
 
-ICP introduces a more secure alternative to wrapped tokens known as **chain-key** tokens. Chain-key tokens are created using ICP's chain-key cryptography protocols, such as [threshold signing](https://internetcomputer.org/docs/current/concepts/glossary#chain-key). Each chain-key token is deployed on ICP and backed 1:1 with the native token held 100% onchain by an ICP smart contract. There are no intermediaries or centralized bridges used for chain-key tokens.
+ICP introduces a more secure alternative to wrapped tokens known as **chain-key** tokens. Chain-key tokens are created using ICP's chain-key cryptography protocols, such as [threshold signing](https://internetcomputer.org/docs/current/references/glossary#chain-key). Each chain-key token is deployed on ICP and backed 1:1 with the native token held 100% onchain by an ICP smart contract. There are no intermediaries or centralized bridges used for chain-key tokens.
 
 Chain-key tokens can be swapped for one another seamlessly. Making transactions with chain-key tokens on ICP is often faster and cheaper than transactions on the token's native network.
 

docs/developer-docs/multi-chain/ethereum/evm-rpc/evm-rpc-canister.mdx

@@ -88,7 +88,7 @@ Alternatively, you can include the EVM RPC canister by specifying the Candid and
 }
 ```
 
-Then start the local replica and deploy the canister locally with a specified number of nodes (`31` for the [fiduciary subnet](/docs/current/concepts/subnet-types#fiduciary-subnets)):
+Then start the local replica and deploy the canister locally with a specified number of nodes (`31` for the [fiduciary subnet](/docs/current/references/subnets/subnet-types#fiduciary-subnets)):
 
 ```
 dfx start --clean --background
@@ -804,7 +804,7 @@ dfx canister call evm_rpc eth_sendRawTransaction "(variant {$RPC_SOURCE}, $RPC_C
 
 :::
 Some JSON-RPC APIs may only return a `NonceTooLow` status when successfully submitting a transaction. This is because during the HTTP outcall consensus, only the first request is successful, while the others reply with a duplicate transaction status.
-If you encounter this issue, one possible workaround is to use a deduplicating proxy server such as the community-built C-ATTS EVM RPC proxy ([source code](https://github.com/c-atts/catts-evm-rpc-proxy)). 
+If you encounter this issue, one possible workaround is to use a deduplicating proxy server such as the community-built C-ATTS EVM RPC proxy ([source code](https://github.com/c-atts/catts-evm-rpc-proxy)).
 :::
 
 ### Error "already known"

docs/developer-docs/multi-chain/ethereum/evm-rpc/overview.mdx

@@ -78,7 +78,7 @@ Learn more about the [costs of EVM RPC requests](costs.mdx).
 
 ## Deployed canister
 
-The EVM RPC canister runs on the 34-node [fiduciary subnet](https://internetcomputer.org/docs/current/concepts/subnet-types#fiduciary-subnets) with the following principal: [`7hfb6-caaaa-aaaar-qadga-cai`](https://dashboard.internetcomputer.org/canister/7hfb6-caaaa-aaaar-qadga-cai).
+The EVM RPC canister runs on the 34-node [fiduciary subnet](https://internetcomputer.org/docs/current/references/subnets/subnet-types#fiduciary-subnets) with the following principal: [`7hfb6-caaaa-aaaar-qadga-cai`](https://dashboard.internetcomputer.org/canister/7hfb6-caaaa-aaaar-qadga-cai).
 
 Refer to the [GitHub repository](https://github.com/internet-computer-protocol/evm-rpc-canister?tab=readme-ov-file#reproducible-builds) for information on how to verify the hash of the deployed WebAssembly module.
 

docs/developer-docs/multi-chain/overview.mdx

@@ -100,7 +100,7 @@ primitives that are not natively available on other chains. For example:
 A key feature of the ICP’s Chain Fusion capabilities is [threshold signing](/docs/current/developer-docs/smart-contracts/signatures/t-ecdsa/). This feature allows canisters to control accounts on other blockchains. The private keys that are used to sign transactions are never accessible in a single physical place, but securely distributed as shares among a group of nodes performing a threshold signing protocol to generate signatures on behalf of a canister.
 
 :::info
-Threshold signing is also referred to as [chain-key cryptography](/docs/current/concepts/glossary#chain-key).
+Threshold signing is also referred to as [chain-key cryptography](/docs/current/references/glossary#chain-key).
 :::
 
 ### Integrations