refactor(canister-calls): rename pages to descriptive titles

marc0olo · marc0olo · commit dc03f486db75 · 2026-04-24T17:22:17.000+02:00
- onchain-calls → inter-canister-calls
- offchain-calls → calling-from-clients
- parallel-calls → parallel-inter-canister-calls (reordered to sidebar position 3)

Updates all cross-references across docs.
diff --git a/docs/concepts/app-architecture.md b/docs/concepts/app-architecture.md
@@ -59,7 +59,7 @@ Separate canisters handle distinct responsibilities. The two-canister setup (fro
 - Request and response payloads are limited to 2 MiB per call.
 - Cross-subnet calls add one consensus round of latency compared to same-subnet calls.
 
-For implementation details and common pitfalls, see [Onchain calls](../guides/canister-calls/onchain-calls.md).
+For implementation details and common pitfalls, see [Inter-canister calls](../guides/canister-calls/inter-canister-calls.md).
 
 ### Canister-per-subnet
 
@@ -101,7 +101,7 @@ Start with the simplest architecture that meets your requirements. You can alway
 ## Next steps
 
 - [Quickstart](../getting-started/quickstart.md): deploy your first application
-- [Onchain calls](../guides/canister-calls/onchain-calls.md): inter-canister communication patterns
+- [Inter-canister calls](../guides/canister-calls/inter-canister-calls.md): inter-canister communication patterns
 - [Asset canister](../guides/frontends/asset-canister.md): frontend deployment
 - [Canisters](canisters.md): canister internals
 
diff --git a/docs/getting-started/choose-your-path.md b/docs/getting-started/choose-your-path.md
@@ -38,7 +38,7 @@ This is where most developers start after the quickstart. The backend guides cov
 - [HTTPS outcalls](../guides/backends/https-outcalls.md): call external APIs from your canister
 - [Timers](../guides/backends/timers.md): schedule recurring tasks
 - [Randomness](../guides/backends/randomness.md): generate unpredictable values onchain
-- [Calling other canisters](../guides/canister-calls/onchain-calls.md): compose functionality across canisters
+- [Calling other canisters](../guides/canister-calls/inter-canister-calls.md): compose functionality across canisters
 
 ## Fullstack applications
 
diff --git a/docs/guides/backends/randomness.md b/docs/guides/backends/randomness.md
@@ -226,6 +226,6 @@ Note: this example predates `mo:core` and uses the older `Random.Finite` API. Th
 - [Onchain Randomness (concept)](../../concepts/onchain-randomness.md): how the IC's threshold VRF works
 - [Management Canister](../../reference/management-canister.md): `raw_rand` API reference
 - [Data Integrity](../security/data-integrity.md): using randomness in a secure application design
-- [Inter-canister calls](../canister-calls/onchain-calls.md): async patterns and reentrancy
+- [Inter-canister calls](../canister-calls/inter-canister-calls.md): async patterns and reentrancy
 
 <!-- Upstream: informed by dfinity/portal — docs/building-apps/integrations/randomness.mdx; dfinity/icskills — skills/canister-security/SKILL.md; dfinity/examples — motoko/random_maze; caffeinelabs/motoko-core — src/Random.mo -->
diff --git a/docs/guides/canister-calls/calling-from-clients.md b/docs/guides/canister-calls/calling-from-clients.md
@@ -1,8 +1,8 @@
 ---
-title: "Offchain Calls"
+title: "Calling from Clients"
 description: "Call canister functions from frontends, scripts, and backend services using IC agent libraries"
 sidebar:
-  order: 3
+  order: 4
 ---
 
 An **agent** is a client-side library that constructs ingress messages, signs them with a cryptographic identity, and sends them to ICP boundary nodes. Agents handle the protocol details (CBOR encoding, request IDs, certificate verification) so your application code works with native language types.
@@ -314,7 +314,7 @@ const agent = await HttpAgent.create({
 ## Next steps
 
 - [Candid and binding generation](candid.md): generate typed clients from `.did` files
-- [Onchain calls](onchain-calls.md): canister-to-canister calls from within the IC
+- [Inter-canister calls](inter-canister-calls.md): canister-to-canister calls from within the IC
 - [Internet Identity](../authentication/internet-identity.md): adding user authentication to offchain calls
 - [Asset canister](../frontends/asset-canister.md): deploying the frontend that makes these calls
 
diff --git a/docs/guides/canister-calls/candid.mdx b/docs/guides/canister-calls/candid.mdx
@@ -291,7 +291,7 @@ console.log(greeting); // "Hello, World!"
 
 ### From another canister
 
-When one canister calls another, Candid handles the argument encoding and response decoding transparently. See [Onchain calls](onchain-calls.md) for how to make inter-canister calls in Motoko and Rust.
+When one canister calls another, Candid handles the argument encoding and response decoding transparently. See [Inter-canister calls](inter-canister-calls.md) for how to make inter-canister calls in Motoko and Rust.
 
 ## Safe interface upgrades
 
@@ -420,7 +420,7 @@ async fn invoke_callee() {
 }
 ```
 
-The `.dynamic_callee("PUBLIC_CANISTER_ID:callee")` mode reads the canister ID from a canister environment variable at runtime. The same `PUBLIC_CANISTER_ID:<name>` variables that `icp deploy` injects (see [canister discovery](onchain-calls.md#canister-discovery)). For canisters with fixed IDs, use `.static_callee(principal)` instead.
+The `.dynamic_callee("PUBLIC_CANISTER_ID:callee")` mode reads the canister ID from a canister environment variable at runtime. The same `PUBLIC_CANISTER_ID:<name>` variables that `icp deploy` injects (see [canister discovery](inter-canister-calls.md#canister-discovery)). For canisters with fixed IDs, use `.static_callee(principal)` instead.
 {/* Needs human verification: the upstream ic-cdk-bindgen README uses ICP_CANISTER_ID: in its example, but icp-cli sets PUBLIC_CANISTER_ID:. We use PUBLIC_CANISTER_ID: here to match icp-cli. An issue has been filed on dfinity/cdk-rs to align the upstream README. */}
 
 For type selector configuration and advanced options, see the [`ic-cdk-bindgen` documentation](https://crates.io/crates/ic-cdk-bindgen).
@@ -443,8 +443,8 @@ For type selector configuration and advanced options, see the [`ic-cdk-bindgen`
 
 ## Next steps
 
-- [Onchain calls](onchain-calls.md): make inter-canister calls using Candid interfaces
-- [Offchain calls](offchain-calls.md): call canisters from JavaScript frontends and agents
+- [Inter-canister calls](inter-canister-calls.md): make inter-canister calls using Candid interfaces
+- [Calling from clients](calling-from-clients.md): call canisters from JavaScript frontends and agents
 - [Candid specification](../../reference/candid-spec.md): full type reference and subtyping rules
 
 {/* Upstream: informed by dfinity/portal docs/building-apps/interact-with-canisters/candid/ (3 files), docs/building-apps/developer-tools/cdks/rust/generating-candid.mdx, icp-cli concepts/binding-generation.md, ic-cdk-bindgen README, and @icp-sdk/bindgen. Type mappings verified against .sources/candid (spec), .sources/motoko (IDL-Motoko.md), and .sources/cdk-rs. */}
diff --git a/docs/guides/canister-calls/inter-canister-calls.mdx b/docs/guides/canister-calls/inter-canister-calls.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Onchain Calls"
+title: "Inter-canister Calls"
 description: "Call functions on other canisters from your canister code"
 sidebar:
   order: 2
@@ -27,7 +27,7 @@ There are two types of canister methods, and the choice affects latency, cost, a
 
 **Use update calls** when modifying state, transferring cycles, or when the caller needs a consensus-backed guarantee that the call was executed correctly.
 
-To make query responses verifiable without the cost of update calls, see [Certified Variables](../backends/certified-variables.md). For running multiple query calls in parallel, see [Parallel Calls and Composite Queries](parallel-calls.md).
+To make query responses verifiable without the cost of update calls, see [Certified Variables](../backends/certified-variables.md). For running multiple query calls in parallel, see [Parallel inter-canister calls](parallel-inter-canister-calls.md).
 
 ## Making calls
 
@@ -398,7 +398,7 @@ Calls between canisters on the same subnet complete within a single round. Cross
 
 ## Next steps
 
-- [Parallel Calls and Composite Queries](parallel-calls.md): make multiple calls concurrently and use composite queries for efficient read patterns
+- [Parallel inter-canister calls](parallel-inter-canister-calls.md): make multiple calls concurrently and use composite queries for efficient read patterns
 - [Candid](candid.md): define the interface your canister exposes for inter-canister calls
 - [Certified Variables](../backends/certified-variables.md): make query responses verifiable without update call overhead
 - [Inter-Canister Call Security](../security/inter-canister-calls.md): reentrancy guards, async safety patterns, and trust considerations
diff --git a/docs/guides/canister-calls/parallel-inter-canister-calls.mdx b/docs/guides/canister-calls/parallel-inter-canister-calls.mdx
@@ -1,8 +1,8 @@
 ---
-title: "Parallel Calls"
+title: "Parallel Inter-canister Calls"
 description: "Execute multiple inter-canister calls concurrently to reduce latency, especially across subnets."
 sidebar:
-  order: 4
+  order: 3
 ---
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';
@@ -355,7 +355,7 @@ Parallel and composite calls carry the same atomicity properties as any inter-ca
 
 ## Next steps
 
-- [Onchain calls](onchain-calls.md): making basic inter-canister calls
+- [Inter-canister calls](inter-canister-calls.md): making basic inter-canister calls
 - [Canister optimization](../canister-management/optimization.md): profiling and improving throughput
 - [Inter-canister call security](../security/inter-canister-calls.md): atomicity, reentrancy, and call safety
 
diff --git a/docs/guides/defi/token-ledgers.mdx b/docs/guides/defi/token-ledgers.mdx
@@ -565,6 +565,6 @@ icp canister call icrc1_ledger icrc1_transfer \
 - [Token standards](../../reference/token-standards.md): formal ICRC-1, ICRC-2, ICRC-7, and ICRC-37 specifications
 - [Chain-key tokens](chain-key-tokens.md): working with ckBTC and ckETH (minting, deposits, withdrawals)
 - [Wallet integration](wallet-integration.md): connecting wallets to your app
-- [Onchain calls](../canister-calls/onchain-calls.md): how inter-canister calls work (ledger calls are inter-canister calls)
+- [Inter-canister calls](../canister-calls/inter-canister-calls.md): how inter-canister calls work (ledger calls are inter-canister calls)
 
 {/* Upstream: informed by dfinity/portal docs/defi/token-standards/, docs/defi/token-integrations/: icrc-1.mdx, icrc-2.mdx, icrc-7.mdx, icrc-37.mdx; dfinity/icskills skills/icrc-ledger/SKILL.md; dfinity/examples motoko/nft-creator */}
diff --git a/docs/guides/security/access-management.mdx b/docs/guides/security/access-management.mdx
@@ -244,7 +244,7 @@ import Runtime "mo:core/Runtime";
 </TabItem>
 <TabItem label="Rust">
 
-In Rust, there is no built-in `is_controller` function: checking controllers requires an async call to the management canister. See [onchain calls](../canister-calls/onchain-calls.md) for inter-canister call patterns.
+In Rust, there is no built-in `is_controller` function: checking controllers requires an async call to the management canister. See [inter-canister calls](../canister-calls/inter-canister-calls.md) for inter-canister call patterns.
 
 </TabItem>
 </Tabs>
diff --git a/docs/guides/security/inter-canister-calls.md b/docs/guides/security/inter-canister-calls.md
@@ -476,8 +476,8 @@ Before shipping any canister that makes inter-canister calls:
 
 ## Next steps
 
-- [Onchain calls](../canister-calls/onchain-calls.md): Basic inter-canister call patterns and the `Call` API
-- [Parallel calls](../canister-calls/parallel-calls.md): Running multiple calls concurrently and handling partial failures
+- [Inter-canister calls](../canister-calls/inter-canister-calls.md): Basic inter-canister call patterns and the `Call` API
+- [Parallel inter-canister calls](../canister-calls/parallel-inter-canister-calls.md): Running multiple calls concurrently and handling partial failures
 - [Security concepts](../../concepts/security.md): IC security model and threat landscape
 
 <!-- Upstream: informed by dfinity/icskills — canister-security/SKILL.md, multi-canister/SKILL.md -->
diff --git a/docs/languages/rust/index.md b/docs/languages/rust/index.md
@@ -204,7 +204,7 @@ Rust canisters compile to `wasm32-unknown-unknown`. Most pure-computation crates
 | Current time | `std::time::Instant` | `ic_cdk::api::time()` returns nanoseconds since the epoch. |
 | Environment variables | `std::env::var` | Not available at runtime. Use `env!()` or `option_env!()` to embed values at compile time. |
 | Random numbers | `rand`, `getrandom` | Use `ic_cdk::management_canister::raw_rand()` for onchain randomness, or implement `getrandom::register_custom_getrandom!` for crates that depend on `getrandom`. |
-| Network I/O | `reqwest`, `hyper` | Use [HTTPS outcalls](../../guides/canister-calls/offchain-calls.md) via the management canister. |
+| Network I/O | `reqwest`, `hyper` | Use [HTTPS outcalls](../../guides/canister-calls/calling-from-clients.md) via the management canister. |
 
 Most crates that target `wasm32-unknown-unknown` for browser use (via `wasm-bindgen` or `wasm-pack`) will **not** work because they depend on JavaScript host bindings that do not exist in the ICP runtime.
 
diff --git a/docs/reference/developer-tools.md b/docs/reference/developer-tools.md
@@ -82,7 +82,7 @@ Community CDKs are maintained independently of DFINITY. Check each project's doc
 
 ## Client libraries
 
-Client libraries handle the protocol details of calling canisters from outside the network: constructing and signing ingress messages, encoding Candid, and verifying responses. For setup and usage patterns, see [Offchain calls](../guides/canister-calls/offchain-calls.md).
+Client libraries handle the protocol details of calling canisters from outside the network: constructing and signing ingress messages, encoding Candid, and verifying responses. For setup and usage patterns, see [Calling from clients](../guides/canister-calls/calling-from-clients.md).
 
 ### JavaScript / TypeScript
 
diff --git a/web3-jargon-issues.txt b/web3-jargon-issues.txt
