From 399df5677bd116a016664a10a0da432da29e829d Mon Sep 17 00:00:00 2001 From: Scott Main Date: Mon, 2 Jul 2012 21:47:20 -0700 Subject: docs: various link fixes and other typos from external tracker Change-Id: I2a107f7e16429c0fe80c5e4cb67ecfaf267db301 --- docs/html/training/basics/activity-lifecycle/recreating.jd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/html/training/basics/activity-lifecycle') diff --git a/docs/html/training/basics/activity-lifecycle/recreating.jd b/docs/html/training/basics/activity-lifecycle/recreating.jd index 005a95b..3bbf0bb 100644 --- a/docs/html/training/basics/activity-lifecycle/recreating.jd +++ b/docs/html/training/basics/activity-lifecycle/recreating.jd @@ -32,7 +32,7 @@ href="{@docRoot}guide/topics/resources/runtime-changes.html">Handling Runtime Ch

There are a few scenarios in which your activity is destroyed due to normal app behavior, such as when the user presses the Back button or your activity signals its own destruction by -calling {@link android.app.Activity#finish()}. The system may also destory your activity if it's +calling {@link android.app.Activity#finish()}. The system may also destroy your activity if it's currently stopped and hasn't been used in a long time or the foreground activity requires more resources so the system must shut down background processes to recover memory.

-- cgit v1.1