diff --git a/content/blog/2025-07-24-introducing-patternizer.adoc b/content/blog/2025-07-24-introducing-patternizer.adoc
index 79afe178c..dd2787a3b 100644
--- a/content/blog/2025-07-24-introducing-patternizer.adoc
+++ b/content/blog/2025-07-24-introducing-patternizer.adoc
@@ -44,7 +44,7 @@ Navigate to your repository's root and run the Patternizer container, mounting y
 +
 [source,bash]
 ----
-podman run -v "$PWD:/repo:z" quay.io/hybridcloudpatterns/patternizer init
+podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer init
 ----
 +
 This single command scans your repository for Helm charts and generates all the necessary files to turn it into a Validated Pattern.
@@ -88,7 +88,7 @@ Run the `init` command with the `--with-secrets` flag:
 
 [source,bash]
 ----
-podman run -v "$PWD:/repo:z" quay.io/hybridcloudpatterns/patternizer init --with-secrets
+podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer init --with-secrets
 ----
 
 This command updates your configuration to integrate with External Secrets Operator (ESO) and Vault. It generates a `values-secret.yaml.template` for defining your secrets and automatically adds the required operator subscriptions to your pattern.
diff --git a/content/blog/2025-08-29-new-common-makefile-structure.adoc b/content/blog/2025-08-29-new-common-makefile-structure.adoc
index 6ac92e111..7680c58ef 100644
--- a/content/blog/2025-08-29-new-common-makefile-structure.adoc
+++ b/content/blog/2025-08-29-new-common-makefile-structure.adoc
@@ -67,14 +67,14 @@ Adopting the new approach is straightforward whether you're bootstrapping a bran
 +
 [source,bash]
 ----
-podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer init
+podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer init
 ----
 +
 Add secrets scaffolding at any time with:
 +
 [source,bash]
 ----
-podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer init --with-secrets
+podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer init --with-secrets
 ----
 . Review the changes (`values-*.yaml`, `pattern.sh`, `Makefile`, `Makefile-common`), then commit.
 . Try it out:
@@ -95,7 +95,7 @@ Move from the legacy `common` structure to the new Makefile-driven setup with a
 
 [source,bash]
 ----
-podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer upgrade
+podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer upgrade
 ----
 
 What this does:
@@ -111,7 +111,7 @@ If you prefer to fully replace your `Makefile` with the default version, run:
 
 [source,bash]
 ----
-podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer upgrade --replace-makefile
+podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer upgrade --replace-makefile
 ----
 
 After upgrading, commit the changes and use the targets described below (for example, `./pattern.sh make show` or `./pattern.sh make install`).
@@ -341,7 +341,7 @@ Ready to try it? Run:
 
 [source,bash]
 ----
-podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer upgrade
+podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer upgrade
 ----
 
 and commit the changes. Your repo will instantly be on the new path.