From ce68c49337f8be438f1cc0909f8b08f6e1138509 Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Mon, 11 May 2026 18:34:55 +0200
Subject: [PATCH] fix: promote routing-peer section headings to h2 (#741)

The page jumped from h1 directly to h3, leaving no h2 heading and
breaking the docs build. Promote both NetworkRouter and NetworkResource
sections to h2 so the hierarchy is contiguous.
---
 src/pages/manage/integrations/kubernetes/routing-peer.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/pages/manage/integrations/kubernetes/routing-peer.mdx b/src/pages/manage/integrations/kubernetes/routing-peer.mdx
index 2c8025a9..795d7ba8 100644
--- a/src/pages/manage/integrations/kubernetes/routing-peer.mdx
+++ b/src/pages/manage/integrations/kubernetes/routing-peer.mdx
@@ -2,7 +2,7 @@
 
 The operator exposes Kubernetes services to your NetBird network by combining two resources, a `NetworkRouter` and a `NetworkResource`.
 
-### NetworkRouter
+## NetworkRouter
 
 A `NetworkRouter` creates a network in NetBird and deploys routing peer pods in the cluster. These pods are configured as routing peers for the network, handling traffic between NetBird clients and services running in the cluster.
 
@@ -19,7 +19,7 @@ spec:
     name: prod.company.internal
 ```
 
-### NetworkResource
+## NetworkResource
 
 A `NetworkResource` exposes a Kubernetes service in NetBird by creating a matching resource in the routers network. The cluster IP of the service will be used as the resource IP. A record in the routers zone will also be created using the name and namespace of the service. The following example creates an nignx deployment and exposes the service with the record `nginx.default.prod.company.internal`.