diff --git a/04-materials/01-exploring-extensions.md b/04-materials/01-exploring-extensions.md
index fe86333f..47101b43 100644
--- a/04-materials/01-exploring-extensions.md
+++ b/04-materials/01-exploring-extensions.md
@@ -7,7 +7,9 @@
 :::
 
 :::{tip} Terms
-{term}`menu bar`, {term}`main area`, {term}`status bar`, {term}`side panel`
+{term}`extension <extension>`, {term}`plugin <plugin>`, {term}`widget <widget>`,
+{term}`menu bar <menu bar>`, {term}`main area <main area>`,
+{term}`status bar <status bar>`, {term}`side panel <side panel>`
 :::
 
 
@@ -22,6 +24,38 @@
 5. Right {term}`side panel <side panel>`
 
 
+## Extensions and plugins and widgets -- oh, my!
+
+While they sound similar, `extensions <extension>` and {term}`plugins <plugin>` serve
+different purposes.
+
+{term}`Plugins <plugin>` are JupyterLab's fundamental building blocks which define
+functionality and business logic.
+{term}`Extensions <extension>` are the delivery mechanism or "container" for plugins.
+Extensions are the thing that end-users `pip install`.
+
+:::{pull-quote}
+End-users care about extensions, and developers care about plugins.
+:::
+
+A {term}`widget <widget>` is a user interface component provided by a plugin, either for
+the end user to display (e.g. an interactive visualization of data) or for JupyterLab to
+display (e.g. a document viewer that opens when you double-click a particular file
+type).
+
+```{mermaid}
+graph TB
+
+    subgraph Extension["Extension"]
+        subgraph Plugin["Plugin(s) (n>=1)"]
+            Widget["Widget(s) (n>=0)"]
+        end
+    end
+
+    style Widget stroke-dasharray: 5 5
+```
+
+
 ## Extension types
 
 ### {term}`Server extension`
diff --git a/04-materials/02-anatomy-of-extensions.md b/04-materials/02-anatomy-of-extensions.md
index 6caa3418..964042f1 100644
--- a/04-materials/02-anatomy-of-extensions.md
+++ b/04-materials/02-anatomy-of-extensions.md
@@ -13,7 +13,6 @@ In this module, we will:
 :::
 
 :::{tip} Terms
-{term}`extension <extension>`, {term}`plugin <plugin>`, {term}`widget <widget>`,
 {term}`main area widget <main area widget>`, {term}`command <command>`,
 {term}`command palette <command palette>`, {term}`launcher <launcher>`
 :::
@@ -56,7 +55,7 @@ Before we get started, we need to set up:
 * A repository on GitHub
 
 
-### Dependency environment
+### 🔧 Dependency environment
 
 Create an environment named `jupytercon2025`.
 We'll use this environment for the rest of this workshop:
@@ -79,7 +78,7 @@ micromamba install python pip nodejs gh "copier~=9.2" jinja2-time
 ```
 
 
-### Important Git settings
+### 🔧 Important Git settings
 
 1. Git needs to know who you are.
 
@@ -108,7 +107,7 @@ micromamba install python pip nodejs gh "copier~=9.2" jinja2-time
 :::
 
 
-### Create a GitHub repository and clone it locally
+### 🔧 Create a GitHub repository and clone it locally
 
 0. Change to the parent directory where you want to work, e.g.
 
@@ -183,38 +182,6 @@ micromamba install python pip nodejs gh "copier~=9.2" jinja2-time
    **Copy the entire repository URL for the next step!**
 
 
-## Extensions and plugins and widgets -- oh, my!
-
-While they sound similar, `extensions <extension>` and {term}`plugins <plugin>` serve
-different purposes.
-
-{term}`Plugins <plugin>` are JupyterLab's fundamental building blocks which define
-functionality and business logic.
-{term}`Extensions <extension>` are the delivery mechanism or "container" for plugins.
-Extensions are the thing that end-users `pip install`.
-
-:::{pull-quote}
-End-users care about extensions, and developers care about plugins.
-:::
-
-A {term}`widget <widget>` is a user interface component provided by a plugin, either for
-the end user to display (e.g. an interactive visualization of data) or for JupyterLab to
-display (e.g. a document viewer that opens when you double-click a particular file
-type).
-
-```{mermaid}
-graph TB
-
-    subgraph Extension["Extension"]
-        subgraph Plugin["Plugin(s) (n>=1)"]
-            Widget["Widget(s) (n>=0)"]
-        end
-    end
-
-    style Widget stroke-dasharray: 5 5
-```
-
-
 ## What are we building together?
 
 First, we'll examine and demonstrate