From 661cff9572a9df2ed171fc50fd0c915523aa08a2 Mon Sep 17 00:00:00 2001 From: Tory McKeag <143734462+getorymckeag@users.noreply.github.com> Date: Thu, 26 Sep 2024 12:53:15 -0700 Subject: [PATCH] Update docs/decision-log/seasonal-ratings-schedule.md Co-authored-by: Christopher Atkins <57670484+catkins-miso@users.noreply.github.com> Signed-off-by: Tory McKeag <143734462+getorymckeag@users.noreply.github.com> --- docs/decision-log/seasonal-ratings-schedule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/decision-log/seasonal-ratings-schedule.md b/docs/decision-log/seasonal-ratings-schedule.md index 3f85764..d5ad177 100644 --- a/docs/decision-log/seasonal-ratings-schedule.md +++ b/docs/decision-log/seasonal-ratings-schedule.md @@ -20,7 +20,7 @@ FERC 881 creates a practical need to be able to share these ratings in a more st some support for seasonal ratings makes sense in TROLIE, even if it is optional. However seasonal rating interop is challenging, because the definition and meaning of each season differs -between grid operators. The definition for [seasons](../concepts.md#seasons) in the FERC 881 context is 4 +between grid operators. The definition for [seasons](../concepts.md#seasons) in the FERC 881 context is quite flexible. While internally, grid operators may assign seasonal ratings to well-known named seasons such as `Fall`, the practices around `Fall` ratings can differ significantly between grid operators: