Merge branch 'main' into runext/demo

Author: Natalie Arellano

Makefile

@@ -43,7 +43,7 @@ endif
 endif
 
 ifeq ($(shell uname -s),Darwin)
-	HUGO_OS:=macOS
+	HUGO_OS:=darwin
 	HUGO_ARCH:=universal
 endif
 
@@ -139,7 +139,7 @@ build: $(HUGO_BIN) pack-version pack-docs-update
 .PHONY: test
 test: install-pack-cli check-pack-cli-version install-ugo
 	@echo "> Testing..."
-	ugo run -r -p ./content/docs/
+	ugo run -v -r -p ./content/docs/
 
 .PHONY: htmltest-install
 htmltest-install:
@@ -188,4 +188,4 @@ katacoda:
 check-katacoda: katacoda
 	@echo "Checking if Katacoda docs are up-to-date..."
 	@git diff --quiet HEAD -- katacoda/scenarios || ( echo "Katacoda docs are not up-to-date! Please run 'make katacoda' and commit the katacoda/scenarios folder" && exit 1)
-	@echo "All katacoda docs are up-to-date"
+	@echo "All katacoda docs are up-to-date"

RELEASE.md

@@ -15,15 +15,15 @@ Some use cases in which this may be desired...
 ### Process
 
 1. A milestone in the following format is created: `<component(s)>/<version>` <sup>*</sup>
-1. Issues are created and tagged with appropriete milestone.
+1. Issues are created and tagged with appropriate milestone.
 1. A release branch in the following format is created off of `main`: `release/<component(s)>/<version>` <sup>*</sup>
 1. As changes are completed, PRs would target the release branch and merged using the same guidelines as merging to `main`.
