fix: update documentation and code references to replace 'demo step' with 'move'

Author: estruyf

docs/.frontmatter/database/mediaDb.json

@@ -94,7 +94,7 @@ message: <message>
 
 ## Set state
 
-The `setState` action allows you to set a key/value pair in the extension state which can be accessed by other actions. You can use the state value in your demo steps by using the following `{STATE_<key>}` syntax.
+The `setState` action allows you to set a key/value pair in the extension state which can be accessed by other actions. You can use the state value in your moves by using the following `{STATE_<key>}` syntax.
 
 <Tabs syncKey="vscode-set-state">
 <TabItem label="JSON">

docs/src/content/docs/actions/vscode.mdx

@@ -264,7 +264,7 @@ For example, if you want to highlight a piece of code, you can select the code a
 2. Search for the **Demo Time: Add scene** command.
 3. Click on the `highlight` action in the command palette.
 
-  <Image class="mx-auto" src={demoStepImage} alt="Add a demo step from the &quot;Demo Time: Add scene&quot; command" />
+  <Image class="mx-auto" src={demoStepImage} alt="Add a move from the &quot;Demo Time: Add scene&quot; command" />
 
 4. Select the act file in which you want to add the step (only if you have multiple act files).
 5. Select if you want to add it to an existing demo or create a new one.

docs/src/content/docs/adding-demos.mdx

@@ -27,7 +27,7 @@ Open the Overview with the command `Demo Time: Overview` from the Command Palett
 From the Overview you can:
 
 - Start a demo or open the demo presenter view.
-- Run a demo step-by-step or jump directly to a slide.
+- Run a scene step-by-step or jump directly to a slide.
 - Open the demo configuration editor for quick edits.
 
 These actions are exposed as toolbar buttons inside the dashboard and can also be triggered via the demo actions and automation steps described elsewhere in the docs.

docs/src/content/docs/features/overview-dashboard.mdx

@@ -87,7 +87,7 @@ import LiveCodingComparison from '../../components/LiveCodingComparison.astro';
 			</CustomCard>
 
 			<CustomCard title="Demo like a pro" icon="rocket">
-				Test your demo steps in advance and ensure everything works perfectly. No more juggling snippets, notes, or worrying about what could go wrong.
+				Test your moves in advance and ensure everything works perfectly. No more juggling snippets, notes, or worrying about what could go wrong.
 
 				<svg xmlns="http://www.w3.org/2000/svg" slot="icon" class="h-6 w-6" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2">
 						<path d="M20 6 9 17l-5-5"/>

docs/src/content/docs/index.mdx

@@ -55,7 +55,7 @@ Once started, Analytics will begin tracking your presentation in the background.
 
 While Analytics is recording, it tracks:
 
-- **Step Timing**: How long you spend on each demo step
+- **Step Timing**: How long you spend on each move
 - **Navigation Patterns**: Which steps you skip, repeat, or spend extra time on
 - **File Interactions**: Which files you open, edit, or reference
 - **Terminal Commands**: Commands you execute in the integrated terminal

docs/src/content/docs/pro-features/analytics.mdx

@@ -112,7 +112,7 @@ This endpoint will execute the previous step in the demo.
 
 ### `/api/notes`
 
-Returns the notes of the current slide or demo step.
+Returns the notes of the current slide or move.
 
 - Method: `GET`
 

docs/src/content/docs/references/api.mdx

@@ -50,7 +50,7 @@ To do this, follow these steps:
 4. Select the folder where you saved the images.
 5. Click on the `Select folder with PowerPoint exported slide images` button.
 6. Choose to create a new act file, or only import the slides.
-    - When you choose to create a new act file. All the slides will be added as demo steps and you are ready to present.
+    - When you choose to create a new act file. All the slides will be added as moves and you are ready to present.
 7. Let the import process finish.
     - If you choose to create a new act file, the import process will open the new act file.
 

docs/src/content/docs/slides/powerpoint-import.mdx

@@ -7,7 +7,7 @@ lastmod: 2025-07-04T18:02:57.716Z
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 
-When you want to insert content to a file, you can use the `content` or `contentPath` properties in the demo step.
+When you want to insert content to a file, you can use the `content` or `contentPath` properties in the move.
 
 | Property | Description |
 | --- | --- |
@@ -90,4 +90,4 @@ insertTypingSpeed: 25
 ```
 
 </TabItem>
-</Tabs>
+</Tabs>

docs/src/content/docs/tips/adding-content.mdx

@@ -6,7 +6,7 @@ lastmod: 2025-01-22T11:25:57.794Z
 
 import { Code } from '@astrojs/starlight/components';
 
-The extension has built-in variables which you can use in your demo steps. These variables are placeholders that get replaced with the actual value when the demo gets executed.
+The extension has built-in variables which you can use in your moves. These variables are placeholders that get replaced with the actual value when the demo gets executed.
 
 - `{DT_INPUT}`: The extension will ask you to provide a value for this variable when the demo gets executed.
 - `{DT_CLIPBOARD}`: The value in your clipboard will be used for this variable.
@@ -16,7 +16,7 @@ The extension has built-in variables which you can use in your demo steps. These
 
 ### Request user input
 
-You can use the `{DT_INPUT}` variable in your demo steps to request user input. When the demo gets executed, the extension will ask you to provide a value for this variable.
+You can use the `{DT_INPUT}` variable in your moves to request user input. When the demo gets executed, the extension will ask you to provide a value for this variable.
 
 <Code code={`
 {
@@ -29,7 +29,7 @@ You can use the `{DT_INPUT}` variable in your demo steps to request user input.
 
 ### Use clipboard content
 
-Similar to the `{DT_INPUT}` variable, you can use the `{DT_CLIPBOARD}` variable in your demo steps to use the value in your clipboard.
+Similar to the `{DT_INPUT}` variable, you can use the `{DT_CLIPBOARD}` variable in your moves to use the value in your clipboard.
 
 <Code code={`
 {
@@ -42,7 +42,7 @@ Similar to the `{DT_INPUT}` variable, you can use the `{DT_CLIPBOARD}` variable
 
 ### Use state value
 
-You can use the `{STATE_<key>}` variable in your demo steps to use the value of the state key which you set via the `setState` action.
+You can use the `{STATE_<key>}` variable in your moves to use the value of the state key which you set via the `setState` action.
 
 <Code code={`
 [
@@ -64,7 +64,7 @@ You can use the `{STATE_<key>}` variable in your demo steps to use the value of
 
 ## Define custom variables
 
-You can define variables in a `variables.json` file in the `.demo` folder. Once you created the `variables.json` file and added variables/constants to it, you can use these variables in your demo steps by using curly braces `{variable_name}`.
+You can define variables in a `variables.json` file in the `.demo` folder. Once you created the `variables.json` file and added variables/constants to it, you can use these variables in your demo moves by using curly braces `{variable_name}`.
 
 ### Example variables file
 
@@ -74,7 +74,7 @@ You can define variables in a `variables.json` file in the `.demo` folder. Once
   lang="json" 
   title={`.demo/variables.json`} />
 
-### Example usage in demo steps
+### Example usage in moves
 
 <Code code={`
 {
@@ -83,4 +83,4 @@ You can define variables in a `variables.json` file in the `.demo` folder. Once
     "args": "{SLIDES_URL}"
 }`} 
   lang="json" 
-  title={`.demo/demo.json`} />
+  title={`.demo/demo.json`} />