[camel-k] 02/03: Using a variable for the version.

[ac...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch release-1.9.x
in repository https://gitbox.apache.org/repos/asf/camel-k.git

commit a9174758ddc90be951b9e0d218b159a074368275
Author: María Arias de Reyna <de...@gmail.com>
AuthorDate: Tue May 17 09:44:07 2022 +0200

    Using a variable for the version.
---
 docs/modules/ROOT/pages/contributing/local-development.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/modules/ROOT/pages/contributing/local-development.adoc b/docs/modules/ROOT/pages/contributing/local-development.adoc
index 78f56aa72..38926ac90 100644
--- a/docs/modules/ROOT/pages/contributing/local-development.adoc
+++ b/docs/modules/ROOT/pages/contributing/local-development.adoc
@@ -62,23 +62,23 @@ A similar procedure may work if you use other local environments. The idea is to
 
 Camel K integrations are based on https://github.com/apache/camel-k-runtime[Camel K runtime], generally paired with the operator release. If you need to specify a different runtime, or you have a local Camel K runtime that you want to test, then you will need to specify it in the `Integration Platform`:
 ----
-./kamel install --skip-operator-setup -n operator-test --registry localhost:5000 --force --runtime-version 1.7.0-SNAPSHOT
+./kamel install --skip-operator-setup -n operator-test --registry localhost:5000 --force --runtime-version $version
 ----
 
-With the above instructions, the operator will pick up and use the snapshot version you have released locally.
+The `$version` variable must be replaced with the version you are building. For example, `1.3.1-SNAPSHOT`. With these instructions, the operator will pick up and use the snapshot version you have released locally.
 
 ==== Using a Docker registry
 
 Alternatively, if no local registry is available, you can use a docker registry. First, create a secret with your registry username and password:
 
 ```
-kubectl -n default create secret docker-registry external-registry-secret --docker-username my-user --docker-password "password"
+kubectl -n default create secret docker-registry external-registry-secret --docker-username $my-user --docker-password "$password"
 ```
 
 And then you can run the installation of Camel K operator:
 
 ```
-./kamel install --skip-operator-setup -n operator-test --force --runtime-version 1.7.0-SNAPSHOT --registry docker.io --organization my-org-or-username --registry-secret external-registry-secret 
+./kamel install --skip-operator-setup -n operator-test --force --runtime-version $version --registry docker.io --organization $my-org-or-username --registry-secret external-registry-secret 
 ```
 
-Make sure to replace the `my-org-or-username` with your actual username or organization used to host the images.
+Make sure to replace the `$my-org-or-username` with your actual username or organization used to host the images and the `$version` with the appropiate version number.