[wicket] branch master updated: Fix index of a list item

[mg...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mgrigorov pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/wicket.git


The following commit(s) were added to refs/heads/master by this push:
     new c0fdc2e  Fix index of a list item
c0fdc2e is described below

commit c0fdc2eb3ce1dd519c9c817da3ea3fe9c0610a58
Author: Martin Tzvetanov Grigorov <mg...@apache.org>
AuthorDate: Tue May 4 17:33:46 2021 +0300

    Fix index of a list item
---
 .../src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc b/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc
index a2c778a..45df71c 100644
--- a/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc
+++ b/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc
@@ -6,7 +6,7 @@ During its life a Wicket component goes through the following stages:
 1. *Initialization:* a component is instantiated and initialized by Wicket.
 2. *Rendering:* components are prepared for rendering and generate markup. If a component contains children (i.e. is a subclass of _MarkupContainer_) their rendering result is included in the resulting markup.
 3. *Removed:* this stage is triggered when a component is explicitly removed from its component hierarchy, i.e. when its parent invokes _remove(component)_ on it. This stage is facultative and is never triggered for pages.
-3. *Detached:* after request processing has ended all components are notified to detach any state that is no longer needed. 
+4. *Detached:* after request processing has ended all components are notified to detach any state that is no longer needed.
 
 The following picture shows the state diagram of component lifecycle: