(groovy) branch master updated: misc: minor documentation edits

[pa...@apache.org]

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 3fca4f9a43 misc: minor documentation edits
3fca4f9a43 is described below

commit 3fca4f9a43b145c4d8d38518764a68ef23d1bea0
Author: Jonny Carter <jc...@adaptavist.com>
AuthorDate: Fri May 30 10:26:45 2025 -0500

    misc: minor documentation edits
---
 src/spec/doc/_type-checking-extensions.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/spec/doc/_type-checking-extensions.adoc b/src/spec/doc/_type-checking-extensions.adoc
index eee08b54ed..ccef4de5f7 100644
--- a/src/spec/doc/_type-checking-extensions.adoc
+++ b/src/spec/doc/_type-checking-extensions.adoc
@@ -1062,14 +1062,14 @@ type of the dynamic call is a `Robot`, subsequent calls will be done statically!
 
 Some would wonder why the static compiler doesn't do this by default without an extension. It is a design decision:
 
-* if the code is statically compiled, we normally want type safety and best performance
-* so if unrecognized variables/method calls are made dynamic, you loose type safety, but also all support for typos at
-compile time!
+* if the code is statically compiled, we normally want type safety and the best performance
+* if unrecognized variables/method calls are made dynamic, you lose type safety, but also all support for catching typos
+at compile time!
 
 In short, if you want to have mixed mode compilation, it *has* to be explicit, through a type checking extension, so
 that the compiler, and the designer of the DSL, are totally aware of what they are doing.
 
-`makeDynamic` can be used on 3 kind of AST nodes:
+`makeDynamic` can be used on 3 kinds of AST nodes:
 
 * a method node (`MethodNode`)
 * a variable (`VariableExpression`)