This is an automated email from the ASF dual-hosted git repository.

asf-ci-deploy pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/grails-doc.git


The following commit(s) were added to refs/heads/gh-pages by this push:
     new 5664d96902 Deploying to documentation branch - 19:19:07
5664d96902 is described below

commit 5664d969028c3fc89f8845f48c5f8925b8f8e84d
Author: jamesfredley <[email protected]>
AuthorDate: Fri Sep 19 19:19:07 2025 +0000

    Deploying to documentation branch - 19:19:07
---
 snapshot/guide/pages/upgrading60x.html | 2 +-
 snapshot/guide/single.html             | 2 +-
 snapshot/guide/upgrading.html          | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/snapshot/guide/pages/upgrading60x.html 
b/snapshot/guide/pages/upgrading60x.html
index 099f2e14ed..bbebfc514f 100644
--- a/snapshot/guide/pages/upgrading60x.html
+++ b/snapshot/guide/pages/upgrading60x.html
@@ -200,7 +200,7 @@ It is advisable to switch to the new form of the 
property.</p>
 <li>
 <p>Closures using the DELEGATE_FIRST strategy now behave differently.
 The resolution order in Groovy 3 used to be Delegate&#8217;s invokeMethod, 
Owner&#8217;s invokeMethod, Delegate&#8217;s invokeMissingMethod, Owner&#8217;s 
invokeMissingMethod.
-In Groovy 4, the order iw now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
+In Groovy 4, the order is now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
 </li>
 <li>
 <p>Closures defined in a parent class that reference its private properties or 
methods may no longer have access to them in subclasses.
diff --git a/snapshot/guide/single.html b/snapshot/guide/single.html
index 5af0593402..6381ff7f40 100644
--- a/snapshot/guide/single.html
+++ b/snapshot/guide/single.html
@@ -2373,7 +2373,7 @@ It is advisable to switch to the new form of the 
property.</p>
 <li>
 <p>Closures using the DELEGATE_FIRST strategy now behave differently.
 The resolution order in Groovy 3 used to be Delegate&#8217;s invokeMethod, 
Owner&#8217;s invokeMethod, Delegate&#8217;s invokeMissingMethod, Owner&#8217;s 
invokeMissingMethod.
-In Groovy 4, the order iw now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
+In Groovy 4, the order is now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
 </li>
 <li>
 <p>Closures defined in a parent class that reference its private properties or 
methods may no longer have access to them in subclasses.
diff --git a/snapshot/guide/upgrading.html b/snapshot/guide/upgrading.html
index 7b5e82bcd6..df61926e68 100644
--- a/snapshot/guide/upgrading.html
+++ b/snapshot/guide/upgrading.html
@@ -229,7 +229,7 @@ It is advisable to switch to the new form of the 
property.</p>
 <li>
 <p>Closures using the DELEGATE_FIRST strategy now behave differently.
 The resolution order in Groovy 3 used to be Delegate&#8217;s invokeMethod, 
Owner&#8217;s invokeMethod, Delegate&#8217;s invokeMissingMethod, Owner&#8217;s 
invokeMissingMethod.
-In Groovy 4, the order iw now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
+In Groovy 4, the order is now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
 </li>
 <li>
 <p>Closures defined in a parent class that reference its private properties or 
methods may no longer have access to them in subclasses.

Reply via email to