From 41d25048473c1d985feed3a7c31472425e86fc5d Mon Sep 17 00:00:00 2001
From: Zoffix Znet <cpan@zoffix.com>
Date: Sat, 13 Oct 2018 12:03:25 -0400
Subject: [PATCH] Reword "in future language versions"

- We *are* deprecating some features on language level in 6.d,
    even if the Rakudo implementation currently can't issue
    per-language-version deprecation warnings on methods
- Just because an implementation doesn't short-circuit Junctions
    yet, doesn't mean that's defined behaviour on language level
---
 doc/Type/IO/Handle.pod6 |  4 ++--
 doc/Type/Junction.pod6  | 10 +++++-----
 doc/Type/Pair.pod6      |  7 +++++--
 3 files changed, 12 insertions(+), 9 deletions(-)

diff --git a/doc/Type/IO/Handle.pod6 b/doc/Type/IO/Handle.pod6
index 94207fcf6..7307c7312 100644
--- a/doc/Type/IO/Handle.pod6
+++ b/doc/Type/IO/Handle.pod6
@@ -97,8 +97,8 @@ C<open> to open (if C<closed>) the C<$*IN> handle if opening in read-only
 mode or to open the C<$*OUT> handle if opening in write-only mode. All other
 modes in this case will result in exception being thrown.
 
-In future language versions, path C<'-'> will likely have no special meaning and
-relying on this behaviour in new programs is not recommended.
+As of B<6.d> language version, use path C<'-'> is deprecated and it will
+be removed in future language versions entirely.
 
 The C<:out-buffer> controls output buffering and by default behaves as if
 it were C<Nil>. See method L<out-buffer> for details.
diff --git a/doc/Type/Junction.pod6 b/doc/Type/Junction.pod6
index f6929854c..b28a0f3ac 100644
--- a/doc/Type/Junction.pod6
+++ b/doc/Type/Junction.pod6
@@ -60,11 +60,11 @@ Note that the compiler is allowed, but not required, to parallelize
 autothreading (and Junction behavior in general), so it is usually an
 error to autothread junctions over code with side effects.
 
-It is possible that I<future language versions> will include short-circuiting
-behaviour in Junctions. For example one or more routine calls (C<a()>, C<b()>,
-or C<c()>) in the code below might not get executed at all, if the result of
-the conditional has been fully determined from routine calls already performed
-(only one truthy return value is enough to know the entire Junction is true):
+Implementations are allowed to short-circuit Junctions. For example one or more
+routine calls (C<a()>, C<b()>, or C<c()>) in the code below might not get
+executed at all, if the result of the conditional has been fully determined
+from routine calls already performed (only one truthy return value is enough
+to know the entire Junction is true):
 
 =begin code :preamble<sub a(){}; sub b(){}; sub c(){}>
 if a() | b() | c() {
diff --git a/doc/Type/Pair.pod6 b/doc/Type/Pair.pod6
index cd25a7b46..aa4b22e8d 100644
--- a/doc/Type/Pair.pod6
+++ b/doc/Type/Pair.pod6
@@ -301,8 +301,11 @@ Makes the I<value> of the C<Pair> read-only, by removing it from its L<Scalar co
     CATCH { default { put .^name, ': ', .Str } };
     # OUTPUT: «X::Assignment::RO: Cannot modify an immutable Str (apple)␤»
 
-B<NOTE:> this method is proposed for removal in future language versions and its
-use is not recommended.
+B<NOTE:> this method is deprecated as of B<6.d> language version. Instead,
+create a new C<Pair>, with L<deconted|/language/glossary#decont> key/value.
+
+    =for code :preamble<my $p>
+    $p.=Map.=head.say;                # OUTPUT: «orange␤»
 
 =head2 method Str