From a53639a8e57310a689d2172dfe85d37b3b8fde90 Mon Sep 17 00:00:00 2001 From: Kieran H Date: Fri, 22 Jul 2022 23:38:26 +0100 Subject: [PATCH] Update FM Basics.md --- docs/FM Basics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/FM Basics.md b/docs/FM Basics.md index e92ef9be..abcb2d4d 100644 --- a/docs/FM Basics.md +++ b/docs/FM Basics.md @@ -36,7 +36,7 @@ Start and End times are in UTC. They are when the flow measure will be in effect Reason should be provided for all flow measures, even if considered obvious. This message should specifically indicate the flow limitation (e.g. EDDH landing rate, Jever sector capacity). The presence of an event is not in itself a reason to require flow control. -The flow measure required should then be selected. With the exception of ‘prohibit’ type flow measures, all measures require a value (e.g. a time, distance or waypoint) to be immediately specified. (see 'FM: Types' documentation for further details. +The flow measure required should then be selected. With the exception of ‘prohibit’ and 'ground stop' flow measures (see FM: Types), all measures require a value (e.g. a time, distance or waypoint) to be immediately specified. (see 'FM: Types' documentation for further details. Flow measures then require filters and applicability information set in the ‘FAO’ tab. These are documented below.