Merge branch 'master' into jessiemongeon1-patch-6

docs/developer-docs/ai/ai-on-chain.mdx

@@ -10,7 +10,7 @@ import '/src/components/CenterImages/center.scss';
 
 <MarkdownChipRow labels={["Advanced", "Tutorial", "Rust" ]} />
 
-## Overview
+
 
 ICP's unique ability to run compute at scale allows AI and neural networks to run directly onchain within a canister smart contract.
 

docs/developer-docs/ai/inference.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Concept", "DeAI" ]} />
 
-## Overview 
+
 
 Inference in the context of decentralized AI refers to using a trained model to draw conclusions about new data. 
 It's possible for canister smart contracts to run inference in a number of ways depending on the decentralization and performance requirements.

docs/developer-docs/ai/machine-learning-sample.mdx

@@ -11,7 +11,7 @@ import '/src/components/CenterImages/center.scss';
 <MarkdownChipRow labels={["Advanced", "Tutorial", "Rust" ]} />
 
 
-## Overview
+
 
 Machine learning is a form of artificial intelligence (AI) that observes statistical algorithms and their data to learn patterns and generalizations. By analyzing these data patterns, machine learning algorithms can execute tasks by predicting the correct result with high accuracy.
 

docs/developer-docs/ai/samples.mdx

@@ -10,7 +10,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Concept", "DeAI" ]} />
 
-## Overview
+
 
 ICP's unique ability to run compute at scale allows AI and neural networks to run directly onchain within a canister smart contract. Canisters can also interact with LLMs stored off-chain through HTTPS outcalls, or stored locally on a user's device.
 

docs/developer-docs/ai/training-models.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Motoko", "Concept"]} />
 
-## Overview
+
 
 Training AI models on ICP provides developers with a decentralized infrastructure and simplifies the setup process. ICP’s built-in computation and storage capabilities remove the need for external hardware. With GPU support on the roadmap, ICP will soon further enhance its AI capabilities and allow developers to train complex models, including large-scale AI systems.
 

docs/developer-docs/backend/rust/access-control.mdx

@@ -9,7 +9,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 To demonstrate access control using a Rust backend canister, you'll explore access control in the context of NFTs. NFTs (non-fungible tokens) are unique tokens with arbitrary
 metadata, usually an image of some kind, to form the digital equivalent of trading cards.

docs/developer-docs/backend/rust/candid.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 Candid is an **interface description language** with the primary purpose of describing the public interface of a service. A service is usually in the form of a program deployed as a canister. Candid is language-agnostic, meaning that it allows for the inter-operation between services and frontends written in different programming languages, including Rust.
 

docs/developer-docs/backend/rust/counter.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 In this guide, you are going to write a dapp that provides a few basic functions to increment a counter value. by calling functions on a deployed canister. By calling the function to increment a value multiple times, you can verify that the variable state, that is, the value of the variable between calls, persists.
 

docs/developer-docs/backend/rust/deploying.mdx

