From 88041d19553e7a70cc5c34ed8e362e99fba630a4 Mon Sep 17 00:00:00 2001 From: Jared Ezzet Hasson Date: Mon, 29 Oct 2018 08:53:44 -0600 Subject: [PATCH] onDestroy() explanation (#20344) Gave an instance of when the onDestroy call would be used in practice --- guide/english/android-development/core-components/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/english/android-development/core-components/index.md b/guide/english/android-development/core-components/index.md index 635829239c..9cfbfcc13b 100644 --- a/guide/english/android-development/core-components/index.md +++ b/guide/english/android-development/core-components/index.md @@ -43,7 +43,7 @@ An _activity_ is a component that has a user interface and represents a single s * onDestroy(): -> The final call you receive before your activity is destroyed. This can happen either because the activity is finishing (someone called finish() on it, or because the system is temporarily destroying this instance of the activity to save space. You can distinguish between> these two scenarios with the isFinishing() method. +> The final call you receive before your activity is destroyed. This can happen either because the activity is finishing (someone called finish() on it, or because the system is temporarily destroying this instance of the activity to save space. You can distinguish between> these two scenarios with the isFinishing() method. This call is often used when the user hits the back button, or closes the instance of the app. #### Sample code to understand Activity Lifecycle ``` java