A context is an instance of the transition type. In that sense, we could imagine our Place User behavior in this way:

Multiple context instances
Each context needs to keep track which state is currently processed. There is no single current state, but each context has a state pointer which shows which state is currently the one with respect to this context. One could also say:
The current state of the Place User is the tuple of all current states of all contexts.
We have three classes of states, acording to the definitions shown for the Hybrid type system.
As a convention, we call a state nonstable when it is not stable, i.e. when it is unstable or semistable.
The connections (transitions) between states are fixed, as are their modes, too. That is, you cannot make a state stable when it was unstable. This would mean changing the transition type of the Place User, or effectively changing the behavior of your PU. Of course, the same is true for changes of other modes, and for changes of transitions.
Therefore, it is reasonable to define the context mode:
A context is stable (unstable, semistable) if and only if its current state is stable (unstable, semistable).
Hence, a nonstable context is in a nonstable state.
We sometimes call contexts spontaneous contexts when they are in a nonstable initial state.