groovy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pa...@apache.org
Subject [groovy] 03/04: Fix typos (closes #842)
Date Thu, 27 Dec 2018 20:16:30 GMT
This is an automated email from the ASF dual-hosted git repository.

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

commit ad502e5010f8cb13e8f1c6bf2575b24a6ceff675
Author: Javier S. López <jslopez@gmail.com>
AuthorDate: Sun Dec 16 12:29:37 2018 +0100

    Fix typos (closes #842)
---
 src/spec/doc/design-pattern-composite.adoc   | 2 +-
 subprojects/groovy-jmx/src/spec/doc/jmx.adoc | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/spec/doc/design-pattern-composite.adoc b/src/spec/doc/design-pattern-composite.adoc
index e307431..32ce50e 100644
--- a/src/spec/doc/design-pattern-composite.adoc
+++ b/src/spec/doc/design-pattern-composite.adoc
@@ -29,7 +29,7 @@ Consider this usage of the composite pattern where we want to call `toString()`
 
 image::assets/img/CompositeClasses.gif[]
 
-In Java, the `Component` class is essential as it provides the type used for both leaf and
composite nodes. In Groovy, because of duck-typing, we don't need it for that purpose, however,
it can still server as a useful place to place common behaviour between the leaf and composite
nodes.
+In Java, the `Component` class is essential as it provides the type used for both leaf and
composite nodes. In Groovy, because of duck-typing, we don't need it for that purpose, however,
it can still serve as a useful place to place common behaviour between the leaf and composite
nodes.
 
 For our purposes, we will assemble the following hierarchy of components.
 
diff --git a/subprojects/groovy-jmx/src/spec/doc/jmx.adoc b/subprojects/groovy-jmx/src/spec/doc/jmx.adoc
index 5c748c6..935e33a 100644
--- a/subprojects/groovy-jmx/src/spec/doc/jmx.adoc
+++ b/subprojects/groovy-jmx/src/spec/doc/jmx.adoc
@@ -712,7 +712,7 @@ JmxBuilder **supports the explicit description and export of constructors**
defi
 
 ==== Export all Constructors with "*"
 
-You can use the builder's special '""' **notation to *export all constructors** declared
on the underlying bean. The builder will use default values to describe the MBean constructors.
+You can use the builder's special "*" **notation to export all constructors** declared on
the underlying bean. The builder will use default values to describe the MBean constructors.
 
 [source,groovy]
 ----
@@ -747,7 +747,7 @@ Similar to constructors, JmxBuilder supports the description and export
of MBean
 
 ==== Export All Operations with "*"
 
-You can use the builder's special '""'' **notation to *export all operations** defined on
the bean to be exposed for management. The builder will use default descriptor values for
the operations being exported.
+You can use the builder's special "*" **notation to export all operations** defined on the
bean to be exposed for management. The builder will use default descriptor values for the
operations being exported.
 
 [source,groovy]
 ----


Mime
View raw message