Review comments addressed

src/jekyll/README.md

@@ -35,9 +35,9 @@ You can directly reference pre-built versions of `Dockerfile` by using the `imag
 - `mcr.microsoft.com/devcontainers/jekyll:buster`
 
 You can decide how often you want updates by referencing a [semantic version](https://semver.org/) of each image. For example:
-- `mcr.microsoft.com/devcontainers/jekyll:3` (or `3-bookworm`, `3-bullseye` to pin to an OS version)
-- `mcr.microsoft.com/devcontainers/jekyll:3.0` (or `3.0-bookworm`, `3.0-bullseye`  to pin to an OS version)
-- `mcr.microsoft.com/devcontainers/jekyll:3.0.0` (or `3.0.0-bookworm`, `3.0.0-bullseye` to pin to an OS version)
+- `mcr.microsoft.com/devcontainers/jekyll:2` (or `2-bookworm`, `2-bullseye` to pin to an OS version)
+- `mcr.microsoft.com/devcontainers/jekyll:2.0` (or `2.0-bookworm`, `2.0-bullseye`  to pin to an OS version)
+- `mcr.microsoft.com/devcontainers/jekyll:2.2.0` (or `2.2.0-bookworm`, `2.2.0-bullseye` to pin to an OS version)
 
 
 However, we only do security patching on the latest [non-breaking, in support](https://github.com/devcontainers/images/issues/90) versions of images (e.g. `2-bullseye`). You may want to run `apt-get update && apt-get upgrade` in your Dockerfile if you lock to a more specific version to at least pick up OS security updates.

src/jekyll/manifest.json

@@ -32,7 +32,6 @@
 				"jekyll:${VERSION}-bookworm"
 			],
 			"3.3-bookworm": [
-				"jekyll:${VERSION}",
 				"jekyll:${VERSION}-bookworm"
 			],
 			"3.3-bullseye": [