anchor.diff:  public abstract Class<? extends Page> getHomePage()
   ----
   
  -As you may guess from its name, this method specifies which page to use as homepage for our application. 
  +As you may guess from its name, this method specifies which page to use as a homepage for our application.
   Another important method is _init()_:
   
   [source,java]
  
positive.code: }
  ----
  
  Since this is a very basic example of a Wicket application, we don't need to specify anything inside the _init_ method. The home page of the application is the _HomePage_ class. In the next paragraph we will see how this page is implemented and which conventions we have to follow to create a page in Wicket.
  
  NOTE: Declaring a _WicketFilter_ inside web.xml descriptor is not the only way we have to kickstart our application.
  If we prefer to use a servlet instead of a filter, we can use class _org.apache.wicket.protocol.http.WicketServlet_. See the JavaDoc for further details.
  
  
negative.code: 
  In this chapter we will see a classic Hello World! example implemented using a Wicket page with a built-in component called _Label_ (the code is from the HelloWorldExample project). Since this is the first example of the guide, before looking at Java code we will go through the common artifacts needed to build a Wicket application from scratch.
  
  NOTE: All the example projects presented in this document have been generated using Maven and the utility page at  http://wicket.apache.org/start/quickstart.html[http://wicket.apache.org/start/quickstart.html] . *Appendix A* contains the instructions needed to use these projects and build a quickstart application using Apache Maven. All the artifacts used in the next example (files web.xml, HomePage.class and HomePage.html) are automatically generated by Maven.
  
  