diff --git a/content/blog/building-images-bake/baked_elephant.png b/content/blog/building-images-bake/baked_elephant.png
new file mode 100644
index 000000000..71649d9d9
Binary files /dev/null and b/content/blog/building-images-bake/baked_elephant.png differ
diff --git a/content/blog/building-images-bake/index.md b/content/blog/building-images-bake/index.md
index fa286e794..694071c72 100644
--- a/content/blog/building-images-bake/index.md
+++ b/content/blog/building-images-bake/index.md
@@ -2,6 +2,10 @@
 title: "Creating a custom container image for CloudNativePG v2.0"
 date: 2025-07-23
 draft: false
+image:
+    url: baked_elephant.png
+    alt: "Baked elephant cookies"
+    attribution:
 author: jgonzalez
 tags:
  - blog
@@ -21,7 +25,7 @@ summary: Using Docker's Bake to create container images for the CloudNativePG Op
 ## Summary
 Nearly two years ago, we shared a [blog post on building custom container 
 images for CloudNativePG]({{% ref "/blog/creating-container-images/" %}}). Since then, the container ecosystem has evolved 
-significantly—one notable development being the introduction of [Docker Bake]((https://docs.docker.com/build/bake/)).
+significantly—one notable development being the introduction of [Docker Bake](https://docs.docker.com/build/bake/).
 
 Docker Bake simplifies image builds using a straightforward configuration file, 
 and it’s now our recommended approach for building CloudNativePG images.
@@ -48,7 +52,7 @@ extensions = [
 target "myimage" {
   dockerfile-inline = <<EOT
 ARG BASE_IMAGE="ghcr.io/cloudnative-pg/postgresql:16.9-standard-bookworm"
-FROM $BAS_EIMAGE AS myimage
+FROM $BASE_IMAGE AS myimage
 ARG EXTENSIONS
 USER root
 RUN apt-get update && \