Remove level 1 headers from docs as it duplicates title frontmatter (#14)

Signed-off-by: Thomas Cooper <code@tomcooper.dev>

Author: tomncooper

docs/_index.md

@@ -6,8 +6,6 @@ weight = 0
     type = 'docs'
 +++
 
-# Developer Quick-Start
-
 Please make sure you have all the [prerequisites](prerequisites.md) covered first.
 Then you can deploy a complete, open-source, event-streaming stack on your local Kubernetes cluster (e.g. MiniKube, KIND) with a single command:
 

docs/accessing-services.md

@@ -3,8 +3,6 @@ title = 'Accessing Services'
 weight = 3
 +++
 
-# Accessing Services
-
 ## StreamsHub Console
 
 ### Ingress Access

docs/architecture.md

@@ -3,8 +3,6 @@ title = 'Architecture'
 weight = 6
 +++
 
-# Architecture
-
 ## Two-Phase Deployment
 
 The event stack is deployed in two sequential phases:
@@ -17,9 +15,9 @@ Operators must be running to process these resources.
 
 This separation exists for three reasons:
 
-1. **CRD registration** — Kubernetes must register CRDs before it can accept custom resources of that type
-2. **Operator readiness** — operators must be running to reconcile their custom resources
-3. **Safe teardown** — during uninstall, operands are deleted first while operators are still alive to process finalizers
+1. CRD registration — Kubernetes must register CRDs before it can accept custom resources of that type
+2. Operator readiness — operators must be running to reconcile their custom resources
+3. Safe teardown — during uninstall, operands are deleted first while operators are still alive to process finalizers
 
 The install script uses `kubectl apply --server-side` for Phase 1 to handle large CRDs (such as those from the Prometheus Operator) that exceed the annotation size limit used by client-side apply.
 

docs/installation.md

@@ -3,8 +3,6 @@ title = 'Installation'
 weight = 2
 +++
 
-# Installation
-
 ## Quick-Start Install
 
 Deploy the entire core stack with a single command:

docs/overlays/_index.md

@@ -3,8 +3,6 @@ title = 'Overlays'
 weight = 4
 +++
 
-# Overlays
-
 The developer quick-start uses [Kustomize overlays](architecture.md) to provide optional extensions on top of the core stack. 
 Each overlay adds components that integrate with the base deployment.
 

docs/overlays/core.md

@@ -5,8 +5,6 @@ cpu_total = '3 CPU cores'
 memory_total = '4.5 GiB'
 +++
 
-# Core Overlay
-
 The core overlay is the default deployment. 
 It installs the base event-streaming stack without any optional extensions.
 

docs/overlays/developing.md

@@ -3,8 +3,6 @@ title = 'Developing Overlays'
 weight = 100
 +++
 
-# Developing Overlays
-
 This page covers the requirements for adding or modifying overlays. 
 CI enforces various checks on the overlays automatically on every pull request.
 

docs/overlays/metrics.md

@@ -5,8 +5,6 @@ cpu_total = '3 CPU cores'
 memory_total = '5.5 GiB'
 +++
 
-# Metrics Overlay
-
 The metrics overlay extends the core stack with Prometheus-based monitoring.
 
 ## Quick-Start Install

docs/prerequisites.md

@@ -3,8 +3,6 @@ title = 'Prerequisites'
 weight = 1
 +++
 
-# Prerequisites
-
 ## Required
 
 - **kubectl v1.27 or later** — the install scripts use Kustomize v5.0 features (the `labels` transformer) which require kubectl 1.27+.

docs/troubleshooting.md

@@ -3,8 +3,6 @@ title = 'Troubleshooting'
 weight = 7
 +++
 
-# Troubleshooting
-
 ## Operator Not Becoming Ready
 
 If an operator deployment does not reach `Ready`/`Available` within the timeout: