docs: minor updates

Author: dieppa

docs/overview/_category_.json

@@ -1,5 +1,5 @@
 {
-  "label": "Overview",
+  "label": "Get started",
   "position": 2,
   "link": {
     "type": "doc",

docs/overview/core-concepts.md

@@ -4,7 +4,7 @@ sidebar_position: 30
 
 # Core concepts
 
-### ChangeUnits
+## ChangeUnits
 **ChangeUnits** are the fundamental building blocks of Flamingock's Change-as-Code architecture. They represent atomic, versioned changes applied to target systems with complete safety guarantees and audit capabilities.
 
 Each ChangeUnit includes:
@@ -21,7 +21,7 @@ ChangeUnits can be implemented in two forms:
 For a deeper dive around ChangeUnits, see the [ChangeUnits](../change-units/anatomy-and-structure.md) section.
 
 
-### Templates
+## Templates
 Templates provide a reusable layer on top of ChangeUnits for common change patterns. When you have multiple changes that share similar logic (for example, executing SQL statements), templates allow you to abstract that common logic and reuse it.
 
 With templates, you create multiple ChangeUnits using a declarative, low-code approach. Each ChangeUnit uses a template and passes its specific configuration. For example, an SQL template receives the SQL statement as configuration, executes it, and handles errors consistently.
@@ -49,6 +49,9 @@ For detailed configuration and implementation, see the [Recovery strategies](../
 
 ## Audit store
 The **audit store** is where Flamingock records metadata about change executions. Its purpose is to track which ChangeUnits have been executed, when they ran, and their outcomes. This ensures idempotency, enables rollbacks, and provides audit capabilities. The audit store is managed entirely by Flamingock - your code never directly interacts with it.
+  :::info
+  In Cloud Edition, the audit store is automatically provided - no configuration needed in your builder. Community Edition users must configure their own audit store.
+  :::
 
 ## 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.
@@ -78,9 +81,3 @@ Key characteristics:
 - Each stage defines where to find its changes (package or directory location)
 
 For detailed information about stages and advanced configurations, see the [Setup and stages](../flamingock-library-config/setup-and-stages.md) section.
-
-
-## Events
-Flamingock can notify your application about the execution status of changes through events. This enables integration with monitoring systems, custom logging, or triggering downstream processes based on change completion.
-
-For more information about events, see the [Events](../flamingock-library-config/events.md) section.

sidebars.js

@@ -25,7 +25,7 @@ const sidebars = {
     // Core Documentation Group
     {
       type: 'html',
-      value: '<div class="sidebar-contents-header">Overview</div>',
+      value: '<div class="sidebar-contents-header">Get started</div>',
     },
     {
       type: 'autogenerated',