Author: mgrigorov
Date: Tue Jul 26 15:35:34 2011
New Revision: 1151140
URL: http://svn.apache.org/viewvc?rev=1151140&view=rev
Log:
Fix typos in comments
Modified:
wicket/trunk/wicket-core/src/main/java/org/apache/wicket/MarkupContainer.java
wicket/trunk/wicket-core/src/main/java/org/apache/wicket/markup/html/panel/DefaultMarkupSourcingStrategy.java
Modified:
wicket/trunk/wicket-core/src/main/java/org/apache/wicket/MarkupContainer.java
URL:
http://svn.apache.org/viewvc/wicket/trunk/wicket-core/src/main/java/org/apache/wicket/MarkupContainer.java?rev=1151140&r1=1151139&r2=1151140&view=diff
==============================================================================
---
wicket/trunk/wicket-core/src/main/java/org/apache/wicket/MarkupContainer.java
(original)
+++
wicket/trunk/wicket-core/src/main/java/org/apache/wicket/MarkupContainer.java
Tue Jul 26 15:35:34 2011
@@ -177,7 +177,7 @@ public abstract class MarkupContainer ex
// Check if the markup is available after the
child has been added to the parent
try
{
- // If not yet triggered, than do now
(e.g. Pages)
+ // If not yet triggered, then do now
(e.g. Pages)
if (getMarkup() != null)
{
internalOnMarkupAttached();
Modified:
wicket/trunk/wicket-core/src/main/java/org/apache/wicket/markup/html/panel/DefaultMarkupSourcingStrategy.java
URL:
http://svn.apache.org/viewvc/wicket/trunk/wicket-core/src/main/java/org/apache/wicket/markup/html/panel/DefaultMarkupSourcingStrategy.java?rev=1151140&r1=1151139&r2=1151140&view=diff
==============================================================================
---
wicket/trunk/wicket-core/src/main/java/org/apache/wicket/markup/html/panel/DefaultMarkupSourcingStrategy.java
(original)
+++
wicket/trunk/wicket-core/src/main/java/org/apache/wicket/markup/html/panel/DefaultMarkupSourcingStrategy.java
Tue Jul 26 15:35:34 2011
@@ -97,7 +97,7 @@ public final class DefaultMarkupSourcing
}
// If the child has not been directly added to the container,
but via a
- // TransparentWebMarkupContainer, than we are in trouble. In
general Wicket iterates over
+ // TransparentWebMarkupContainer, then we are in trouble. In
general Wicket iterates over
// the markup elements and searches for associated components,
not the other way around.
// Because of TransparentWebMarkupContainer (or more generally
resolvers), there is no
// "synchronous" search possible.
