- * An application can be terminated by either system, such as power-off and OOM, or others, such as self and other applications. @n
- * When the termination by system, called an “urgent termination”, occurs, the method, %OnAppTerminating(), cannot be executed properly.
- * For more details, while power-off, even if %OnAppTerminating() is called, it has a short time for executing. If the application is killed by OOM, %OnAppTerminating() is not called. @n
- * Because %OnAppTerminating() is not likely to be called due to urgent termination, the application should save the critical data as they can do.
- * For example, the application can set the check point or use the callback for low memory. @n
- * When the termination by self or other applications, called a “normal termination”, occurs, the method, %OnAppTerminating(), can be executed properly.
- * It provides more time for executing than urgent termination, but limits to the time to 3 or 5 seconds. @n
- * The main loop is already quitted when %OnAppTerminating() is called.
- * Thus, the application should not use a kind of asynchronous API of which the callback is triggered by the main loop.
+ * An application's termination is triggered either by the system or by other applications. @n
+ * When the termination is triggered by the system because of conditions, such as power-off, and OOM, it is called "urgent termination" and during these terminations the %OnAppTerminating() method cannot be executed properly.
+ * When an application is terminated because of a power-off, although this method is called, it should be executed in a short duration. And when an application is killed by OOM, this method is not called. @n
+ * This implies that this method is not likely to be called during an urgent termination, and hence the application should save its critical data as often as possible.
+ * For example, the application can set a check point or use a callback for low memory issues.
+ * When an application terminates itself or is terminated by other applications, it is called "normal termination" and during these terminations this method is executed properly because more time is provided for execution as compared to an urgent termination (however, it does have a limit of 3-5 seconds). @n
+ * When this method is called, the main loop has already been quit.
+ * Thus, the application should not use any kind of asynchronous API that has callbacks triggered by the main loop.