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 2020/04/24 04:20:45 UTC

[groovy] branch GROOVY_3_0_X updated: fix typo

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

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


The following commit(s) were added to refs/heads/GROOVY_3_0_X by this push:
     new e4ef86f  fix typo
e4ef86f is described below

commit e4ef86f45d980ea07b3aef5069a7552659da0505
Author: Paul King <pa...@asert.com.au>
AuthorDate: Fri Apr 24 14:18:30 2020 +1000

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

diff --git a/src/spec/doc/core-differences-java.adoc b/src/spec/doc/core-differences-java.adoc
index f38ac8b..4d5cb18 100644
--- a/src/spec/doc/core-differences-java.adoc
+++ b/src/spec/doc/core-differences-java.adoc
@@ -360,7 +360,7 @@ In addition, Groovy has the following keywords:
 * `trait`
 * `it` // within closures
 
-Groovy is less stringent that Java in that it allows some keywords to appear in places that would be illegal in Java,
+Groovy is less stringent than Java in that it allows some keywords to appear in places that would be illegal in Java,
 e.g. the following is valid: `var var = [def: 1, as: 2, in: 3, trait: 4]`.
 Never-the-less, you are discouraged from using the above keywords in places that might cause confusion even when
 the compiler might be happy. In particular, avoid using them for variable, method and class names,