From 0fbeb6d2cd417f0ca60c01c553129375805d45c3 Mon Sep 17 00:00:00 2001
From: Stefan Prodan <stefan.prodan@gmail.com>
Date: Fri, 12 Feb 2021 18:23:25 +0200
Subject: [PATCH] Update semver flag in image update guide

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
---
 docs/guides/image-update.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/guides/image-update.md b/docs/guides/image-update.md
index 929deca1..c2623759 100644
--- a/docs/guides/image-update.md
+++ b/docs/guides/image-update.md
@@ -170,7 +170,7 @@ Create an `ImagePolicy` to tell Flux which semver range to use when filtering ta
 ```sh
 flux create image policy podinfo \
 --image-ref=podinfo \
---semver=5.0.x \
+--select-semver=5.0.x \
 --export > ./clusters/my-cluster/podinfo-policy.yaml
 ```
 
@@ -471,7 +471,7 @@ Assuming you've configured Flux to update an app to its latest stable version:
 ```sh
 flux create image policy podinfo \
 --image-ref=podinfo \
---semver=">=5.0.0"
+--select-semver=">=5.0.0"
 ```
 
 If the latest version e.g. `5.0.1` causes an incident in production, you can tell Flux to 
@@ -480,7 +480,7 @@ revert the image tag to a previous version e.g. `5.0.0` with:
 ```sh
 flux create image policy podinfo \
 --image-ref=podinfo \
---semver=5.0.0
+--select-semver=5.0.0
 ```
 
 Or by changing the semver range in Git:
@@ -505,7 +505,7 @@ and tell Flux to consider only versions greater than `5.0.1`:
 ```sh
 flux create image policy podinfo \
 --image-ref=podinfo \
---semver=">5.0.1"
+--select-semver=">5.0.1"
 ```
 
 ## ImageRepository cloud providers authentication