docs: overview(landing page), introduction, and FAQ improved formatting

Author: dieppa

docs/audit-stores/community/couchbase-audit-store.md

@@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem';
 
 The Couchbase audit store (`CouchbaseSyncAuditStore`) enables Flamingock to record execution history and ensure safe coordination across distributed deployments using Couchbase as the storage backend.
 
-> 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](../../get-started/audit-store-vs-target-system.md).
 
 ## Version Compatibility
 

docs/audit-stores/community/dynamodb-audit-store.md

@@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem';
 
 The DynamoDB audit store (`DynamoSyncAuditStore`) enables Flamingock to record execution history and ensure safe coordination across distributed deployments using Amazon DynamoDB as the storage backend.
 
-> 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](../../get-started/audit-store-vs-target-system.md).
 
 ## Version Compatibility
 

docs/audit-stores/community/mongodb-audit-store.md

@@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem';
 
 The MongoDB audit store (`MongoDBSyncAuditStore`) enables Flamingock to record execution history and ensure safe coordination across distributed deployments using MongoDB as the storage backend.
 
-> 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](../../get-started/audit-store-vs-target-system.md).
 
 ## Version Compatibility
 

docs/audit-stores/introduction.md

@@ -19,7 +19,7 @@ The audit store tracks:
 
 Unlike target systems (which your code modifies), the audit store is managed automatically by Flamingock and never modified by your Changes.
 
-> **Conceptual overview**: For architectural understanding, see [Target systems vs audit store](../overview/audit-store-vs-target-system.md)
+> **Conceptual overview**: For architectural understanding, see [Target systems vs audit store](../get-started/audit-store-vs-target-system.md)
 
 
 ## Cloud audit store

docs/changes/introduction.md

@@ -9,7 +9,7 @@ import TabItem from '@theme/TabItem';
 
 # Changes
 
-A **Change** is the atomic, versioned, self-contained unit of change in Flamingock. It encapsulates logic to evolve [**target systems**](../overview/audit-store-vs-target-system.md) safely, deterministically, and with complete auditability.
+A **Change** is the atomic, versioned, self-contained unit of change in Flamingock. It encapsulates logic to evolve [**target systems**](../get-started/audit-store-vs-target-system.md) safely, deterministically, and with complete auditability.
 
 ## Key characteristics
 

docs/overview/Change-as-Code.md renamed to docs/get-started/Change-as-Code.md

@@ -7,7 +7,7 @@ title: " "
 # Introduction
 
 **Flamingock** brings *Change-as-Code (CaC)* to your entire stack.  
-It applies **versioned, auditable changes** to the external systems your application depends on — such as databases, schemas, message brokers, APIs, and cloud services.  
+It applies **versioned, auditable changes** to the external systems your application depends on — such as  schemas, message brokers, databases, APIs, cloud services...  
 
 Unlike infrastructure-as-code tools, Flamingock runs **inside your application** (or via the **CLI**).  
 It ensures these systems evolve **safely, consistently, and in sync with your code at runtime**.