Fix order within Infrastructure folder

RebeccaTamachiro · RebeccaTamachiro · commit aa1a3ad572fe · 2024-11-22T15:36:13.000Z
diff --git a/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx b/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx
@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Extended DNS error codes
+sidebar:
+  order: 4
 slug: 1.1.1.1/infrastructure/extended-dns-error-codes
-
 ---
 
 
diff --git a/src/content/docs/1.1.1.1/infrastructure/ipv6-networks.mdx b/src/content/docs/1.1.1.1/infrastructure/ipv6-networks.mdx
@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Support for IPv6-only networks
+sidebar:
+  order: 3
 slug: 1.1.1.1/infrastructure/ipv6-networks
-
 ---
 
 While network infrastructure is shifting towards IPv6-only networks, providers still need to support IPv4 addresses. Dual-stack networks are networks in which all nodes have both IPv4 and IPv6 connectivity capabilities, and can therefore understand both IPv4 and IPv6 packets.
diff --git a/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx b/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx
@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Network operators
+sidebar:
+  order: 1
 slug: 1.1.1.1/infrastructure/network-operators
-
 ---
 
 Network operators, including Internet Service Providers (ISPs), device manufacturers, public Wi-Fi networks, municipal broadband providers, and security scanning services can use [1.1.1.1](/1.1.1.1/setup/) in place of operating their own recursive DNS infrastructure.