-1. Once all issues and/or the associated component release is shipped, the release branch is merged into `main` by subteam maintainers.
+1. Once all issues and/or the associated component release is shipped, the release branch is merged into `main` by sub-team maintainers.
 
 _* may require a [project contributor or maintainer](https://github.com/buildpacks/community/blob/main/TEAMS.md) intervention._
 
 
-##### Example Namings
+##### Example Naming
 
 Branches:
 
@@ -42,7 +42,7 @@ Milestones:
 
 ##### Example Workflow
 
-Let's imagine `pack` is releasing version `1.2.3`. It is known that there will be a decent amount of changes to a few guides and we'd like to seperate the entire set of changes per guide. The steps that would be taken are as follows:
+Let's imagine `pack` is releasing version `1.2.3`. It is known that there will be a decent amount of changes to a few guides and we'd like to separate the entire set of changes per guide. The steps that would be taken are as follows:
 
 1. A milestone `pack/1.2.3` would be created.
 1. Issues for the necessary changes would be tagged with milestone `pack/1.2.3`.

content/community.md

@@ -15,7 +15,7 @@ Partake in one or many of our following public events:
 
 #### How can I start contributing?
 
-If you are new to the project, the first thing you should do is gain some understanding of the project. This normaly entails doing the following:
+If you are new to the project, the first thing you should do is gain some understanding of the project. This normally entails doing the following:
 
 1. Watch a few [talks (videos)][talks].
 2. Next, run through some [tutorials][tutorials].
@@ -30,7 +30,7 @@ If you didn't find anything you'd like to improve while going through the tutori
 | [`lifecycle`][lifecycle] | Go, Docker             | Executables that implement the main [specifications][spec] and are used by [platforms][platforms] such as `pack`.
 | [`docs`][docs]           | Hugo, HTML, JavaScript | Main website and documentation.
 
-> Dependending our your depth of understading or desires some components may be more ideal than others.
+> Depending our your depth of understanding or desires some components may be more ideal than others.
 
 [talks]: /docs/#talks
 [tutorials]: /docs/#tutorials

content/docs/app-developer-guide/build-an-app.md

@@ -31,7 +31,7 @@ pack builder suggest
 ```
 <!--+- "{{execute}}"+-->
 
-For this guide we're actually going to use a sample builder, `cnbs/sample-builder:bionic`, which is not listed
+For this guide we're actually going to use a sample builder, `cnbs/sample-builder:jammy`, which is not listed
 as a suggested builder for good reason. It's a sample.
 
 ### 2. Build your app
@@ -47,12 +47,12 @@ ls samples || git clone https://github.com/buildpacks/samples
 
 2. Build the app
 ```
-pack build sample-app --path samples/apps/java-maven --builder cnbs/sample-builder:bionic
+pack build sample-app --path samples/apps/java-maven --builder cnbs/sample-builder:jammy
 ```
 <!--+- "{{execute}}"+-->
 
 > **TIP:** If you don't want to keep specifying a builder every time you build, you can set it as your default
-> builder by running `pack config default-builder <BUILDER>` for example `pack config default-builder cnbs/sample-builder:bionic`
+> builder by running `pack config default-builder <BUILDER>` for example `pack config default-builder cnbs/sample-builder:jammy`
 <!--+- "{{execute}}"+-->
 
 ### 3. Run it

content/docs/app-developer-guide/build-an-arm-app.md

@@ -74,8 +74,8 @@ docker run --rm \
   --volume ~/workspace/platform:/platform \
   --mount type=bind,source=~/workspace/order.toml,target=/cnb/order.toml \
   --env CNB_PLATFORM_API=0.7 \
-  ubuntu:bionic \
-  /cnb/lifecycle/creator -log-level debug -daemon -run-image ubuntu:bionic hello-arm64
+  ubuntu:jammy \
+  /cnb/lifecycle/creator -log-level debug -daemon -run-image ubuntu:jammy hello-arm64
 ```
 
 ### 4. Run it

content/docs/app-developer-guide/building-on-podman.md

@@ -47,7 +47,7 @@ git clone https://github.com/buildpacks/samples
 ![](https://i.imgur.com/0mmV6K7.png)
 
 ```shell=bash
-pack build sample-app -p samples/apps/ruby-bundler/ -B cnbs/sample-builder:bionic
+pack build sample-app -p samples/apps/ruby-bundler/ -B cnbs/sample-builder:jammy
 ```
 
 Where:

content/docs/app-developer-guide/environment-variables.md

@@ -30,7 +30,7 @@ export FOO=BAR
 pack build sample-app \
     --env "HELLO=WORLD" \
     --env "FOO" \
-    --builder cnbs/sample-builder:bionic \
+    --builder cnbs/sample-builder:jammy \
     --buildpack  samples/buildpacks/hello-world/ \
     --buildpack samples/apps/bash-script/bash-script-buildpack/ \
     --path  samples/apps/bash-script/
@@ -76,7 +76,7 @@ echo -en "HELLO=WORLD\nFOO" > ./envfile
 ```
 pack build sample-app \
     --env-file ./envfile \
-    --builder cnbs/sample-builder:bionic \
+    --builder cnbs/sample-builder:jammy \
     --buildpack  samples/buildpacks/hello-world/ \
     --buildpack samples/apps/bash-script/bash-script-buildpack/ \
     --path  samples/apps/bash-script/
@@ -122,7 +122,7 @@ EOL
 2. Build the app
 ```
 pack build sample-app \
-    --builder cnbs/sample-builder:bionic \
+    --builder cnbs/sample-builder:jammy \
     --buildpack  samples/buildpacks/hello-world/ \
     --buildpack samples/apps/bash-script/bash-script-buildpack/ \
     --path  samples/apps/bash-script/

content/docs/app-developer-guide/mounting-volumes.md

@@ -87,7 +87,7 @@ Now, we can mount this volume during `pack build`:
 ```bash
 ls -al
 pack build volume-example \
-    --builder cnbs/sample-builder:bionic \
+    --builder cnbs/sample-builder:jammy \
     --buildpack samples/buildpacks/hello-world \
     --path samples/apps/bash-script \
     --volume test-volume:/platform/volume:ro

content/docs/app-developer-guide/specify-buildpacks.md

@@ -102,7 +102,7 @@ A buildpack located in a CNB Registry
 - `urn:cnb:registry:[email protected]`
 
 <small><sup>†</sup> Directory buildpacks are not currently supported on Windows.</small><br />
-<small><sup>‡</sup> Version may be omited if there is only one buildpack in the builder matching the `id`.</small>
+<small><sup>‡</sup> Version may be omitted if there is only one buildpack in the builder matching the `id`.</small>
 
 [project-toml]: /docs/app-developer-guide/using-project-descriptor/
 [samples]: https://github.com/buildpacks/samples

content/docs/app-developer-guide/using-cache-image.md

@@ -29,10 +29,10 @@ For the following examples we will use:
 > **NOTE:**  If we wish to publish to an external registry like `Dockerhub` we will first need to authenticate with `docker` to allow us to push images. We can do this via `docker login`
 
 
-Next we trust the `cnbs/sample-builder:bionic` builder in order to allow access to docker credentials when publishing.
+Next we trust the `cnbs/sample-builder:jammy` builder in order to allow access to docker credentials when publishing.
 
 ```
-pack config trusted-builders add cnbs/sample-builder:bionic
+pack config trusted-builders add cnbs/sample-builder:jammy
 ```
 <!--+- "{{execute}}"+-->
 
@@ -42,7 +42,7 @@ To build the `localhost:5000/buildpack-examples/cache-image-example` application
 
 ```
 pack build localhost:5000/buildpack-examples/cache-image-example \
-    --builder cnbs/sample-builder:bionic \
+    --builder cnbs/sample-builder:jammy \
     --buildpack samples/java-maven \
     --path samples/apps/java-maven \
     --cache-image localhost:5000/buildpack-examples/maven-cache-image:latest \
@@ -76,7 +76,7 @@ builds may also update the specified `cache-image`.
 The following command will restore data for the `samples/java-maven:maven_m2` layer from the cache image.
 ```
 pack build localhost:5000/buildpack-examples/second-cache-image-example \
-    --builder cnbs/sample-builder:bionic \
+    --builder cnbs/sample-builder:jammy \
     --buildpack samples/java-maven \
     --path samples/apps/java-maven \
     --cache-image localhost:5000/buildpack-examples/maven-cache-image:latest \