singleton view-models and their child containers

The section on containers says: "Each time the Router navigates to a screen, it creates a child container to encapsulate all the resources related to that navigation event and then auto-registers the screen's view-model in that child container. As you know, auto-registration, by default, results in the view-model being registered as a singleton."

This is misleading because apparently the child container in which the view-model is registered is not itself a singleton and is disposed when the router navigates to another view. Thus, though the view-model may be a singleton, it does not appear to behave as one.

@singleton could be referenced here, with a clear description of what both true _and_ false parameters mean for view-models.

Locate the documentation section containing the quoted container and auto-registration explanation, then review the @singleton guidance referenced in the issue. Clarify how the true and false parameters affect view-models and explain the child container lifecycle so the documentation accurately describes the resulting behavior.

Written by the indexing model from the issue text.