fixup! Reflect API 0.7 move to RESTORING

AidanDelaney · AidanDelaney · commit b92815787c41 · 2022-09-17T14:14:46.000+01:00
Signed-off-by: Aidan Delaney &lt;adelaney21@bloomberg.net&gt;
diff --git a/katacoda/scenarios/buildpack-author-guide/detection.md b/katacoda/scenarios/buildpack-author-guide/detection.md
@@ -46,5 +46,5 @@ ERROR: failed to build: executing lifecycle: failed with status code: 51
 
 Notice that `detect` now passes because there is a valid `Gemfile` in the Ruby app at `ruby-sample-app`, but now `build` fails because it is currently written to error out.
 
-You will also notice that `ANALYZING` now appears in the build output. This step is part of the buildpack lifecycle that looks to see if any previous image builds have layers that the buildpack can re-use. We will get into this topic in more detail later.
+You will also notice that `RESTORING` now appears in the build output. This step is part of the buildpack lifecycle that looks to see if any previous image builds have layers that the buildpack can re-use. We will get into this topic in more detail later.
 

Original file line number	Diff line number	Diff line change
`@@ -46,5 +46,5 @@ ERROR: failed to build: executing lifecycle: failed with status code: 51`
`46`	`46`
`47`	`47`	Notice that `detect` now passes because there is a valid `Gemfile` in the Ruby app at `ruby-sample-app`, but now `build` fails because it is currently written to error out.
`48`	`48`
`49`		-You will also notice that `ANALYZING` now appears in the build output. This step is part of the buildpack lifecycle that looks to see if any previous image builds have layers that the buildpack can re-use. We will get into this topic in more detail later.
	`49`	+You will also notice that `RESTORING` now appears in the build output. This step is part of the buildpack lifecycle that looks to see if any previous image builds have layers that the buildpack can re-use. We will get into this topic in more detail later.
`50`	`50`