Repository: groovy
Updated Branches:
  refs/heads/master 9b1fb03d6 -> bddcb5741


typo


Project: http://git-wip-us.apache.org/repos/asf/groovy/repo
Commit: http://git-wip-us.apache.org/repos/asf/groovy/commit/bddcb574
Tree: http://git-wip-us.apache.org/repos/asf/groovy/tree/bddcb574
Diff: http://git-wip-us.apache.org/repos/asf/groovy/diff/bddcb574

Branch: refs/heads/master
Commit: bddcb574153db143e3a2c61f0638763be95c6294
Parents: 9b1fb03
Author: paulk <pa...@asert.com.au>
Authored: Wed Jan 3 11:20:37 2018 +1000
Committer: paulk <pa...@asert.com.au>
Committed: Wed Jan 3 11:20:37 2018 +1000

----------------------------------------------------------------------
 src/spec/doc/core-object-orientation.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/groovy/blob/bddcb574/src/spec/doc/core-object-orientation.adoc
----------------------------------------------------------------------
diff --git a/src/spec/doc/core-object-orientation.adoc 
b/src/spec/doc/core-object-orientation.adoc
index febd42f..7177c86 100644
--- a/src/spec/doc/core-object-orientation.adoc
+++ b/src/spec/doc/core-object-orientation.adoc
@@ -464,7 +464,7 @@ to omit the type.
 A property is an externally visible feature of a class. Rather than just using 
a public field to represent
 such features (which provides a more limited abstraction and would restrict 
refactoring possibilities),
 the typical convention in Java is to follow JavaBean conventions, i.e. 
represent the property using a
-combination of a private backing field and getters/setters. Groovy follows 
these same convetions
+combination of a private backing field and getters/setters. Groovy follows 
these same conventions
 but provides a simpler approach to defining the property. You can define a 
property with:
 
 * an *absent* access modifier (no `public`, `protected` or `private`)

Reply via email to