Merge remote-tracking branch 'refs/remotes/origin/master' into dfx-0.…

…20.0

# Conflicts:
#	submodules/internetidentity
#	submodules/motoko
#	submodules/response-verfication

docs/developer-docs/web-apps/application-frontends/custom-frontend.mdx

@@ -4,7 +4,7 @@ keywords: [intermediate, tutorial, frontend]
 
 import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
-# Customizing the default frontend canister
+# Customizing the default frontend
 
 <MarkdownChipRow labels={["Intermediate", "Tutorial"]} />
 

docs/developer-docs/web-apps/application-frontends/overview.mdx

@@ -10,6 +10,8 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 Dapps deployed on ICP often utilize a frontend interface to facilitate user interaction with the application. Application frontends include the user interface, webpage, dashboard, or other assets that are displayed in the web browser.
 
+Frontend canisters are also referred to as 'asset canisters', since they are defined as `"type": "asset"` in the `dfx.json` file for a project.
+
 Frontends can exist in the following forms:
 
 - A frontend canister that communicates with backend canister(s) to provide a full-stack dapp. You can learn more by viewing the [default frontend canister](custom-frontend.mdx) and learn how to customize it.
@@ -18,8 +20,6 @@ Frontends can exist in the following forms:
 
 - A frontend canister that doesn't communicate with any backend canisters and only provides web assets such as a website. [Learn more about serving static assets](serving-static-assets).
 
-Frontend canisters are also referred to as asset canisters in the context of ICP.
-
 ## Resources
 
 - [Customize the default frontend canister](./custom-frontend.mdx).

docs/tutorials/developer-journey/level-3/3.2-https-outcalls.mdx

@@ -8,6 +8,8 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Tutorial"]} />
 
+<iframe width="560" height="315" src="https://www.youtube.com/embed/gEyfbFMyhwc?si=2Tmy6FZj-IQ9xU5c" 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>
+
 ## Overview
 
 In the past, blockchain networks were only able to communicate with external servers through blockchain oracles, or third-party entities that relayed calls from the blockchain to an external server, then routed the response back to the blockchain. This is because blockchains are a form of replicated state machine, where each replica must perform the same computations within the same state to make the same transitions each round. Since doing computations with results from an external source may lead to a state divergence, tools like oracles have been used in the past. However, on the Internet Computer, canisters can communicate directly with external servers or other blockchains through **HTTPS outcalls**.

docs/tutorials/developer-journey/level-3/3.3-certified-data.mdx

@@ -8,6 +8,8 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow";
 
 <MarkdownChipRow labels={["Intermediate", "Tutorial"]} />
 
+<iframe width="560" height="315" src="https://www.youtube.com/embed/OztLHEilyuc?si=pEXWrE4fGyMsSBOH" 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>
+
 ## Overview
 
 In a previous module, [2.2: Advanced canister calls](/docs/current/tutorials/developer-journey/level-2/2.2-advanced-canister-calls), you briefly touched on certified variables. In this guide, you'll dive deeper into certified data and take a look at an example that displays how to use certified data.