You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by mg...@apache.org on 2016/03/25 13:59:35 UTC

wicket git commit: Small corrections

Repository: wicket
Updated Branches:
  refs/heads/wicket-7.x aac61bdb0 -> 3cbe984f7


Small corrections


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

Branch: refs/heads/wicket-7.x
Commit: 3cbe984f7973a54d177702482077f3f2f3da445a
Parents: aac61bd
Author: Martin Tzvetanov Grigorov <mg...@apache.org>
Authored: Fri Mar 25 13:59:21 2016 +0100
Committer: Martin Tzvetanov Grigorov <mg...@apache.org>
Committed: Fri Mar 25 13:59:21 2016 +0100

----------------------------------------------------------------------
 .../src/docs/guide/internals/autocomponents.gdoc              | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/wicket/blob/3cbe984f/wicket-user-guide/src/docs/guide/internals/autocomponents.gdoc
----------------------------------------------------------------------
diff --git a/wicket-user-guide/src/docs/guide/internals/autocomponents.gdoc b/wicket-user-guide/src/docs/guide/internals/autocomponents.gdoc
index 6e4f974..ee7ac07 100644
--- a/wicket-user-guide/src/docs/guide/internals/autocomponents.gdoc
+++ b/wicket-user-guide/src/docs/guide/internals/autocomponents.gdoc
@@ -35,12 +35,11 @@ public void init()
 }
 {code}
 
-Usually we won't need to change the defgitk
-ault configuration of @IMarkupFilters@S, but it's important to be aware of this internal mechanism before we talk about another advanced feature, which is building auto components resolvers.
+Usually we won't need to change the default configuration of @IMarkupFilters@S, but it's important to be aware of this internal mechanism before we talk about another advanced feature, which is building auto components resolvers.
 
 h3. Auto components resolvers
 
-Even if Wicket encourages developers to use just standard HTML in their markup code, in this guide we have seen a number of "special" tags (those starting with @wicket:@) that help us for specific tasks (think for example at the @wicket:enclosure@ tag). Wicket handles most of these tags creating a corresponding special component called _auto_ component. This kind of components are resolved in two steps:
+Even if Wicket encourages developers to use just standard HTML in their markup code, in this guide we have seen a number of "special" tags (those starting with @wicket:@) that help us for specific tasks (e.g. @wicket:enclosure@ tag). Wicket handles most of these tags creating a corresponding special component called _auto_ component. This kind of components are resolved in two steps:
 
 # first their tag is identified by a @IMarkupFilters@ which also takes care of assigning a unique tag id.
 # then during rendering phase when an auto-component is found a new component is created for it using one of the registered @org.apache.wicket.markup.resolver.IComponentResolver@:
@@ -64,7 +63,7 @@ public interface IComponentResolver extends IClusterable
 }
 {code}
 
-Registerd @IComponentResolver@S can be retrieved through Application's settings:
+Registered @IComponentResolver@s can be retrieved through Application's settings:
 
 {code}
 Application.get()