Apply suggestions from code review

Thank you Jaime!

Co-authored-by: Jaime Silvela <[email protected]>
Signed-off-by: Floor Drees <[email protected]>

Author: FloorD

content/blog/building-images-bake/index.md

@@ -22,13 +22,14 @@ summary: Creating a container image for CloudNativePG Operator v2.0
 ---
 
 ## Summary
-In an almost [two years old blog post]({{% ref "/blog/creating-container-images/" %}}), we explained how
-to build a custom container image for CloudNativePG. After two years, many things have changed in the world of containers.
+Almost two years ago, we wrote a [blog post on
+building custom container images for CloudNativePG]({{% ref "/blog/creating-container-images/" %}}).
+Since then, many things have changed in the world of containers.
 One of those things has been the introduction of [Bake](https://docs.docker.com/build/bake/) in Docker, which allows you to build
 images using a simple configuration file. Bake is now our recommended way to build images for CloudNativePG.
 
-We will follow a simple baking recipe to create a custom container image or a set of container images, since Bake
-allows you to build multiple images at once in a simple way.
+We will follow a simple baking recipe to create a custom container image.
+Bake will also allow you to easily build multiple images at the same time.
 
 ## Ingredients
 
@@ -81,7 +82,7 @@ EOT
 There are a few things that we should remark here:
 
 - The `extensions` variable is a list of extensions that we want to include in the image. In our recipe we are using `pg_vector`,
-  but you can add any other extension that you want to include in the image.
+  but you can add any other extension you want.
 - The `dockerfile-inline` variable contains our Dockerfile definition, which cannot be used remotely. We will explain more about this later.
 - The `target` and the `tgt` have the same name, you can use whatever you want here as a name
 - The `pgVersion` variable is a list that contains basically the MAJOR.MINOR version of PostgreSQL