From 19b695b2eedc6b3ba351ec6ab9550ff54a1d5880 Mon Sep 17 00:00:00 2001
From: Daniel Hilst <392820+dhilst@users.noreply.github.com>
Date: Thu, 10 Sep 2026 10:16:11 -0300
Subject: [PATCH] docs(dhcptest): point the architecture table at the section
 it means

The examples table said "see backend parity below" and nothing below is called
that. The asymmetries are enumerated under "Feature: The two backends behave
the same on the wire", so name that heading and its scenario instead.
---
 xCAT-test/dhcptest/spec.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/xCAT-test/dhcptest/spec.md b/xCAT-test/dhcptest/spec.md
index d88c3cae3..13493cfae 100644
--- a/xCAT-test/dhcptest/spec.md
+++ b/xCAT-test/dhcptest/spec.md
@@ -131,7 +131,9 @@ Scenario Outline: The loader follows the client architecture in option 93
     | 0x000b | aarch64 UEFI                 | boot/grub2/grub2.aarch64  |
     | 0x001b | riscv64 UEFI, TFTP           | boot/grub2/grub2.riscv64  |
 
-  Examples: architectures only one backend answers -- see backend parity below
+  Examples: architectures only one backend answers
+  # Enumerated in full under "Feature: The two backends behave the same on the
+  # wire", scenario "Known asymmetries between the backends".
     | arch   | client                       | loader                    |
     | 0x0010 | x86-64 UEFI HTTP boot        | xcat/xnba.efi (Kea only)  |
     | 0x000c | ppc64 UEFI                   | /boot/grub2/grub2.ppc (Kea only) |