docs: general updates and fixed links (#80)

dieppa · web-flow · commit c0d3cf6b4ccb · 2025-09-15T21:28:29.000+01:00
diff --git a/docs/audit-stores/community/couchbase-audit-store.md b/docs/audit-stores/community/couchbase-audit-store.md
@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 This page explains how to configure **Couchbase** as Flamingock's audit store.  
 The audit store is where Flamingock records execution history and ensures safe coordination across distributed deployments.
 
-> For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../overview/audit-store-vs-target-system.md).
+> For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../../overview/audit-store-vs-target-system.md).
 
 
 ## Minimum setup
@@ -157,5 +157,5 @@ Flamingock.builder()
 
 ## Next steps
 
-- Learn about [Target systems](../flamingock-library-config/target-system-configuration.md)  
+- Learn about [Target systems](../../target-systems/introduction.md)  
 - 👉 See a [full example project](https://github.com/flamingock/flamingock-examples/tree/master/couchbase)
diff --git a/docs/audit-stores/community/dynamodb-audit-store.md b/docs/audit-stores/community/dynamodb-audit-store.md
@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 This page explains how to configure **Amazon DynamoDB** as Flamingock's audit store.
 The audit store is where Flamingock records execution history and ensures safe coordination across distributed deployments.
 
-> For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../overview/audit-store-vs-target-system.md).
+> For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../../overview/audit-store-vs-target-system.md).
 
 
 ## Minimum setup
@@ -161,5 +161,5 @@ Consider using **ON_DEMAND** billing mode for unpredictable workloads.
 
 ## Next steps
 
-- Learn about [Target systems](../flamingock-library-config/target-system-configuration.md)  
+- Learn about [Target systems](../../target-systems/introduction.md)  
 - 👉 See a [full example project](https://github.com/flamingock/flamingock-examples/tree/master/dynamodb)
diff --git a/docs/audit-stores/community/mongodb-audit-store.md b/docs/audit-stores/community/mongodb-audit-store.md
@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 This page explains how to configure **MongoDB** as Flamingock's audit store.
 The audit store is where Flamingock records execution history and ensures safe coordination across distributed deployments.
 
-> For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../overview/audit-store-vs-target-system.md).
+> For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../../overview/audit-store-vs-target-system.md).
 
 
 ## Minimum setup
@@ -179,5 +179,5 @@ Recommended only for dev/test environments.
 
 ## Next steps
 
-- Learn about [Target systems](../targetsystems/configuration.md)  
+- Learn about [Target systems](../../target-systems/introduction.md)  
 - 👉 See a [full example project](https://github.com/flamingock/flamingock-examples/tree/master/mongodb)  
diff --git a/docs/audit-stores/community/mongodb-springdata-audit-store.md b/docs/audit-stores/community/mongodb-springdata-audit-store.md
@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 This page explains how to configure **MongoDB with Spring Data** as Flamingock's audit store.
 The audit store is where Flamingock records execution history and ensures safe coordination across distributed deployments.
 
-> For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../overview/audit-store-vs-target-system.md).
+> For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../../overview/audit-store-vs-target-system.md).
 
 
 ## Minimum setup
@@ -211,5 +211,5 @@ Spring Boot will automatically:
 
 ## Next steps
 
