Add missing renames

Author: Johannes7k75

docs/introduction/what_is_dockform.md

@@ -5,7 +5,7 @@ title: What is Dockform?
 # What is Dockform?
 
 Dockform extends Docker Compose with a fully declarative workflow.  
-It lets you manage not only your Compose applications, but also the supporting resources that normally sit outside of `docker-compose.yml` — such as external networks, volume lifecycles, secrets, and configuration files.
+It lets you manage not only your Compose stacks, but also the supporting resources that normally sit outside of `docker-compose.yml` — such as external networks, volume lifecycles, secrets, and configuration files.
 
 Think of Dockform as the missing declarative layer for everything you’d otherwise configure manually with commands like `docker network create`, `docker volume create`, or ad-hoc shell scripts. All of it is written as code, stored in a manifest, and applied consistently.
 

docs/more/best_practices.md

@@ -43,7 +43,7 @@ filesets:
       - "**/.DS_Store"
 ```
 
-## Applications and Compose
+## Stacks and Compose
 
 - Set a stable `project.name` for predictable container and network names. See https://docs.docker.com/compose/how-tos/project-name/
 - Keep Compose files close to each app’s `root` folder; avoid cross-tree paths.
@@ -86,7 +86,7 @@ Always ensure you have recent backups for stateful volumes before destructive co
 
 ## Suggested project structure
 
-- Dockform is unopinionated, but grouping applications by folder is effective.
+- Dockform is unopinionated, but grouping stacks by folder is effective.
 
 ```text
 repo/

docs/more/debugging.md

@@ -18,7 +18,7 @@ Dockform provides several diagnostic commands to help you understand what's happ
 |---------|---------|-------------|
 | `dockform doctor` | Environment health check | Setup validation, troubleshooting failures |
 | `dockform manifest render` | Inspect processed manifest | Debug environment interpolation, validate structure |
-| `dockform compose render` | View resolved Compose config | Debug application-specific issues, inspect final output |
+| `dockform compose render` | View resolved Compose config | Debug stack-specific issues, inspect final output |
 | `--log-file` or `--verbose` | View full execution logs | Debug runtime issues |
 
 ## Validation with `doctor`
@@ -103,10 +103,10 @@ $ dockform manifest render | grep identifier
 
 ### Compose rendering
 
-Render the fully-resolved Docker Compose configuration for a specific application as defined in your Dockform manifest. This command:
+Render the fully-resolved Docker Compose configuration for a specific stack as defined in your Dockform manifest. This command:
 
 - **Loads manifest config** (project, profiles, env files, inline env, SOPS).
-- **Resolves application root** and all referenced compose files.
+- **Resolves stack root** and all referenced compose files.
 - **Merges multiple compose files** and normalizes to a single YAML.
 - **Interpolates compose-style variables**: `${VAR}`, `${VAR:-default}`, `${VAR:?err}`.
 - **Respects profiles/extends/anchors** via docker compose config.
@@ -115,7 +115,7 @@ Render the fully-resolved Docker Compose configuration for a specific applicatio
 Usage:
 
 ```bash [shell ~vscode-icons:file-type-shell~]
-# Render an app by name (from your manifest’s applications map)
+# Render an app by name (from your manifest’s stacks map)
 $ dockform compose render myapp
 
 # Optional flags
@@ -173,7 +173,7 @@ Both `manifest render` and `compose render` commands share common behavior patte
   $ dockform compose render api > debug-compose.yml
   
   # Process with jq (if converted to JSON)
-  $ dockform manifest render | yq eval -o=json | jq '.applications'
+  $ dockform manifest render | yq eval -o=json | jq '.stacks'
   ```
 
 ## Logging and verbose output
@@ -273,7 +273,7 @@ For troubleshooting docker compose config errors independently:
 
 1. **Start with environment validation**: `dockform doctor` to ensure all dependencies are properly configured
 2. **Check manifest processing**: `dockform manifest render` to verify environment interpolation
-3. **Inspect application config**: `dockform compose render <app>` to see the final configuration
+3. **Inspect stack config**: `dockform compose render <app>` to see the final configuration
 4. **Test deployment**: `dockform plan` to preview changes before applying
 
 This systematic approach helps identify issues at each layer of Dockform's processing pipeline.

docs/more/snapshots_and_restore.md

@@ -173,7 +173,7 @@ dockform volume restore myapp_data snapshot.tar.zst --stop-containers
 
 2. **Staged approach**: For production restores, consider:
    ```bash
-   # 1. Stop application containers
+   # 1. Stop stack containers
    docker compose stop app
 
    # 2. Restore data volume