chore: merge main

peterpeterparker · peterpeterparker · commit 6adbed29fd83 · 2026-01-08T08:40:21.000+01:00
Signed-off-by: David Dal Busco &lt;david.dalbusco@outlook.com&gt;
diff --git a/docs/build/analytics/index.md b/docs/build/analytics/index.md
@@ -110,5 +110,5 @@ Consequently, this leaves the canister open to potential attacks that can pollut
 :::
 
 [CLI]: ../../reference/cli.mdx
-[satellites]: ../../terminology.md#satellite
-[orbiter]: ../../terminology.md#orbiter
+[satellites]: ../../terminology.mdx#satellite
+[orbiter]: ../../terminology.mdx#orbiter
diff --git a/docs/build/datastore/collections.md b/docs/build/datastore/collections.md
@@ -40,5 +40,5 @@ Any collection with read permissions set to `public`, `managed` or `restricted`
 
 :::
 
-[satellite]: ../../terminology.md#satellite
-[controllers]: ../../terminology.md#controller
+[satellite]: ../../terminology.mdx#satellite
+[controllers]: ../../terminology.mdx#controller
diff --git a/docs/build/datastore/index.mdx b/docs/build/datastore/index.mdx
@@ -48,7 +48,7 @@ As for documents, they can be up to 2MB in size. However, larger files can be sa
 
 The Datastore supports various configuration options to fine-tune its behavior, such as resource limits and operational constraints. For a detailed explanation of all available options, see the [configuration](../../reference/configuration.mdx#datastore) section.
 
-[satellite]: ../../terminology.md#satellite
+[satellite]: ../../terminology.mdx#satellite
 
 ---
 
diff --git a/docs/build/functions/index.md b/docs/build/functions/index.md
@@ -14,7 +14,7 @@ keywords:
 
 # Functions
 
-Functions are a set of features enabling developers to extend the native capabilities of [Satellites](../../terminology.md#satellite) using Rust or TypeScript. They let you define serverless behaviors directly within your containerized environment.
+Functions are a set of features enabling developers to extend the native capabilities of [Satellites](../../terminology.mdx#satellite) using Rust or TypeScript. They let you define serverless behaviors directly within your containerized environment.
 
 Triggered by events like document and asset operations, they allow you to automatically run backend code or assertions. These functions are shipped with your container and don’t require you to manage or scale your own servers.
 
diff --git a/docs/build/hosting/development.md b/docs/build/hosting/development.md
@@ -78,4 +78,4 @@ If you're having trouble, feel free to reach out for assistance—we’re happy
 
 If one of the status `Pending...` is reached, the console will automatically refresh the status every few seconds until your domain is available.
 
-[console]: ../../terminology.md#console
+[console]: ../../terminology.mdx#console
diff --git a/docs/build/storage/collections.md b/docs/build/storage/collections.md
@@ -46,4 +46,4 @@ Any collection with read permissions set to `public`, `managed` or `restricted`
 
 :::
 
-[controllers]: ../../terminology.md#controller
+[controllers]: ../../terminology.mdx#controller
diff --git a/docs/build/storage/index.mdx b/docs/build/storage/index.mdx
@@ -61,4 +61,4 @@ import DatastoreVsStorage from "../components/datastore-storage.md";
 
 <DatastoreVsStorage />
 
-[satellite]: ../../terminology.md#satellite
+[satellite]: ../../terminology.mdx#satellite
diff --git a/docs/create-a-satellite.mdx b/docs/create-a-satellite.mdx
@@ -41,4 +41,4 @@ You can change this later in your Satellite "Hosting" settings.
 
 :::
 
-[satellite]: terminology.md#satellite
+[satellite]: terminology.mdx#satellite
diff --git a/docs/faq.md b/docs/faq.md
@@ -69,7 +69,7 @@ In contrast, Juno is fully [open-source](https://github.com/junobuild/), providi
 
 Firebase follows a usage-based pricing model, where costs are calculated based on factors like request volume and data storage. The absence of a cap-setting option is a cause for concern, as unexpected spikes in usage can result in substantial expenses.
 
-In contrast, Juno takes a different approach. Developers pre-charge their modules with [cycles](./terminology.md#cycles), which are then utilized to cover computation and memory usage. This mechanism eliminates the risk of encountering unexpected financial burdens due to unforeseen usage surges.
+In contrast, Juno takes a different approach. Developers pre-charge their modules with [cycles](terminology.mdx#cycles), which are then utilized to cover computation and memory usage. This mechanism eliminates the risk of encountering unexpected financial burdens due to unforeseen usage surges.
 
 ### Do you have a library for [some other language]?
 
@@ -91,6 +91,6 @@ You can also check out the [guides](/docs/category/guides), which feature exampl
 
 Do you have more questions or need further assistance? Feel free to reach out to us on [Discord](https://discord.gg/wHZ57Z2RAG) or [Twitter](https://twitter.com/junobuild). We're here to help!
 
-[mission control]: terminology.md#mission-control
-[satellites]: terminology.md#satellite
+[mission control]: terminology.mdx#mission-control
+[satellites]: terminology.mdx#satellite
 [Internet Computer]: https://internetcomputer.org/
diff --git a/docs/guides/github-actions/index.mdx b/docs/guides/github-actions/index.mdx
@@ -100,5 +100,5 @@ When using the Actions, you can configure the following environment variables:
 | `PROJECT_PATH`       | No        | The path to the folder containing the `juno.config` file if it doesn't exist at the root of your repository. e.g. `./my-app-subfolder`.                                                    |
 
 [CLI]: ../../reference/cli.mdx
-[satellite]: ../../terminology.md#satellite
-[cycles]: ../../terminology.md#cycles
+[satellite]: ../../terminology.mdx#satellite
+[cycles]: ../../terminology.mdx#cycles
diff --git a/docs/management/monitoring.md b/docs/management/monitoring.md
@@ -135,7 +135,7 @@ To enable monitoring, go to the [Monitoring Section](https://console.juno.build/
 The wizard simplifies the setup process, making it easy to configure monitoring according to your needs.
 
 [Analytics]: ../build/analytics/index.md
-[Satellites]: ../terminology.md#satellite
-[Mission Control]: ../terminology.md#mission-control
-[cycles]: ../terminology.md#cycles
-[console]: ../terminology.md#console
+[Satellites]: ../terminology.mdx#satellite
+[Mission Control]: ../terminology.mdx#mission-control
+[cycles]: ../terminology.mdx#cycles
+[console]: ../terminology.mdx#console
diff --git a/docs/management/snapshots.md b/docs/management/snapshots.md
@@ -46,4 +46,4 @@ In addition to standard recovery, snapshots can also be uploaded to reapply the
 
 This should be used carefully though, as snapshots also include elements such as public access keys and user IDs. Applying one module's snapshot to another may cause unintended side effects.
 
-[console]: ../terminology.md#console
+[console]: ../terminology.mdx#console
diff --git a/docs/miscellaneous/access-keys.md b/docs/miscellaneous/access-keys.md
@@ -15,7 +15,7 @@ When you create a [satellite], you and your Mission Control become its owners. P
 :::note
 
 - What was previously referred to as _controllers_ in earlier versions of the documentation is now called _administrative access keys_. The concept remains the same — only the terminology has been updated for clarity and consistency.
-- One access key is identified by a [principal](../terminology.md#principal).
+- One access key is identified by a [principal](../terminology.mdx#principal).
 
 :::
 
@@ -117,6 +117,6 @@ This action will overwrite the previously saved key used to configure your local
 
 :::
 
-[console]: ../terminology.md#console
-[satellite]: ../terminology.md#satellite
-[mission control]: ../terminology.md#mission-control
+[console]: ../terminology.mdx#console
+[satellite]: ../terminology.mdx#satellite
+[mission control]: ../terminology.mdx#mission-control
diff --git a/docs/miscellaneous/architecture.md b/docs/miscellaneous/architecture.md
@@ -95,7 +95,7 @@ While it functions as a CDN, technically it's not a traditional content delivery
 
 Mission Control is your personal management container. It tracks your Satellites and Orbiters, and it acts as your wallet.
 
-You use it for example to spin up new containers or provide [cycles](../terminology.md#cycles) to keep your modules running. It serves as your central hub for managing projects and resources.
+You use it for example to spin up new containers or provide [cycles](../terminology.mdx#cycles) to keep your modules running. It serves as your central hub for managing projects and resources.
 
 Mission Control belongs to you. No one else can access it — not Juno, not the Console, not any other service.
 
diff --git a/docs/miscellaneous/memory.md b/docs/miscellaneous/memory.md
@@ -143,6 +143,6 @@ In any case, the best course of action is to reach out so we can assess your sit
 - [Measure different collection libraries written in Rust](https://dfinity.github.io/canister-profiling/collections/)
 - [Question about freeing/shrinking memory in WebAssembly design](https://github.com/WebAssembly/design/issues/1300)
 
-[satellite]: ../terminology.md#satellite
-[orbiter]: ../terminology.md#orbiter
-[mission control]: ../terminology.md#mission-control
+[satellite]: ../terminology.mdx#satellite
+[orbiter]: ../terminology.mdx#orbiter
+[mission control]: ../terminology.mdx#mission-control
diff --git a/docs/miscellaneous/provisioning-options.mdx b/docs/miscellaneous/provisioning-options.mdx
@@ -48,4 +48,4 @@ import Subnets from "../components/subnets.md";
 
 <Subnets />
 
-[subnet]: terminology.md#subnet
+[subnet]: terminology.mdx#subnet
diff --git a/docs/miscellaneous/wallet.mdx b/docs/miscellaneous/wallet.mdx
@@ -1,6 +1,6 @@
 # Wallet
 
-This section provides guidance on managing your assets and cycles with your [wallet](../terminology.md#wallet), which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.
+This section provides guidance on managing your assets and cycles with your [wallet](../terminology.mdx#wallet), which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.
 
 :::important
 
@@ -38,7 +38,7 @@ It provides independence by allowing you to top up your modules without relying
 
 To get ICP from the outside world into your wallet, you can use most cryptocurrency exchange platforms that allow you to buy ICP (refer to this [list](https://coinranking.com/fr/coin/aMNLwaUbY+internetcomputerdfinity-icp/exchanges) of major ones). These platforms let you convert dollars (or other currencies) into ICP. Keep in mind that exchanges charge a fee for this service.
 
-Once you have obtained ICP on those platforms, you can initiate a transaction to send it to your wallet. For this purpose, you will need to provide a destination address where the ICP should be sent. This destination address corresponds to the [Account Identifier](../terminology.md#account-identifier) of your wallet.
+Once you have obtained ICP on those platforms, you can initiate a transaction to send it to your wallet. For this purpose, you will need to provide a destination address where the ICP should be sent. This destination address corresponds to the [Account Identifier](../terminology.mdx#account-identifier) of your wallet.
 
 You can locate the destination address in Juno's [console]. Once you've logged in, go to your [wallet](https://console.juno.build/wallet) and click "Receive".
 
diff --git a/docs/pricing.md b/docs/pricing.md
@@ -30,7 +30,7 @@ From there, you can dive into the details below to estimate storage, deployment,
 
 As the owner of your Mission Control, Satellites and Orbiters, you are responsible for their operating costs.
 
-To ensure that your infrastructure usage is covered, you must maintain a minimum balance of [cycles](terminology.md#cycles).
+To ensure that your infrastructure usage is covered, you must maintain a minimum balance of [cycles](terminology.mdx#cycles).
 
 You can top up your cycle balance in the Juno [console](https://console.juno.build/) through one of the following methods:
 
@@ -94,6 +94,6 @@ Figures are estimates and may change as the Internet Computer evolves.
 
 :::
 
-[mission control]: terminology.md#mission-control
-[satellite]: terminology.md#satellite
-[orbiter]: terminology.md#orbiter
+[mission control]: terminology.mdx#mission-control
+[satellite]: terminology.mdx#satellite
+[orbiter]: terminology.mdx#orbiter
diff --git a/docs/reference/cli.mdx b/docs/reference/cli.mdx
@@ -185,7 +185,7 @@ import Upgrade from "./cli/upgrade.md";
 
 :::important
 
-- We recommend that you stay current with the Juno releases, as some features may not perform correctly in the [console](../terminology.md#console) if your modules are outdated.
+- We recommend that you stay current with the Juno releases, as some features may not perform correctly in the [console](../terminology.mdx#console) if your modules are outdated.
 - Upgrading requires a stable internet connection for a successful process.
 
 :::
@@ -386,7 +386,7 @@ These config files are created based on the selected `--profile` and `--mode`:
 | `juno[-profile][-mode]-cli-settings` |           | Stores CLI preferences, e.g. whether the access key file is encrypted (to avoid unnecessary prompts). |
 | `juno[-profile][-mode]-cli-state`    |           | Stores ephemeral state like applied config hashes.                                                    |
 
-[satellite]: ../terminology.md#satellite
-[mission control]: ../terminology.md#mission-control
-[principal]: ../terminology.md#principal
-[controller]: ../terminology.md#controller
+[satellite]: ../terminology.mdx#satellite
+[mission control]: ../terminology.mdx#mission-control
+[principal]: ../terminology.mdx#principal
+[controller]: ../terminology.mdx#controller
diff --git a/docs/reference/settings.md b/docs/reference/settings.md
@@ -16,7 +16,7 @@ When a module runs out of cycles, it will be uninstalled, meaning its code and s
 
 This grace period gives developers and users time to react. For sensitive applications, it's common to set a relatively long freezing threshold to ensure there’s enough time to notice a low balance and top up the module before removal
 
-That’s why [Mission Control](../terminology.md#mission-control) (your wallet) and [Satellites](../terminology.md#satellite) (your projects) are spun up with a default freezing threshold of **one year** (360 days), reflecting their high importance.
+That’s why [Mission Control](../terminology.mdx#mission-control) (your wallet) and [Satellites](../terminology.mdx#satellite) (your projects) are spun up with a default freezing threshold of **one year** (360 days), reflecting their high importance.
 
 In contrast, [Analytics](../build/analytics/index.md) modules are considered less critical and are provisioned with a default threshold of **three months** (90 days).
 
@@ -125,6 +125,6 @@ The default value is `0n` - i.e. no particular allocation.
 
 If you set the compute allocation to `50n`, the module will be allocated 50% of the compute capacity. This ensures that the module has a guaranteed share of the compute resources, potentially improving its performance by ensuring it has sufficient processing power for its operations.
 
-[satellites]: ../terminology.md#satellite
-[mission controls]: ../terminology.md#mission-control
-[orbiters]: ../terminology.md#orbiter
+[satellites]: ../terminology.mdx#satellite
+[mission controls]: ../terminology.mdx#mission-control
+[orbiters]: ../terminology.mdx#orbiter
diff --git a/docs/setup-the-sdk.mdx b/docs/setup-the-sdk.mdx
@@ -117,4 +117,4 @@ await initSatellite({
 });
 ```
 
-[satellite]: terminology.md#satellite
+[satellite]: terminology.mdx#satellite
diff --git a/docs/terminology.mdx b/docs/terminology.mdx
@@ -119,10 +119,10 @@ Think of it like a digital vault:
 
 Because your wallet is also your [mission-control](#mission-control), which requires resources to stay alive, we recommend holding a reasonable amount of tokens. Think of it like a day-to-day wallet for frequent operations rather than one for savings.
 
-[console]: terminology.md#console
-[satellite]: terminology.md#satellite
-[satellites]: terminology.md#satellite
-[orbiters]: terminology.md#orbiter
-[mission control]: terminology.md#mission-control
-[mission controls]: terminology.md#mission-control
+[console]: terminology.mdx#console
+[satellite]: terminology.mdx#satellite
+[satellites]: terminology.mdx#satellite
+[orbiters]: terminology.mdx#orbiter
+[mission control]: terminology.mdx#mission-control
+[mission controls]: terminology.mdx#mission-control
 [infrastructure]: miscellaneous/infrastructure.md

Original file line number	Diff line number	Diff line change
`@@ -78,4 +78,4 @@ If you're having trouble, feel free to reach out for assistance—we’re happy`
`78`	`78`
`79`	`79`	If one of the status `Pending...` is reached, the console will automatically refresh the status every few seconds until your domain is available.
`80`	`80`
`81`		`-[console]: ../../terminology.md#console`
	`81`	`+[console]: ../../terminology.mdx#console`
Original file line number	Diff line number	Diff line change
@@ -46,4 +46,4 @@ Any collection with read permissions set to `public`, `managed` or `restricted`
`46`	`46`
`47`	`47`	`:::`
`48`	`48`
`49`		`-[controllers]: ../../terminology.md#controller`
	`49`	`+[controllers]: ../../terminology.mdx#controller`
Original file line number	Diff line number	Diff line change
`@@ -61,4 +61,4 @@ import DatastoreVsStorage from "../components/datastore-storage.md";`
`61`	`61`
`62`	`62`	`<DatastoreVsStorage />`
`63`	`63`
`64`		`-[satellite]: ../../terminology.md#satellite`
	`64`	`+[satellite]: ../../terminology.mdx#satellite`
Original file line number	Diff line number	Diff line change
`@@ -41,4 +41,4 @@ You can change this later in your Satellite "Hosting" settings.`
`41`	`41`
`42`	`42`	`:::`
`43`	`43`
`44`		`-[satellite]: terminology.md#satellite`
	`44`	`+[satellite]: terminology.mdx#satellite`