-- Learn about [Target systems](../flamingock-library-config/target-system-configuration.md)  
+- Learn about [Target systems](../../target-systems/introduction.md)  
 - 👉 See a [full example project](https://github.com/flamingock/flamingock-examples/tree/master/mongodb-springdata)
diff --git a/docs/audit-stores/introduction.md b/docs/audit-stores/introduction.md
@@ -18,16 +18,21 @@ Unlike target systems (which your code modifies), the audit store is managed aut
 
 > **Conceptual overview**: For architectural understanding, see [Target systems vs audit store](../overview/audit-store-vs-target-system.md)
 
-## Supported audit stores
+## Audit store options
 
-Flamingock supports several databases as audit stores:
+### Cloud Edition
+The audit store is **automatically provided and managed** by Flamingock Cloud. No configuration needed - just focus on your changes while Flamingock handles the audit infrastructure.
+
+### Community setup
+Alternatively, you can configure your own audit store using one of the supported databases:
 
 - [MongoDB audit store](./community/mongodb-audit-store.md)
 - [MongoDB Spring Data audit store](./community/mongodb-springdata-audit-store.md)
-- [DynamoDB audit store](./community/dynamodb-audit-store.md)  
+- [DynamoDB audit store](./community/dynamodb-audit-store.md)
 - [Couchbase audit store](./community/couchbase-audit-store.md)
 
-### Configuration pattern
+
+### Community configuration pattern
 
 Register the audit store with the Flamingock builder:
 
diff --git a/docs/change-units/introduction.md b/docs/change-units/introduction.md
@@ -74,4 +74,4 @@ Dive deeper into specific aspects of ChangeUnits:
 
 Or continue to other key concepts:
 - **[Target Systems](../target-systems/introduction.md)** - Configure where your changes will be applied
-- **[Templates](../templates/introduction.md)** - Explore reusable change patterns
+- **[Templates](../templates/templates-introduction.md)** - Explore reusable change patterns
diff --git a/docs/frameworks/springboot-integration/builder-based-setup.md b/docs/frameworks/springboot-integration/builder-based-setup.md
@@ -87,7 +87,7 @@ FlamingockBuilder builder = Flamingock
 
 :::info
 Platform components are registered using the same `.addDependency(...)` method used for change unit dependencies.  
-For details, see the [Platform component injection](../../flamingock-library-config/platform-component-injection.md) page.
+For details, see the [Context and dependencies](../../flamingock-library-config/context-and-dependencies.md) page.
 :::
 ## Overriding Spring-provided dependencies
 When using the builder-based setup, Flamingock will attempt to resolve dependencies using the Spring context.
diff --git a/docs/frameworks/springboot-integration/introduction.md b/docs/frameworks/springboot-integration/introduction.md
@@ -120,7 +120,7 @@ implementation("io.flamingock:flamingock-springboot-integration-v2-legacy:$flami
 
 Flamingock provides two editions for Spring Boot integration.
 
-### Why are there two Spring Boot integration community-audit-stores artifacts?
+### Why are there two Spring Boot integration artifacts?
 
 The only difference is the Java version they target:
 
diff --git a/docs/overview/audit-store-vs-target-system.md b/docs/overview/audit-store-vs-target-system.md
@@ -17,15 +17,15 @@ Flamingock's architecture separates business changes from execution tracking thr
 - **Examples**: User database, Product catalog, Order management system, Kafka topics, S3 buckets, REST APIs
 - **Purpose**: Store and process your business data and configurations
 - **Modified by**: Your business logic through ChangeUnits
-- **Configuration**: See [Target System Configuration](../flamingock-library-config/target-system-configuration.md) for technical setup
+- **Configuration**: See [Target Systems](../target-systems/introduction.md) for technical setup
 
 ### Audit store: where execution is tracked  
 **Audit store** is Flamingock's dedicated system for tracking what happened:
 
 - **Examples**: Flamingock Cloud backend or dedicated audit table/collection in the user's database. 
 - **Purpose**: Record execution history, compliance data, issue tracking
 - **Modified by**: Flamingock framework automatically (never your code)
-- **Configuration**: See [Audit Store Configuration](../flamingock-library-config/audit-store-configuration.md) for technical setup
+- **Configuration**: See [Audit Stores](../audit-stores/introduction.md) for technical setup
 
 
 ## Why this separation matters
@@ -60,7 +60,7 @@ Systems without native transaction support (Kafka, S3, REST APIs, File Systems):
 Flamingock Cloud provides a fully managed audit store with superior synchronization and recovery through advanced coordination protocols, real-time dashboards, advanced analytics, and multi-environment governance.
 
 ### Community Audit Stores audit store  
-User-provided audit store (MongoDB, DynamoDB, Couchbase) that ensures complete execution tracking, prevents duplicate executions, and provides basic recovery capabilities. See [Community audit store configuration](../flamingock-library-config/audit-store-configuration.md) for setup.
+User-provided audit store (MongoDB, DynamoDB, Couchbase) that ensures complete execution tracking, prevents duplicate executions, and provides basic recovery capabilities. See [Audit stores](../audit-stores/introduction.md) for setup.
 
 
 
@@ -137,7 +137,7 @@ User-provided audit store (MongoDB, DynamoDB, Couchbase) that ensures complete e
 ### For developers
 - **Target systems**: Where your business logic runs and makes changes
 - **Audit store**: Automatically managed by Flamingock for tracking and compliance
-- **Implementation**: See [Target System Configuration](../flamingock-library-config/target-system-configuration.md) and [Audit Store Configuration](../flamingock-library-config/audit-store-configuration.md)
+- **Implementation**: See [Target Systems](../target-systems/introduction.md) and [Audit Stores](../audit-stores/introduction.md)
 
 ### For architects  
 - **Clean separation**: Business logic separated from execution tracking
diff --git a/docs/overview/core-concepts.md b/docs/overview/core-concepts.md
@@ -18,7 +18,7 @@ ChangeUnits can be implemented in two forms:
 - **Code-based**: Java classes with annotations that contain the change logic
 - **Template-based**: Declarative low-code approach using YAML configurations
 
-For a deeper dive around ChangeUnits, see the [ChangeUnits deep dive](../flamingock-library-config/changeunits-deep-dive.md) section.
+For a deeper dive around ChangeUnits, see the [ChangeUnits](../change-units/anatomy-and-structure.md) section.
 
 
 ### Templates
@@ -44,7 +44,7 @@ Flamingock provides two main strategies:
 
 The choice of strategy depends on whether your changes are idempotent and how critical they are to your system's integrity.
 
-For detailed configuration and implementation, see the [Recovery configuration](../flamingock-library-config/recovery-configuration.md) section.
+For detailed configuration and implementation, see the [Recovery strategies](../recovery-and-safety/recovery-strategies.md) section.
 
 
 ## Audit store
@@ -53,7 +53,7 @@ The **audit store** is where Flamingock records metadata about change executions
 ## Target system  
 The **target system** is where your actual business changes are applied. These are the systems your ChangeUnits modify - databases, message queues, APIs, configuration services, etc. Each ChangeUnit declares which target system it operates on.
 
-For more details about how these systems work together, see the [Audit store vs target system](../overview/audit-store-vs-target-system.md) section.
+For more details about how these systems work together, see the [Audit store vs target system](audit-store-vs-target-system.md) section.
 
 
 ## Transaction handling
diff --git a/docs/overview/quick-start.md b/docs/overview/quick-start.md
@@ -138,7 +138,7 @@ public class _002_CreateS3Bucket {
   </TabItem>
 </Tabs>
 
-For more details, see [Concepts → ChangeUnits](../overview/core-concepts.md).
+For more details, see [Core concepts](core-concepts.md).
 
 
 ## 3. Create target systems
@@ -157,7 +157,7 @@ DefaultTargetSystem s3 = new DefaultTargetSystem("aws-s3");
 DefaultTargetSystem kafka = new DefaultTargetSystem("kafka");
 ```
 
-See [Target systems](../flamingock-library-config/target-system-configuration.md) for more details.
+See [Target systems](../target-systems/introduction.md) for more details.
 
 
 ## 4. Configure stages
diff --git a/docs/resources/faq.md b/docs/resources/faq.md
@@ -81,22 +81,22 @@ Yes. You can conditionally run ChangeUnits using [`@Profile`](../frameworks/spri
 ### Configuration
 
 **Where do I set MongoDB connection options like write concern or read preference?**  
-You can define these directly in the config using dedicated properties (e.g. `mongodb.writeConcern.w`, `readPreference`, etc.). Refer to the [extra configuration](../flamingock-library-config/extra-configuration.md) section for detailed examples.
+You can define these directly in the config using dedicated properties (e.g. `mongodb.writeConcern.w`, `readPreference`, etc.). Refer to the [additional configuration](../flamingock-library-config/additional-configuration.md) section for detailed examples.
 
 **Can I inject Spring beans or other services into my ChangeUnits?**  
-Yes. Flamingock supports full [dependency injection](../flamingock-library-config/changeunit-dependency-injection.md) in both Spring and non-Spring environments.
+Yes. Flamingock supports full [dependency injection](../flamingock-library-config/context-and-dependencies.md) in both Spring and non-Spring environments.
 
 **Can I define ChangeUnit dependencies and execution order?**  
-Yes. ChangeUnits can declare dependencies via annotations or configuration metadata. See [ChangeUnit deep dive](../flamingock-library-config/changeunits-deep-dive.md) for more.
+Yes. ChangeUnits can declare dependencies via annotations or configuration metadata. See [ChangeUnit anatomy](../change-units/anatomy-and-structure.md) for more.
 
 
 ### Testing and development
 
 **How do I test Flamingock ChangeUnits?**  
-You can perform [unit](../testing/unit-testing.md), [integration](../testing/integration-testing.md), and [Spring Boot integration](../testing/springboot-integration-testing.md) tests using test runners and mocking utilities.
+You can perform unit, integration, and Spring Boot integration tests using test runners and mocking utilities. See the [Testing](../testing/introduction.md) section for more details.
 
 **Can I use templates to generate ChangeUnits?**  
-Yes. Flamingock offers a templating mechanism for [creating new ChangeUnits](../templates/templates-how-to-use.md) and defining reusable components.
+Yes. Flamingock offers a templating mechanism for [creating new ChangeUnits](../templates/templates-introduction.md) and defining reusable components.
 
 
 ### Migrating from Mongock
@@ -113,7 +113,7 @@ Some of the key advancements introduced by Flamingock include:
 
 While Flamingock retains conceptual compatibility with Mongock, it represents a significant leap forward in flexibility, scalability, and developer experience.
 
-If you are currently using Mongock, we encourage you to [review the migration guide](upgrade-from-mongock.md) and explore what Flamingock can offer in modern change management.
+If you are currently using Mongock, we encourage you to [review the migration guide](coming-from-mongock.md) and explore what Flamingock can offer in modern change management.
 
 
 ### Recovery Strategies & Safety
diff --git a/docs/target-systems/couchbase-target-system.md b/docs/target-systems/couchbase-target-system.md
@@ -19,7 +19,7 @@ While dependencies can be provided through the global context, we highly recomme
 
 ## Dependencies
 
-Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/target-system-configuration.md#dependency-resolution-hierarchy), you can provide dependencies via direct injection or global context.
+Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/context-and-dependencies.md), you can provide dependencies via direct injection or global context.
 
 ### Required dependencies
 
@@ -122,6 +122,6 @@ For more details on dependency resolution, see [Context and dependencies](../fla
 
 ## Next steps
 
-- Learn about [Target system configuration](../flamingock-library-config/target-system-configuration.md)
+- Learn about [Target systems](introduction.md)
 - Explore [ChangeUnits](../change-units/introduction.md)
 - See [Couchbase examples](https://github.com/flamingock/flamingock-examples/tree/master/couchbase)
diff --git a/docs/target-systems/default-target-system.md b/docs/target-systems/default-target-system.md
@@ -31,7 +31,7 @@ Unlike specialized target systems, DefaultTargetSystem requires no mandatory dep
 
 ## Dependencies
 
-Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/target-system-configuration.md#dependency-resolution-hierarchy), you can provide dependencies via direct injection or global context.
+Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/context-and-dependencies.md), you can provide dependencies via direct injection or global context.
 
 ### No required dependencies
 
@@ -92,6 +92,6 @@ For more details on dependency resolution, see [Context and dependencies](../fla
 
 ## Next steps
 
-- Learn about [Target system configuration](../flamingock-library-config/target-system-configuration.md)
+- Learn about [Target systems](introduction.md)
 - Explore [ChangeUnits](../change-units/introduction.md)  
 - See [DefaultTargetSystem examples](https://github.com/flamingock/flamingock-examples/tree/master/default)
diff --git a/docs/target-systems/dynamodb-target-system.md b/docs/target-systems/dynamodb-target-system.md
@@ -18,7 +18,7 @@ While dependencies can be provided through the global context, we highly recomme
 
 ## Dependencies
 
-Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/target-system-configuration.md#dependency-resolution-hierarchy), you can provide dependencies via direct injection or global context.
+Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/context-and-dependencies.md), you can provide dependencies via direct injection or global context.
 
 ### Required dependencies
 
@@ -101,6 +101,6 @@ For more details on dependency resolution, see [Context and dependencies](../fla
 
 ## Next steps
 
-- Learn about [Target system configuration](../flamingock-library-config/target-system-configuration.md)
+- Learn about [Target systems](introduction.md)
 - Explore [ChangeUnits](../change-units/introduction.md)
 - See [DynamoDB examples](https://github.com/flamingock/flamingock-examples/tree/master/dynamodb)
diff --git a/docs/target-systems/mongodb-springdata-target-system.md b/docs/target-systems/mongodb-springdata-target-system.md
@@ -18,7 +18,7 @@ While dependencies can be provided through the global context, we highly recomme
 
 ## Dependencies
 
-Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/target-system-configuration.md#dependency-resolution-hierarchy), you can provide dependencies via direct injection or global context.
+Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/context-and-dependencies.md), you can provide dependencies via direct injection or global context.
 
 ### Required dependencies
 
@@ -108,6 +108,6 @@ For more information on Spring Boot integration, see [Spring Boot integration](.
 
 ## Next steps
 
-- Learn about [Target system configuration](../flamingock-library-config/target-system-configuration.md)
+- Learn about [Target systems](introduction.md)
 - Explore [ChangeUnits](../change-units/introduction.md)
 - See [MongoDB Spring Data examples](https://github.com/flamingock/flamingock-examples/tree/master/mongodb-springdata)
diff --git a/docs/target-systems/mongodb-target-system.md b/docs/target-systems/mongodb-target-system.md
@@ -19,7 +19,7 @@ While dependencies can be provided through the global context, we highly recomme
 
 ## Dependencies
 
-Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/target-system-configuration.md#dependency-resolution-hierarchy), you can provide dependencies via direct injection or global context.
+Following Flamingock's [dependency resolution hierarchy](../flamingock-library-config/context-and-dependencies.md), you can provide dependencies via direct injection or global context.
 
 ### Required dependencies
 
@@ -108,6 +108,6 @@ For more details on dependency resolution, see [Context and dependencies](../fla
 
 ## Next steps
 
-- Learn about [Target system configuration](../flamingock-library-config/target-system-configuration.md)
+- Learn about [Target systems](introduction.md)
 - Explore [ChangeUnits](../change-units/introduction.md)
 - See [MongoDB examples](https://github.com/flamingock/flamingock-examples/tree/master/mongodb)
diff --git a/docs/target-systems/sql-target-system.md b/docs/target-systems/sql-target-system.md
diff --git a/docs/templates/create-your-own-template.md b/docs/templates/create-your-own-template.md
diff --git a/docusaurus.config.js b/docusaurus.config.js
diff --git a/sidebars.js b/sidebars.js
