Merge branch 'main' into fix-518

AidanDelaney · web-flow · commit 4c4f58b3c3cc · 2022-09-30T07:05:15.000-04:00
diff --git a/content/docs/_index.md b/content/docs/_index.md
@@ -58,4 +58,4 @@ Find out the various ways that _you_ can contribute to the Cloud Native Buildpac
 
 ## Project Roadmap
 
-This is a community driven project and our roadmap is publicly available on our [Github page](https://github.com/orgs/buildpacks/projects/1). We encourage you to contribute with feature requests.
+This is a community driven project and our roadmap is publicly available on our [Github page](https://github.com/buildpacks/community/blob/main/ROADMAP.md). We encourage you to contribute with feature requests.
diff --git a/content/docs/buildpack-author-guide/create-buildpack/detection.md b/content/docs/buildpack-author-guide/create-buildpack/detection.md
@@ -50,7 +50,7 @@ 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.
 
 <!--+if false+-->
 ---
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
`@@ -58,4 +58,4 @@ Find out the various ways that _you_ can contribute to the Cloud Native Buildpac`
`58`	`58`
`59`	`59`	`## Project Roadmap`
`60`	`60`
`61`		`-This is a community driven project and our roadmap is publicly available on our [Github page](https://github.com/orgs/buildpacks/projects/1). We encourage you to contribute with feature requests.`
	`61`	`+This is a community driven project and our roadmap is publicly available on our [Github page](https://github.com/buildpacks/community/blob/main/ROADMAP.md). We encourage you to contribute with feature requests.`
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`