From 47c39657fe015c96be443dfb0342cde1758a9402 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Sat, 1 Nov 2025 21:50:14 +0000 Subject: [PATCH] Fix markup --- doc/src/tables/events.m4 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/tables/events.m4 b/doc/src/tables/events.m4 index 54e7f10..02a34e1 100644 --- a/doc/src/tables/events.m4 +++ b/doc/src/tables/events.m4 @@ -47,7 +47,7 @@ The following table lists these rules and implications: .. _EVENTS_arrival_code: ``sdb_arrival`` (Arrival) - A related row should exist on ARRIVALS; there should be a row on + A related row should exist on |ARRIVALS|; there should be a row on |ARRIVALS| with an |ARRIVALS.EID| value of the event's |EVENTS.EID|. There may be at most one of these related |ARRIVALS| rows. @@ -61,7 +61,7 @@ The following table lists these rules and implications: The system will generate a warning when there is no |ROLES| row related to the arrival event. - The |EVENTS|.\ |EVENTS.Start| column contains the arrival time of + The EVENTS.\ |EVENTS.Start| column contains the arrival time of the individual identified in the related |ROLES| row. The |EVENTS|.\ |EVENTS.Stop| column contains the departure time of -- 2.34.1