diff --git a/README.md b/README.md
index 220bf01d62..84b279a1d2 100644
--- a/README.md
+++ b/README.md
@@ -142,11 +142,6 @@ This audience should be kept in mind when writing docs. For example:
### Documentation types
The structure and content of the documentation page will vary based on the document type. Some common types are:
-#### Overview
-An overview of a documentation section or broad concept of ICP. When creating an overview page that discusses the capabilities of ICP, the benefits and attributes of the possible capabilities should be written about, not only the currently implemented workflows. For example, instead of writing about the currently implemented Bitcoin and Ethereum integrations, the [Chain Fusion overview](/docs/current/developer-docs/multi-chain/overview) page discusses ICP’s cross-chain functionalities and benefits on a much broader scale beyond the two current integrations.
-
-For overview pages, using bullet point lists to describe specific benefits or features of ICP is recommended.
-
#### Feature or tool detail page
A page that details a specific tool or feature. Feature or tool pages should provide a deeper explanation of a specific feature or tool, why a developer should use it, and how they can use it. It should describe the currently implemented workflows the feature/tool supports, and should not include details of conceptual ideas that are not currently live for developers to use (future roadmap items, possible improvements in the future, etc.)
diff --git a/docs/developer-docs/daos/sns/overview.mdx b/docs/developer-docs/daos/sns/overview.mdx
index a1bd0de82c..fafd0bf34d 100644
--- a/docs/developer-docs/daos/sns/overview.mdx
+++ b/docs/developer-docs/daos/sns/overview.mdx
@@ -4,7 +4,7 @@ keywords: [advanced, governance, concept, sns, introduction]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# SNS overview
+# What is an SNS?
diff --git a/docs/developer-docs/daos/sns/tokenomics/rewards.mdx b/docs/developer-docs/daos/sns/tokenomics/rewards.mdx
index efb46e8064..13372fe764 100644
--- a/docs/developer-docs/daos/sns/tokenomics/rewards.mdx
+++ b/docs/developer-docs/daos/sns/tokenomics/rewards.mdx
@@ -12,8 +12,6 @@ Each SNS can be individually configured with parameters that define, among other
how an SNS uses rewards to incentivize certain behavior for the governance participants
and the dapp users.
-## Rewards Overview
-
The goal of this article is to explain the design of the SNS reward scheme.
The full potential of tokenization can be unlocked by a tokenized open governance system,
diff --git a/docs/developer-docs/daos/sns/tokenomics/tokenomics-intro.mdx b/docs/developer-docs/daos/sns/tokenomics/tokenomics-intro.mdx
index 97e40fad8e..6587d9bc95 100644
--- a/docs/developer-docs/daos/sns/tokenomics/tokenomics-intro.mdx
+++ b/docs/developer-docs/daos/sns/tokenomics/tokenomics-intro.mdx
@@ -14,8 +14,7 @@ Therefore when launching or maintaining an SNS, it is important to understand to
The described concepts are also relevant for
[other DAOs](../overview#dao-alternatives).
-## Tokenomics overview
-### What is tokenomics?
+## What is tokenomics?
A token is a digital asset on a blockchain. Tokenomics describes the economics of a token system on a blockchain. It is a game changer for decentralized autonomous organization (DAOs) compared to traditional apps running on a Web 2.0 infrastructure, because it enables the introduction of new incentive systems and use cases. Tokenizing a DAO allows, for instance, that anyone in the world can purchase tokens and thereby contribute to initial funding for the DAO. Moreover, tokens can be paid to early adopters and active users, which will help attract users.
Tokenomics covers a wide range of topics, such as
diff --git a/docs/developer-docs/defi/dex/overview.mdx b/docs/developer-docs/defi/dex/overview.mdx
index 1e63f6763d..0d18601552 100644
--- a/docs/developer-docs/defi/dex/overview.mdx
+++ b/docs/developer-docs/defi/dex/overview.mdx
@@ -4,7 +4,7 @@ keywords: [intermediate, defi, overview, dex, decentralized exchange, exchange]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Decentralized exchange overview
+# Decentralized exchanges
diff --git a/docs/developer-docs/defi/nfts/overview.mdx b/docs/developer-docs/defi/nfts/overview.mdx
index 3bb2682546..fd23311933 100644
--- a/docs/developer-docs/defi/nfts/overview.mdx
+++ b/docs/developer-docs/defi/nfts/overview.mdx
@@ -5,7 +5,7 @@ keywords: [intermediate, concept, nfts]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
-# NFT overview
+# NFTs
diff --git a/docs/developer-docs/defi/overview.mdx b/docs/developer-docs/defi/overview.mdx
index 2a1948a148..d85612aefa 100644
--- a/docs/developer-docs/defi/overview.mdx
+++ b/docs/developer-docs/defi/overview.mdx
@@ -5,7 +5,7 @@ keywords: [intermediate, defi, overview, tokens, icrc-1, icrc ledger, icrc index
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
-# Digital assets overview
+# Digital assets
diff --git a/docs/developer-docs/defi/rosetta/icp_rosetta/index.mdx b/docs/developer-docs/defi/rosetta/icp_rosetta/index.mdx
index 5ad4ea9987..9db2b9456d 100644
--- a/docs/developer-docs/defi/rosetta/icp_rosetta/index.mdx
+++ b/docs/developer-docs/defi/rosetta/icp_rosetta/index.mdx
@@ -4,7 +4,7 @@ keywords: [intermediate, rosetta, tutorial, approve, icrc, rosetta]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Overview
+# What is ICP Rosetta?
diff --git a/docs/developer-docs/defi/rosetta/icrc_rosetta/index.mdx b/docs/developer-docs/defi/rosetta/icrc_rosetta/index.mdx
index 1928377ed4..b438a7ff3e 100644
--- a/docs/developer-docs/defi/rosetta/icrc_rosetta/index.mdx
+++ b/docs/developer-docs/defi/rosetta/icrc_rosetta/index.mdx
@@ -4,7 +4,8 @@ keywords: [intermediate, rosetta, tutorial]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Overview
+# What is ICRC Rosetta?
+
The ICRC Rosetta implementation allows for communication with the ICRC-1 compatible ledgers through the [Rosetta-API standard](https://docs.cdp.coinbase.com/mesh/docs/welcome). Examples include the [ckBTC ledger](https://dashboard.internetcomputer.org/canister/mxzaz-hqaaa-aaaar-qaada-cai) and the [ckETH ledger](https://dashboard.internetcomputer.org/canister/ss2fx-dyaaa-aaaar-qacoq-cai).
diff --git a/docs/developer-docs/defi/token_integrations/index.mdx b/docs/developer-docs/defi/token_integrations/index.mdx
index 4b5c591811..5710d20302 100644
--- a/docs/developer-docs/defi/token_integrations/index.mdx
+++ b/docs/developer-docs/defi/token_integrations/index.mdx
@@ -12,8 +12,7 @@ import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
Developers have several options for integrating with the ICP or ICRC-1 ledgers. They can use either the ICRC Rosetta or ICP Rosetta implementations, which is commonly recommended, it might be useful for certain workflows to directly integrate with these ledgers. This section will describe what a direct integration means, how it can be achieved, and how it differs to using Rosetta.
-## Token architecture overview
-
+## Token architecture
Tokens on ICP are managed by smart contracts. The ICP ledger canister manages the list of balances for ICP tokens and implements methods for transferring tokens. It builds a chain of blocks consisting of all ICP token transactions since genesis. The chain is authenticated by having the ICP sign the tip of the chain. External parties can retrieve this chain and verify it is genuine by:
- Verifying the signature which requires the public key of ICP.
diff --git a/docs/developer-docs/defi/tokens/advanced/direct_integration.mdx b/docs/developer-docs/defi/tokens/advanced/direct_integration.mdx
index f857511824..0baf17c00d 100644
--- a/docs/developer-docs/defi/tokens/advanced/direct_integration.mdx
+++ b/docs/developer-docs/defi/tokens/advanced/direct_integration.mdx
@@ -12,8 +12,7 @@ import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
Developers have several options for integrating with the ICP or ICRC-1 ledgers. They can use either the ICP or ICRC Rosetta implementations, which is commonly recommended, although for some workflows, it might be beneficial to directly integrate with these ledgers instead. This section will describe what a direct integration means, how it can be achieved, and how it differs to using Rosetta.
-## Token architecture overview
-
+## Token architecture
Tokens on ICP are managed by smart contracts. The ICP ledger canister manages the list of balances for ICP tokens and implements methods for transferring tokens. It builds a chain of blocks consisting of all ICP token transactions since genesis. The chain is authenticated by having the ICP sign the tip of the chain. External parties can retrieve this chain and verify it is genuine by:
- Verifying the signature using the public key of ICP.
diff --git a/docs/developer-docs/defi/wallets/overview.mdx b/docs/developer-docs/defi/wallets/overview.mdx
index d8a8733fa8..9c58a4b5a0 100644
--- a/docs/developer-docs/defi/wallets/overview.mdx
+++ b/docs/developer-docs/defi/wallets/overview.mdx
@@ -4,7 +4,7 @@ keywords: [beginner, concept, asset custody, self-custody]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Wallet overview
+# Wallets
diff --git a/docs/developer-docs/developer-tools/dev-tools-overview.mdx b/docs/developer-docs/developer-tools/dev-tools-overview.mdx
index d73b3e01c2..f7bdecefa8 100644
--- a/docs/developer-docs/developer-tools/dev-tools-overview.mdx
+++ b/docs/developer-docs/developer-tools/dev-tools-overview.mdx
@@ -4,12 +4,10 @@ keywords: [beginner, developer tools, dev tools, overview]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Developer tool overview
+# Developer tooling
-
-
Developer tools are used to create, manage, and interact with canisters. They can come in several formats, such as command line tools, onchain and off-chain libraries, and integrated development environments. For ICP developers, there are tools within each of these categories available for you to utilize when developing your ICP canisters.
## Command line
diff --git a/docs/developer-docs/developer-tools/off-chain/agents/overview.mdx b/docs/developer-docs/developer-tools/off-chain/agents/overview.mdx
index 6dcf58037e..59b34d2d18 100644
--- a/docs/developer-docs/developer-tools/off-chain/agents/overview.mdx
+++ b/docs/developer-docs/developer-tools/off-chain/agents/overview.mdx
@@ -4,7 +4,7 @@ keywords: [intermediate, agents, overview, javascript, rust, nodejs]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Agents overview
+# What are the ICP agents?
diff --git a/docs/developer-docs/identity/authentication/overview.mdx b/docs/developer-docs/identity/authentication/overview.mdx
index 0531a84618..b53a7e3ca9 100644
--- a/docs/developer-docs/identity/authentication/overview.mdx
+++ b/docs/developer-docs/identity/authentication/overview.mdx
@@ -4,7 +4,7 @@ keywords: [authentication, identity, login, user login, integration]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Authentication overview
+# Integrating authentication into an application
diff --git a/docs/developer-docs/identity/internet-identity/overview.mdx b/docs/developer-docs/identity/internet-identity/overview.mdx
index 9253d6ede7..f1f89af9ef 100644
--- a/docs/developer-docs/identity/internet-identity/overview.mdx
+++ b/docs/developer-docs/identity/internet-identity/overview.mdx
@@ -4,7 +4,7 @@ keywords: [intermediate, concept, user sign in, user login, internet identity]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Internet Identity overview
+# What is Internet Identity?
diff --git a/docs/developer-docs/identity/verifiable-credentials/overview.mdx b/docs/developer-docs/identity/verifiable-credentials/overview.mdx
index 5b399baf13..072d6e2155 100644
--- a/docs/developer-docs/identity/verifiable-credentials/overview.mdx
+++ b/docs/developer-docs/identity/verifiable-credentials/overview.mdx
@@ -4,7 +4,7 @@ keywords: [intermediate, concept, identity, credentials, verifiable credentials]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Verifiable credentials overview
+# What are verifiable credentials?
diff --git a/docs/developer-docs/multi-chain/bitcoin/overview.mdx b/docs/developer-docs/multi-chain/bitcoin/overview.mdx
index 0791743dad..5964cceb27 100644
--- a/docs/developer-docs/multi-chain/bitcoin/overview.mdx
+++ b/docs/developer-docs/multi-chain/bitcoin/overview.mdx
@@ -5,7 +5,7 @@ keywords: [advanced, bitcoin, btc, overview]
import useBaseUrl from "@docusaurus/useBaseUrl";
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Bitcoin integration overview
+# Bitcoin integration
diff --git a/docs/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview.mdx b/docs/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview.mdx
index ad967947c1..550ef60bf1 100644
--- a/docs/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview.mdx
+++ b/docs/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview.mdx
@@ -4,7 +4,7 @@ keywords: [advanced, bitcoin, btc, ckbtc, chain-key bitcoin]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# ckBTC overview
+# ckBTC
diff --git a/docs/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview.mdx b/docs/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview.mdx
index 0751371522..39ce7592d2 100644
--- a/docs/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview.mdx
+++ b/docs/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview.mdx
@@ -5,7 +5,7 @@ keywords: [advanced, ethereum, cketh, erc20, ckerc20, ckusdc, cklink, ckoct, ckp
import useBaseUrl from "@docusaurus/useBaseUrl";
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# ckERC20 overview
+# ckERC20
diff --git a/docs/developer-docs/multi-chain/chain-key-tokens/cketh/overview.mdx b/docs/developer-docs/multi-chain/chain-key-tokens/cketh/overview.mdx
index ad4312c6e9..8522d950fb 100644
--- a/docs/developer-docs/multi-chain/chain-key-tokens/cketh/overview.mdx
+++ b/docs/developer-docs/multi-chain/chain-key-tokens/cketh/overview.mdx
@@ -5,7 +5,7 @@ keywords: [advanced, ethereum, cketh, chain-key ethereum, overview]
import useBaseUrl from "@docusaurus/useBaseUrl";
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# ckETH overview
+# ckETH
diff --git a/docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx b/docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx
index 3e41d08f21..c0581b6752 100644
--- a/docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx
+++ b/docs/developer-docs/multi-chain/chain-key-tokens/overview.mdx
@@ -5,7 +5,7 @@ keywords: [advanced, Chain Fusion, overview, chain-key tokens, cktokens, ck toke
import useBaseUrl from "@docusaurus/useBaseUrl";
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Chain-key token overview
+# Chain-key tokens
diff --git a/docs/developer-docs/multi-chain/ethereum/evm-rpc/overview.mdx b/docs/developer-docs/multi-chain/ethereum/evm-rpc/overview.mdx
index e098135fc1..eb0a6ddc6c 100644
--- a/docs/developer-docs/multi-chain/ethereum/evm-rpc/overview.mdx
+++ b/docs/developer-docs/multi-chain/ethereum/evm-rpc/overview.mdx
@@ -4,11 +4,11 @@ keywords: [advanced, ethereum, evm rpc, evm, tutorial]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# EVM RPC canister overview
+# EVM RPC canister
-**EVM RPC** is an ICP canister smart contract for communicating with [Ethereum](https://ethereum.org/en/) and other [EVM blockchains](https://chainlist.org/?testnets=true) using an onchain API. Communication with EVM-compatible chains includes obtaining and sending information such as:
+The **EVM RPC** canister is used for communicating with [Ethereum](https://ethereum.org/en/) and other [EVM blockchains](https://chainlist.org/?testnets=true) using an onchain API. Communication with EVM-compatible chains includes obtaining and sending information such as:
- The logs of a specific block or transaction.
diff --git a/docs/developer-docs/multi-chain/ethereum/overview.mdx b/docs/developer-docs/multi-chain/ethereum/overview.mdx
index 8dc24bf43e..279eb0e043 100644
--- a/docs/developer-docs/multi-chain/ethereum/overview.mdx
+++ b/docs/developer-docs/multi-chain/ethereum/overview.mdx
@@ -4,7 +4,7 @@ keywords: [advanced, ethereum, overview]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Ethereum integration overview
+# Ethereum & EVM integration
diff --git a/docs/developer-docs/multi-chain/overview.mdx b/docs/developer-docs/multi-chain/overview.mdx
index 4a1352fd7f..1056c4a6e3 100644
--- a/docs/developer-docs/multi-chain/overview.mdx
+++ b/docs/developer-docs/multi-chain/overview.mdx
@@ -8,7 +8,7 @@ import TabItem from "@theme/TabItem";
import { AdornedTabs } from "/src/components/Tabs/AdornedTabs";
import { AdornedTab } from "/src/components/Tabs/AdornedTab";
-# Chain Fusion overview
+# What is Chain Fusion?
diff --git a/docs/developer-docs/security/security-best-practices/overview.mdx b/docs/developer-docs/security/security-best-practices/overview.mdx
index 6d403f6e0e..b905431e1a 100644
--- a/docs/developer-docs/security/security-best-practices/overview.mdx
+++ b/docs/developer-docs/security/security-best-practices/overview.mdx
@@ -4,7 +4,7 @@ keywords: [security, concept]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Overview
+# What are security best practices?
diff --git a/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-overview.mdx b/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-overview.mdx
index 0f0ecd89fc..1dcbcfd875 100644
--- a/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-overview.mdx
+++ b/docs/developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-overview.mdx
@@ -4,11 +4,11 @@ keywords: [https outcalls, advanced, concept]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# HTTPS outcalls overview
+# What are HTTPS outcalls?
-Canister smart contracts can make a request to a URL using [HTTPS outcalls](https://internetcomputer.org/https-outcalls). HTTPS outcalls can be used to directly obtain off-chain data or interact with off-chain systems, such as Web 2.0 services or enterprise IT infrastructure.
+Canisterscan make a request to a URL using [HTTPS outcalls](https://internetcomputer.org/https-outcalls). HTTPS outcalls can be used to directly obtain off-chain data or interact with off-chain systems, such as Web 2.0 services or enterprise IT infrastructure.
HTTPS outcalls enable a wide range of applications. For example, oracle services can directly integrate with ICP in a trustless manner, and dapps can provide user notifications or anything else that requires communication with servers on the Internet.
diff --git a/docs/developer-docs/smart-contracts/call/overview.mdx b/docs/developer-docs/smart-contracts/call/overview.mdx
index 5ef5910778..20bfde5816 100644
--- a/docs/developer-docs/smart-contracts/call/overview.mdx
+++ b/docs/developer-docs/smart-contracts/call/overview.mdx
@@ -9,7 +9,7 @@ import { BetaChip } from "/src/components/Chip/BetaChip";
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
-# Call overview
+# Calling canisters
diff --git a/docs/developer-docs/smart-contracts/deploy/overview.mdx b/docs/developer-docs/smart-contracts/deploy/overview.mdx
index 0185a6c09a..8753c55cdd 100644
--- a/docs/developer-docs/smart-contracts/deploy/overview.mdx
+++ b/docs/developer-docs/smart-contracts/deploy/overview.mdx
@@ -10,7 +10,7 @@ import { BetaChip } from "/src/components/Chip/BetaChip";
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
-# Deploy overview
+# Deploying canisters
diff --git a/docs/developer-docs/smart-contracts/encryption/vetkeys.mdx b/docs/developer-docs/smart-contracts/encryption/vetkeys.mdx
index 180abbdb57..74bd09fd28 100644
--- a/docs/developer-docs/smart-contracts/encryption/vetkeys.mdx
+++ b/docs/developer-docs/smart-contracts/encryption/vetkeys.mdx
@@ -4,7 +4,7 @@ keywords: [advanced, concept, vetkd, vetkeys]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Overview
+# What are vetKeys?
diff --git a/docs/developer-docs/smart-contracts/test/overview.mdx b/docs/developer-docs/smart-contracts/test/overview.mdx
index 65f8e6da18..f9967c2725 100644
--- a/docs/developer-docs/smart-contracts/test/overview.mdx
+++ b/docs/developer-docs/smart-contracts/test/overview.mdx
@@ -6,9 +6,9 @@ keywords: [intermediate, test, tutorial, test code, test canister, pocket ic, po
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
-# Testing canisters overview
+# Testing canisters
-
+
Testing your canister's code during the development process is an important step to verify that the code operates as expected and does not produce bugs, errors, or result in the canister trapping. Before deploying and using the code in a production environment, it should undergo testing.
diff --git a/docs/developer-docs/web-apps/application-frontends/overview.mdx b/docs/developer-docs/web-apps/application-frontends/overview.mdx
index c771a6e590..c64548f258 100644
--- a/docs/developer-docs/web-apps/application-frontends/overview.mdx
+++ b/docs/developer-docs/web-apps/application-frontends/overview.mdx
@@ -5,7 +5,7 @@ keywords: [beginner, concept, frontend, asset canister, assets]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
-# Asset canister overview
+# What is an asset canister?
diff --git a/docs/references/asset-canister.mdx b/docs/references/asset-canister.mdx
index 2f47381dbe..bfed083dc9 100644
--- a/docs/references/asset-canister.mdx
+++ b/docs/references/asset-canister.mdx
@@ -4,8 +4,6 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-## Overview
-
An [asset canister](https://github.com/dfinity/sdk/tree/master/src/canisters/frontend/ic-frontend-canister), also referred to as a 'frontend canister' is a type of canister deployed on ICP that can be used to store and retrieve an application's frontend, typically used to serve static HTML, JS, and CSS assets.
## Architecture reference
diff --git a/docs/references/bitcoin-how-it-works.mdx b/docs/references/bitcoin-how-it-works.mdx
index 0dc2d99b1d..42120ca9c8 100644
--- a/docs/references/bitcoin-how-it-works.mdx
+++ b/docs/references/bitcoin-how-it-works.mdx
@@ -4,8 +4,6 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-## Overview
-
The Bitcoin integration on the Internet Computer allows for direct and trustless interaction with the Bitcoin network, enabling canister smart contracts to create Bitcoin addresses and send and receive bitcoin directly. This opens up new possibilities for decentralized applications and services, such as DeFi, that can leverage the liquidity and security of Bitcoin without relying on centralized bridges, thereby enhancing security and efficiency.
Two advanced engineering challenges needed to be solved to enable Bitcoin smart contracts on ICP:
diff --git a/docs/references/candid-ref.mdx b/docs/references/candid-ref.mdx
index 03f6e894cf..eaa14b0b62 100644
--- a/docs/references/candid-ref.mdx
+++ b/docs/references/candid-ref.mdx
@@ -4,8 +4,6 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-## Overview
-
This document provides detailed reference information about Candid supported types and links to the Candid specification and documentation for the Candid Rust crate.
- [Supported types](#supported-types).
diff --git a/docs/references/dashboard/overview.mdx b/docs/references/dashboard/overview.mdx
index 3c1f313ac7..e7231ce76b 100644
--- a/docs/references/dashboard/overview.mdx
+++ b/docs/references/dashboard/overview.mdx
@@ -5,7 +5,7 @@ keywords: [ICP dashboard, dashboard, icp dashboard]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
import { GlossaryTooltip } from "/src/components/Tooltip/GlossaryTooltip";
-# ICP dashboard overview
+# Using the ICP dashboard
diff --git a/docs/references/execution-errors.mdx b/docs/references/execution-errors.mdx
index 49c4e00533..c1a001ffe0 100644
--- a/docs/references/execution-errors.mdx
+++ b/docs/references/execution-errors.mdx
@@ -8,7 +8,6 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-## Overview
A list of possible errors returned when executing canisters.
## Errors
diff --git a/docs/references/https-outcalls-how-it-works.mdx b/docs/references/https-outcalls-how-it-works.mdx
index 5d751072b3..51e44539eb 100644
--- a/docs/references/https-outcalls-how-it-works.mdx
+++ b/docs/references/https-outcalls-how-it-works.mdx
@@ -4,8 +4,6 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-## Overview
-
This page provides details on how canister HTTPS outcalls, or canister HTTP requests, work and important aspects to consider when using the API. You also want to note that there are some limitations and differences compared to regular (Web 2.0) computer programs making HTTP calls and considerations for programmers for successfully using this feature. Engineers who intend to use this feature are advised to read through this page to get up to speed quickly w.r.t. the feature. The impatient reader who wants to dive into coding right away can skip the conceptual part and jump right away to the [coding section](#coding-https-outcalls) to get started.
## Architecture
diff --git a/docs/references/node-providers/overview.mdx b/docs/references/node-providers/overview.mdx
index 672402929b..1d2620a557 100644
--- a/docs/references/node-providers/overview.mdx
+++ b/docs/references/node-providers/overview.mdx
@@ -4,7 +4,7 @@ keywords: [references, node providers, nodes ]
import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-# Node provider overview
+# Node provider resources
diff --git a/sidebars.js b/sidebars.js
index f3df47c544..58489500ff 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -66,7 +66,7 @@ const sidebars = {
items: [
{
type: "category",
- label: "Overview",
+ label: "What are canister smart contracts?",
items: [
"developer-docs/smart-contracts/overview/introduction",
"developer-docs/smart-contracts/overview/inside-canisters",
@@ -104,24 +104,22 @@ const sidebars = {
{
type: "category",
label: "Deploy",
+ link: {
+ type: "doc",
+ id: "developer-docs/smart-contracts/deploy/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/smart-contracts/deploy/overview",
- },
"developer-docs/smart-contracts/deploy/custom-testnets",
],
},
{
type: "category",
label: "Call",
+ link: {
+ type: "doc",
+ id: "developer-docs/smart-contracts/call/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/smart-contracts/call/overview",
- },
{
type: "doc",
label: "Async code & inter-canister calls",
@@ -182,12 +180,11 @@ const sidebars = {
{
type: "category",
label: "Test",
+ link: {
+ type: "doc",
+ id: "developer-docs/smart-contracts/test/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/smart-contracts/test/overview",
- },
"developer-docs/smart-contracts/test/pocket-ic",
],
},
@@ -210,12 +207,11 @@ const sidebars = {
{
type: "category",
label: "HTTPS outcalls",
+ link: {
+ type: "doc",
+ id: "developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-overview",
- },
"developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-how-to-use",
"developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-get",
"developer-docs/smart-contracts/advanced-features/https-outcalls/https-outcalls-post",
@@ -318,12 +314,11 @@ const sidebars = {
{
type: "category",
label: "Developer tools",
+ link: {
+ type: "doc",
+ id: "developer-docs/developer-tools/dev-tools-overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/developer-tools/dev-tools-overview",
- },
{
type: "category",
label: "Command line",
@@ -476,12 +471,11 @@ const sidebars = {
{
type: "category",
label: "Agents",
+ link: {
+ type: "doc",
+ id: "developer-docs/developer-tools/off-chain/agents/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/developer-tools/off-chain/agents/overview",
- },
"developer-docs/developer-tools/off-chain/agents/javascript-agent",
"developer-docs/developer-tools/off-chain/agents/nodejs",
"developer-docs/developer-tools/off-chain/agents/rust-agent",
@@ -520,12 +514,11 @@ const sidebars = {
{
type: "category",
label: "Application frontends",
+ link: {
+ type: "doc",
+ id: "developer-docs/web-apps/application-frontends/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/web-apps/application-frontends/overview",
- },
"developer-docs/web-apps/application-frontends/default-frontend",
"developer-docs/web-apps/application-frontends/existing-frontend",
"developer-docs/web-apps/application-frontends/asset-security",
@@ -555,12 +548,11 @@ const sidebars = {
{
type: "category",
label: "Security best practices",
+ link: {
+ type: "doc",
+ id: "developer-docs/security/security-best-practices/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/security/security-best-practices/overview",
- },
{
type: "doc",
label: "Inter-canister calls",
@@ -628,22 +620,20 @@ const sidebars = {
{
type: "category",
label: "Chain Fusion",
+ link: {
+ type: "doc",
+ id: "developer-docs/multi-chain/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/multi-chain/overview",
- },
"developer-docs/multi-chain/supported-chains",
{
type: "category",
label: "Bitcoin",
+ link: {
+ type: "doc",
+ id: "developer-docs/multi-chain/bitcoin/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/multi-chain/bitcoin/overview",
- },
"developer-docs/multi-chain/bitcoin/using-btc/btc-comparison",
"developer-docs/multi-chain/bitcoin/using-btc/btc-dev-workflow",
{
@@ -665,12 +655,11 @@ const sidebars = {
{
type: "category",
label: "Ethereum",
+ link: {
+ type: "doc",
+ id: "developer-docs/multi-chain/ethereum/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/multi-chain/ethereum/overview",
- },
"developer-docs/multi-chain/ethereum/using-eth/eth-comparison",
"developer-docs/multi-chain/ethereum/using-eth/eth-dev-workflow",
{
@@ -685,12 +674,11 @@ const sidebars = {
{
type: "category",
label: "EVM RPC canister",
+ link: {
+ type: "doc",
+ id: "developer-docs/multi-chain/ethereum/evm-rpc/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/multi-chain/ethereum/evm-rpc/overview",
- },
"developer-docs/multi-chain/ethereum/evm-rpc/how-it-works",
"developer-docs/multi-chain/ethereum/evm-rpc/evm-rpc-canister",
"developer-docs/multi-chain/ethereum/evm-rpc/costs",
@@ -703,17 +691,19 @@ const sidebars = {
{
type: "category",
label: "Chain-key tokens",
+ link: {
+ type: "doc",
+ id: "developer-docs/multi-chain/chain-key-tokens/overview",
+ },
items: [
- "developer-docs/multi-chain/chain-key-tokens/overview",
{
type: "category",
label: "ckBTC",
+ link: {
+ type: "doc",
+ id: "developer-docs/multi-chain/chain-key-tokens/ckbtc/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/multi-chain/chain-key-tokens/ckbtc/overview",
- },
"developer-docs/multi-chain/chain-key-tokens/ckbtc/making-transactions",
"developer-docs/multi-chain/chain-key-tokens/ckbtc/using-ckbtc-in-dapps",
],
@@ -721,12 +711,11 @@ const sidebars = {
{
type: "category",
label: "ckETH",
+ link: {
+ type: "doc",
+ id: "developer-docs/multi-chain/chain-key-tokens/cketh/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/multi-chain/chain-key-tokens/cketh/overview",
- },
"developer-docs/multi-chain/chain-key-tokens/cketh/making-transactions",
"developer-docs/multi-chain/chain-key-tokens/cketh/using-cketh-in-dapps",
],
@@ -734,12 +723,11 @@ const sidebars = {
{
type: "category",
label: "ckERC20",
+ link: {
+ type: "doc",
+ id: "developer-docs/multi-chain/chain-key-tokens/ckerc20/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/multi-chain/chain-key-tokens/ckerc20/overview",
- },
"developer-docs/multi-chain/chain-key-tokens/ckerc20/making-transactions",
"developer-docs/multi-chain/chain-key-tokens/ckerc20/using-ckerc20-in-dapps",
"developer-docs/multi-chain/chain-key-tokens/ckerc20/creating-new-ckerc20",
@@ -752,21 +740,19 @@ const sidebars = {
{
type: "category",
label: "Authentication",
+ link: {
+ type: "doc",
+ id: "developer-docs/identity/authentication/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/identity/authentication/overview",
- },
{
type: "category",
label: "Internet Identity (II)",
+ link: {
+ type: "doc",
+ id: "developer-docs/identity/internet-identity/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/identity/internet-identity/overview",
- },
"developer-docs/identity/internet-identity/creating-ii",
"developer-docs/identity/internet-identity/integrate-internet-identity",
"developer-docs/identity/internet-identity/alternative-origins",
@@ -775,12 +761,11 @@ const sidebars = {
{
type: "category",
label: "Verifiable credentials",
+ link: {
+ type: "doc",
+ id: "developer-docs/identity/verifiable-credentials/overview",
+ },
items: [
- {
- label: "Overview",
- type: "doc",
- id: "developer-docs/identity/verifiable-credentials/overview",
- },
"developer-docs/identity/verifiable-credentials/how-it-works",
"developer-docs/identity/verifiable-credentials/issuer",
"developer-docs/identity/verifiable-credentials/relying-party",
@@ -791,12 +776,11 @@ const sidebars = {
{
type: "category",
label: "Digital assets",
+ link: {
+ type: "doc",
+ id: "developer-docs/defi/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/defi/overview",
- },
{
type: "category",
label: "Tokens",
@@ -984,12 +968,11 @@ const sidebars = {
{
type: "category",
label: "NFTs",
+ link: {
+ type: "doc",
+ id: "developer-docs/defi/nfts/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/defi/nfts/overview",
- },
"developer-docs/defi/nfts/nft-collections",
"developer-docs/defi/nfts/marketplaces"
],
@@ -997,23 +980,21 @@ const sidebars = {
{
type: "category",
label: "Decentralized exchanges",
+ link: {
+ type: "doc",
+ id: "developer-docs/defi/dex/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/defi/dex/overview",
- }
],
},
{
type: "category",
label: "Wallets",
+ link: {
+ type: "doc",
+ id: "developer-docs/defi/wallets/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/defi/wallets/overview",
- },
"developer-docs/defi/wallets/self-custody/self-custody-quickstart",
"developer-docs/defi/wallets/self-custody/hardware-wallet-cli",
],
@@ -1023,21 +1004,19 @@ const sidebars = {
{
type: "category",
label: "Decentralized AI",
+ link: {
+ type: "doc",
+ id: "developer-docs/ai/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/ai/overview",
- },
{
type: "category",
label: "Inference",
+ link: {
+ type: "doc",
+ id: "developer-docs/ai/inference",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/ai/inference",
- },
"developer-docs/ai/samples",
],
},
@@ -1051,12 +1030,11 @@ const sidebars = {
{
type: "category",
label: "Network Nervous System (NNS)",
+ link: {
+ type: "doc",
+ id: "developer-docs/daos/nns/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "developer-docs/daos/nns/overview",
- },
{
type: "category",
label: "Using the NNS dapp",
@@ -1113,7 +1091,7 @@ const sidebars = {
},
items: [
{
- label: "Overview",
+ label: "What is an SNS?",
type: "doc",
id: "developer-docs/daos/sns/overview",
},
@@ -1256,12 +1234,11 @@ const sidebars = {
{
type: "category",
label: "ICP dashboard",
+ link: {
+ type: "doc",
+ id: "references/dashboard/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "references/dashboard/overview",
- },
"references/dashboard/using-the-dashboard",
"references/dashboard/dashboard-apis",
],
@@ -1280,24 +1257,22 @@ const sidebars = {
{
type: "category",
label: "Node providers",
+ link: {
+ type: "doc",
+ id: "references/node-providers/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "references/node-providers/overview",
- },
"references/node-providers/node-metrics",
],
},
{
type: "category",
label: "Subnets",
+ link: {
+ type: "doc",
+ id: "references/subnets/overview",
+ },
items: [
- {
- type: "doc",
- label: "Overview",
- id: "references/subnets/overview",
- },
"references/subnets/subnet-types",
],
},
diff --git a/style-guide.md b/style-guide.md
index 282f0d67ff..9a1ad8051b 100644
--- a/style-guide.md
+++ b/style-guide.md
@@ -1,6 +1,6 @@
-# Dev Docs Style Guide
+# ICP Developer Documentation style guide
-## Overview
+## Purpose of this guide
This guide outlines the format, language, and style that should be used when contributing pages to the Internet Computer developer documentation. This is designed to assist with standardizing the documentation to create a cohesive, uniform look and feel across all pages of documentation that have been contributed by multiple individuals and teams.
@@ -21,7 +21,7 @@ This guide will outline the following:
## Page structure
-The developers docs contain a wide variety of different document types, such as overview pages, concept pages, feature pages, tutorials, and reference pages. For this reason, the page structure will vary based on what type of document the page is.
+The developers docs contain a wide variety of different document types, such as introduction pages, concept pages, feature pages, tutorials, and reference pages. For this reason, the page structure will vary based on what type of document the page is.
The following example template can be used:
@@ -36,8 +36,6 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
-## Overview
-
Introduce the feature or tool. What is it? Give a brief overview of how it works, but keep it very high level. Link to additional documents that explain the in-depth concepts behind it (if they exist).
## Prerequisites
@@ -45,9 +43,15 @@ Introduce the feature or tool. What is it? Give a brief overview of how it works
Optional; only necessary for documents that require prerequisite conditions or parameters be met.
List all dependencies that the developer will need to download or setup in order to use the feature. The most common prerequisite is downloading dfx. Please link to the dfx installation page.
-- [x] Prerequisite 1.
-- [x] Prerequisite 2.
-- [x] Prerequisite 3.
+
+
+
+
+Before you start, verify that you have:
+ Install the IC SDK.
+
+
+
## Topic 1
@@ -90,7 +94,7 @@ There are 4 types of headings used throughout the ICP developer docs:
| Heading size | Usage |
|--------------|-------|
| Heading 1 | Page title only; not used within the page's content.|
-| Heading 2 | Used for primary topics amongst the page; used for consistent page headings such as 'Overview', 'Prerequisites', 'Conclusion' and 'References'.|
+| Heading 2 | Used for primary topics amongst the page; used for consistent page headings such as 'Prerequisites', 'Conclusion' and 'References'.|
| Heading 3 | Used for subtopics under primary topics amongst the page or user steps within a tutorial. Note; there are some instances where using Heading 2 for a tutorial step is more fitting, such as when a step contains several different concepts or subtopics. Please refer to the writing a tutorial section below for further information.|
| Heading 4 | Used for listing steps a user should take within a guide document, where the guide document includes several different, separate walkthroughs for the user to follow; in this scenario, this heading should be used in conjunction with a bullet point. Heading 4 is also used for listing terms within the `glossary` document page and for subtopics under an already existing Heading 3 subtopic heading. |
@@ -101,8 +105,6 @@ The following is a sample guide document that showcases how the 4 types of headi
```
# File management
-## Overview
-
This document describes basic file management workflows.
### Workflows covered
@@ -156,7 +158,6 @@ Capitalization within the developer documentation should follow these outlined s
- Example: Using Internet Identity with a dapp
- Example: Motoko reference guide
- Only the first word of a page heading should be capitalized unless the title includes a proper noun.
- - Example: Overview
- Example: Register, build, and deploy the dapp
- Example: Using Motoko canisters
- Titles of links to other documentation pages or external articles, such as blog posts, should not be capitalized except for the proper nouns within the title.