Additional Features: Clarify non-officialness of their proposals

additional-feature-ba.md

@@ -11,11 +11,14 @@
 # Additional Feature BA
 ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
 
-An feature – **bare awaited calls** – makes async function calls terser. It adds
+This document is not yet intended to be officially proposed to TC39 yet; it merely shows a possible
+extension of the [Core Proposal][] in the event that the Core Proposal is accepted.
+
+An additional feature – **bare awaited calls** – would make async function calls terser. It adds
 another mode to bare style: if a bare-style pipeline step is preceded by a
 `await`, then instead of a mere function call, it is an awaited function call.
 `value |> await object.asyncFunction` is equivalent to `await
-object.asyncFunction(value)`. This is backwards compatible with the [Core
+object.asyncFunction(value)`. This would be backwards compatible with the [Core
 Proposal][] as well as all other [additional features][].
 
 [Additional Feature BA is **formally specified in in the draft

additional-feature-bc.md

@@ -11,7 +11,10 @@
 # Additional Feature BC
 ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
 
-An additional feature – **bare constructor calls** – makes constructor calls
+This document is not yet intended to be officially proposed to TC39 yet; it merely shows a possible
+extension of the [Core Proposal][] in the event that the Core Proposal is accepted.
+
+An additional feature – **bare constructor calls** – would make constructor calls
 terser. It adds a mode to bare style: if a bare-style pipeline step is preceded
 by a `new`, then instead of a function call, it is a constructor call. `value |>
 object.Constructor` is equivalent to `object.Constructor(value)`. This is

additional-feature-bp.md

@@ -11,6 +11,9 @@
 # Additional Feature BP
 ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
 
+This document is not yet intended to be officially proposed to TC39 yet; it merely shows a possible
+extension of the [Core Proposal][] in the event that the Core Proposal is accepted.
+
 There is a TC39 proposal for [`do` expressions][] at Stage 1. Smart pipelines do
 **not** require `do` expressions. However, if [`do` expressions][] also become
 part of JavaScript, then, as with **any** other type of expression, a pipeline

additional-feature-np.md

@@ -11,7 +11,10 @@
 # Additional Feature NP
 ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
 
-An Additional Feature – **n-ary pipelines** – enables the passing of
+This document is not yet intended to be officially proposed to TC39 yet; it merely shows a possible
+extension of the [Core Proposal][] in the event that the Core Proposal is accepted.
+
+An Additional Feature – **n-ary pipelines** – would enable the passing of
 multiple arguments into a pipeline’s steps. `(a, b) |> f` is equivalent to
 `f(a, b)`, and `a |> (f(#), g(#)) |> h` is equivalent to `h(f(a), g(a))`.
 

additional-feature-pf.md

@@ -11,8 +11,10 @@
 # Additional Feature PF
 ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
 
-**More than any other** possible extension in this table, this additional
-feature – **Pipeline Functions** – would dramatically increase the usefulness of
+This document is not yet intended to be officially proposed to TC39 yet; it merely shows a possible
+extension of the [Core Proposal][] in the event that the Core Proposal is accepted.
+
+This additional feature – **Pipeline Functions** – would dramatically increase the usefulness of
 pipelines. It introduces just one additional operator that solves:\
 tacit unary **functional composition**,\
 tacit unary functional **partial application**,\

additional-feature-ts.md

@@ -11,12 +11,15 @@
 # Additional Feature TS
 ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.
 
+This document is not yet intended to be officially proposed to TC39 yet; it merely shows a possible
+extension of the [Core Proposal][] in the event that the Core Proposal is accepted.
+
 With the [Core Proposal][] only, all `try` statements’ `catch` clauses would
 prohibit the use of the topic reference within their steps, except where the
 topic reference `#` is inside an inner pipeline inside the `catch` clause: this
 is one of the Core Proposal’s [early errors][] mentioned above.
 
-The next additional feature – **Pipeline `try` Statements** – adds new forms of
+This additional feature – **Pipeline `try` Statements** – would add new forms of
 the `try` statement, the `catch` clause, and the `finally` clause, in the form
 of `try |> …`, `catch |> …`, and `finally |> …`, each followed by a [pipeline
 with the same smart step syntax][smart step syntax].