From 7fbd36f8609e4034221e0c6e6ca0b35811d07922 Mon Sep 17 00:00:00 2001 From: Richard Gibson Date: Wed, 24 Apr 2024 12:04:27 -0400 Subject: [PATCH 1/2] Avoid presumptive use of "always" --- spec/errors.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/errors.md b/spec/errors.md index f152edb77..4d2245980 100644 --- a/spec/errors.md +++ b/spec/errors.md @@ -226,7 +226,7 @@ syntax reserved for future standardization, or for private implementation use that is not supported by the current implementation. > For example, attempting to format this message -> would always result in an _Unsupported Expression_ error: +> would result in an _Unsupported Expression_ error: > > ``` > The value is {!horse}. @@ -274,7 +274,7 @@ for that specific _function_. An **_Unsupported Statement_** error occurs when a message includes a _reserved statement_. > For example, attempting to format this message -> would always result in an _Unsupported Statement_ error: +> would result in an _Unsupported Statement_ error: > > ``` > .some {|horse|} From 7656bec2cc8f6e6e9d7d58355f129783089bfa6c Mon Sep 17 00:00:00 2001 From: Richard Gibson Date: Wed, 24 Apr 2024 12:06:48 -0400 Subject: [PATCH 2/2] Explain the example Unsupported Expression error --- spec/errors.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/spec/errors.md b/spec/errors.md index 4d2245980..0fbac05bd 100644 --- a/spec/errors.md +++ b/spec/errors.md @@ -226,7 +226,8 @@ syntax reserved for future standardization, or for private implementation use that is not supported by the current implementation. > For example, attempting to format this message -> would result in an _Unsupported Expression_ error: +> would result in an _Unsupported Expression_ error +> because it includes a _reserved annotation_. > > ``` > The value is {!horse}.