@@ -9,7 +9,7 @@ import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
 
 <MarkdownChipRow labels={["Beginner", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 In this guide, you'll learn the steps required to write, compile, deploy, and interact with a Rust backend canister.
 

docs/developer-docs/backend/rust/generating-candid.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 In versions of the Rusk CDK `v0.11.0` and higher, the Candid export workflow has been changed.
 You can call the `ic_cdk::export_candid!()` macro to enable the Candid export behavior, then use the [candid-extractor](https://github.com/dfinity/cdk-rs/tree/main/src/candid-extractor) to extract the Candid from the canister's Wasm.

docs/developer-docs/backend/rust/intercanister.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 Inter-canister calls can be used to update information between two or more canisters.
 

docs/developer-docs/backend/rust/message-inspect.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 A canister can inspect an ingress message and either accept or decline the message through the canister's HTTPS interface. If the message is accepted, the canister will execute it.
 

docs/developer-docs/backend/rust/optimizing.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Rust", "Tutorial"]} />
 
-## Overview
+
 Compiling Rust to Wasm often increases the file size significantly. `dfx` versions `0.14.0` and newer include the `wasm-opt` package that can be used to optimize cycle consumption and binary size.
 
 ## Prerequisites

docs/developer-docs/backend/rust/project-organization.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Rust" ]} />
 
-## Overview
+
 
 When a new Rust project is created with the command:
 

docs/developer-docs/backend/rust/quickstart.mdx

@@ -9,7 +9,7 @@ import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
 
 <MarkdownChipRow labels={["Beginner", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 Applications for ICP start as **projects**. You can create new projects for ICP using the IC SDK. This guide focuses on how to create, build, and deploy a Rust program by using the `dfx` parent command and its subcommands.
 

docs/developer-docs/backend/rust/rust-considerations.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Rust" ]} />
 
-## Overview
+
 
 This guide describes information that developers should consider when writing Rust canisters, specifically regarding canister observability and global state.
 

docs/developer-docs/backend/rust/rust-limitations.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 WebAssembly (Wasm) is a binary code format and does not provide network access, a filesystem, or other functionalities other than pure computation. Anything function that needs to communicate outside of the Wasm module must use an IC API. This guide details limitations imposed by Wasm on canisters written in Rust. 
 

docs/developer-docs/backend/rust/searching-records.mdx

@@ -9,7 +9,7 @@ import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
 
 <MarkdownChipRow labels={["Intermediate", "Rust", "Tutorial"]} />
 
-## Overview
+
 In this guide, you are going to write a dapp that provides a few basic functions to add and retrieve simple profile records that consist of a name, description, and an array of keywords.
 
 This program supports the following functions:

docs/developer-docs/backend/rust/stable-structures.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 Stable structures are designed to use stable memory as the backing store, allowing them to grow to gigabytes in size without the need for `pre_upgrade`/`post_upgrade` hooks.
 

docs/developer-docs/backend/rust/timers.mdx

@@ -9,7 +9,7 @@ import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
 
 <MarkdownChipRow labels={["Beginner", "Rust", "Tutorial"]} />
 
-## Overview
+
 This guide demonstrates how to create a small dapp with a periodic task. The task is triggered automatically by the ICP network with a specified interval.
 
 ## Prerequisites

docs/developer-docs/backend/rust/upgrading.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Rust", "Tutorial"]} />
 
-## Overview
+
 
 Unlike a canister reinstall that preserves the canister identifier but no state, a canister upgrade enables you to preserve the state of a deployed canister and change the code.
 

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

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Concept"]} />
 
-## 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/references/glossary#xdr), where **1 trillion cycles equals 1 XDR**.
 Cycles costs are calculated based on:

docs/developer-docs/daos/nns/concepts/neurons/becoming-a-known-neuron.mdx

@@ -9,7 +9,7 @@ import '/src/components/CenterImages/center.scss';
 
 <MarkdownChipRow labels={["Advanced", "Governance", "Tutorial"]} />
 
-## Overview
+
 A know neuron has a name and optionally a short description.
 A known neuron can be registered in the NNS governance via a proposal, officially storing its name and description
 within the NNS. This information can be used by other neurons to find known neurons and [follow](/docs/current/developer-docs/daos/nns/concepts/neurons/neuron-following) them.

docs/developer-docs/daos/nns/concepts/neurons/neuron-following.mdx

@@ -9,7 +9,7 @@ import '/src/components/CenterImages/center.scss';
 
 <MarkdownChipRow labels={["Beginner", "Governance", "Concept"]} />
 
-## Overview
+
 Users may not have the time or knowledge to participate in all voting decisions.
 Therefore, instead of directly voting on proposals, neuron holders may choose to delegate their vote to other neurons that they trust with certain decisions.
 This concept, where a neuron follows the decisions of some other neurons, is called **following** in the NNS DAO.

docs/developer-docs/daos/nns/concepts/neurons/neuron-management.mdx

@@ -15,7 +15,7 @@ This page is for you if you want to learn the technical details about neuron ope
 
 Tutorials for users who want to interact with the NNS using the [NNS dapp](https://nns.ic0.app) frontend are available in the [NNS dapp quickguide](/docs/current/developer-docs/daos/nns/using-the-nns-dapp/nns-app-quickstart).
 
-## Overview
+
 View the most up-to-date [`candid` definition for the NNS governance canister](https://github.com/dfinity/ic/blob/master/rs/nns/governance/canister/governance.did).
 This page will explain some of the relevant definitions from this Candid file.
 To keep up to date with new NNS release proposals from DFINITY, you can subscribe to [this forum thread](https://forum.dfinity.org/t/nns-updates-aggregation-thread/23551).

docs/developer-docs/daos/nns/concepts/neurons/staking-voting-rewards.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Governance", "Concept"]} />
 
-## Overview
+
 Stakeholders gain voting power and can earn voting rewards by staking their ICP tokens in neurons and participating in governance.
 
 The Internet Computer is a decentralized platform whose evolution is decided by its stakeholders through voting.

docs/developer-docs/daos/nns/concepts/proposals/direct-voting.mdx

@@ -9,7 +9,7 @@ import '/src/components/CenterImages/center.scss';
 
 <MarkdownChipRow labels={["Beginner", "Governance", "Concept"]} />
 
-## Overview
+
 The NNS DAO is an open governance system where anyone can become a participant by [staking some ICP in a neuron](https://internetcomputer.org/docs/current/developer-docs/daos/nns/using-the-nns-dapp/nns-app-quickstart#stake-icp-utility-tokens-in-a-neuron). At least 1 ICP is required to create a neuron.
 
 Locking tokens for a period of time is known as the neuron's dissolve delay. If a neuron has more than 6 months dissolve delay, it is eligible to participate in voting. This means that it can both submit and vote on proposals.

docs/developer-docs/daos/nns/overview.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Beginner", "Governance" ]} />
 
-## Overview
+
 <div class="text--center">
 <p> </p>
 </div>

docs/developer-docs/daos/nns/using-the-nns-dapp/nns-app-quickstart.mdx

@@ -9,7 +9,7 @@ import '/src/components/CenterImages/center.scss';
 
 <MarkdownChipRow labels={["Beginner", "Governance", "Tutorial"]} />
 
-## Overview
+
 
 There are different ways to interact with the NNS DAO to participate in governance.
 

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

@@ -10,7 +10,7 @@ import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
 
 <MarkdownChipRow labels={["Intermediate", "Governance", "Tutorial"]} />
 
-## Overview
+
 In addition to being the portal for interacting with the NNS DAO, the NNS dapp also provides access to the SNS DAOs, their launches, and allows users to manage canisters that they control.
 This is a brief guide to some of these additional functionalities.
 

docs/developer-docs/daos/nns/using-the-nns-dapp/nns-dapp-advanced-neuron-operations.mdx

@@ -9,7 +9,7 @@ import '/src/components/CenterImages/center.scss';
 
 <MarkdownChipRow labels={["Intermediate", "Governance", "Tutorial"]} />
 
-## Overview
+
 Once you are a bit more familiar with the NNS, you might want to use the NNS dapp to perform additional neuron operations.
 
 For more background on neurons, including the concepts of voting rewards and what the different neuron operations do in details,

docs/developer-docs/daos/nns/using-the-nns-dapp/nns-dapp-following-other-neurons.mdx

@@ -15,7 +15,7 @@ import '/src/components/CenterImages/center.scss';
 <div class="text--center">
 <iframe width="660" height="415" src="https://www.youtube.com/embed/6BznC9p3w8w?si=m7nc7xTGq5YUtXa3" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> </div>
 
-## Overview
+
 Neuron owners may find it hard to manually vote on every proposal submitted to the NNS.
 For example, they may not have the time or necessary expertise to evaluate each individual proposal.
 The NNS uses a form of liquid democracy to address these challenges called **following**.

docs/developer-docs/daos/nns/using-the-nns-dapp/nns-dapp-importing-tokens.mdx

@@ -15,7 +15,7 @@ import '/src/components/CenterImages/center.scss';
 <div class="text--center">
 <iframe width="660" height="415" src="https://www.youtube.com/embed/zcXmarBk2L4?si=OIxq9LwY0DLzHvE1" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> </div>
 
-## Overview
+
 
 The NNS dapp focuses on providing a simple user interface where community members can interact with different on-chain governance systems deployed on the Internet Computer.
 

docs/developer-docs/daos/nns/using-the-nns-dapp/nns-dapp-making-neurons-public.mdx

@@ -9,7 +9,7 @@ import '/src/components/CenterImages/center.scss';
 
 <MarkdownChipRow labels={["Beginner", "Governance", "Tutorial"]} />
 
-## Overview
+
 
 Neuron visibility settings are available in order to support a [neuron index](https://dashboard.internetcomputer.org/proposal/48491) while respecting neuron holders' privacy. A neuron can be private or public. For public neurons, anyone who knows the neuron's ID can see the full neuron's details, including how they vote on proposals. [Learn more about the differences between private and public neurons](/docs/current/developer-docs/daos/nns/concepts/neurons/neuron-management#neuron-visibility).
 

docs/developer-docs/daos/nns/using-the-nns-dapp/nns-dapp-manage-quill-neurons.mdx

@@ -15,7 +15,7 @@ import '/src/components/CenterImages/center.scss';
 <div class="text--center">
 <iframe width="660" height="415" src="https://www.youtube.com/embed/lKbYUmqF7J4?si=jIvx5rEza7BnMchE" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> </div>
 
-## Overview
+
 You may have neurons controlled by a principal ID that was created using [quill](../../../../../../docs/current/developer-docs/developer-tools/cli-tools/quill-cli-reference/quill-parent). In this case, it may be inconvenient to manage your neurons through the terminal. If you know the seed phrase of this principal ID, you can use a Ledger hardware wallet to manage your neurons through the [NNS dapp](https://nns.ic0.app/).
 
 ## How to access neurons controlled by a principal ID created with quill

docs/developer-docs/daos/nns/using-the-nns-dapp/nns-dapp-send-and-receive-tokens.mdx

@@ -9,7 +9,7 @@ import '/src/components/CenterImages/center.scss';
 
 <MarkdownChipRow labels={["Beginner", "Governance", "Tutorial"]} />
 
-## Overview
+
 When you log into the NNS dapp for the first time you will not yet have any ICP tokens in your wallet.
 Therefore, you first might want transfer some tokens to the NNS dapp wallet.
 This also the first step required for staking a neuron with the NNS dapp.

docs/developer-docs/daos/sns/index.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Advanced", "Governance" ]} />
 
-## Overview
+
 These pages introduce instructions needed when considering handing over control of a
 dapp to a Service Nervous System (SNS) or integrating with an SNS.
 If this is the first time you hear about the SNS, it is recommended to take a look at the high level [SNS](/sns)

docs/developer-docs/daos/sns/launching/integrating.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Advanced", "Governance", "Concept"]} />
 
-## Overview
+
 
 When planning an SNS launch, one topic to consider is whether and how the SNS functionality should be integrated in the dapp.
 For example, one may want to embed a frontend for the SNS swap or for the SNS governance in the dapp's UI.

docs/developer-docs/daos/sns/launching/launch-steps-1proposal.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Advanced", "Governance", "Tutorial"]} />
 
-## Overview
+
 
 At a high level, the stages for launching an SNS in production are explained [here](../launching/launch-summary-1proposal.mdx).
 

docs/developer-docs/daos/sns/launching/launch-summary-1proposal.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Advanced", "Governance", "Tutorial"]} />
 
-## Overview
+
 During an SNS launch, a dapp is handed over to the NNS and the NNS both
 creates the SNS canisters and starts a decentralization swap to decentralize the SNS and
 thereby the dapp.

docs/developer-docs/daos/sns/managing/cycles-usage.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Advanced", "Governance", "Concept"]} />
 
-## Overview
+
 :::caution
 An SNS community must ensure that all SNS and dapp canisters
 have sufficient cycles by manually sending cycles when necessary to

docs/developer-docs/daos/sns/managing/making-proposals.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Advanced", "Governance", "Tutorial"]} />
 
-## Overview
+
 
 To manage an SNS, the SNS community needs to understand how proposals work, how they can be submitted, voted on, and what effect they have.
 

docs/developer-docs/daos/sns/managing/manage-sns-intro.mdx

@@ -8,7 +8,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Advanced", "Governance", "Concept"]} />
 
-## Overview
+
 SNSs are protocol-provided DAOs on ICP that are to some extent maintained by the
 NNS community, who for example approve new upgrades of SNS canister code.
 This eliminates much of the maintenance burden from the SNS communities.

docs/developer-docs/daos/sns/managing/managing-nervous-system-parameters.mdx

@@ -9,7 +9,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 <MarkdownChipRow labels={["Advanced", "Governance", "Tutorial"]} />
 
 
-## Overview
+
 
 The nervous system parameters define the settings of a particular SNS.