You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by pa...@apache.org on 2022/10/29 06:28:37 UTC

[groovy] 08/08: fix typo

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

paulk pushed a commit to branch GROOVY_4_0_X
in repository https://gitbox.apache.org/repos/asf/groovy.git

commit 0448ffad9c459135026e46c5a2db11e53ef7fe63
Author: Paul King <pa...@asert.com.au>
AuthorDate: Wed Oct 26 08:55:51 2022 +1000

    fix typo
---
 src/spec/doc/core-metaprogramming.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/spec/doc/core-metaprogramming.adoc b/src/spec/doc/core-metaprogramming.adoc
index 2ddf603f94..e752d029de 100644
--- a/src/spec/doc/core-metaprogramming.adoc
+++ b/src/spec/doc/core-metaprogramming.adoc
@@ -3383,7 +3383,7 @@ include::../test/metaprogramming/MacroVariableSubstitutionTest.groovy[tags=md5tr
 
 <1> We need a reference to a variable expression
 <2> If using a class outside the standard packages we should add any needed imports or use the qualified name. When
-using the qualified named of a given static method you need to make sure it's resolved in the proper compile phase. In
+using the qualified name of a given static method you need to make sure it's resolved in the proper compile phase. In
 this particular case we're instructing the macro to resolve it at the SEMANTIC_ANALYSIS phase, which is the first compile phase
 with type information.
 <3> In order to substitute any `expression` inside the macro we need to use the `$v` method. `$v` receives a closure as an