remove floating tag references

Author: maltesander

modules/concepts/pages/product-image-selection.adoc

@@ -67,11 +67,7 @@ If the Kubernetes cluster does not have internet access, a xref:_custom_docker_r
 Currently, you need to specify the product version. This can be found on the xref:operators:supported_versions.adoc[list of supported product versions] or on the website of the product itself.
 This requirement might be relaxed in the future, as every platform release will ship wth a recommended product versions, which will be used by default.
 
-Additionally, you can specify the Stackable version: As we need to make changes to the Images from time to time (e.g. security updates), we also have to version them using the Stackable version. An image gets released for every version of the SDP.
-There are two variants you can choose from:
-
-1. Fixed version, e.g. `23.7.0`. This image will never change.
-2. Release line, e.g. `23.7`. This will be a floating tag pointing to the latest patch release of the SDP release line. It will contain the latest security patches, but will also change over time.
+Additionally, as images must be updated from time to time (e.g. new base image, security updates), a Stackable version can be provided. An image with the Stackable version `23.7.0` is fixed and will never change. Security updates within a release line will result in patch version bumps in the Stackable version to e.g. `23.7.1`.
 
 If you don't specify the Stackable version, the operator will use its own version, e.g. `23.7.0`.
 When using a nightly operator or a `pr` version, it will use the nightly `0.0.0-dev` image.
@@ -137,7 +133,7 @@ When deriving images from official Stackable images this will mean updating the
 The recommended process here is:
 
 ** Tag clusters as "do not reconcile" (see xref:operations/cluster_operations.adoc[])
-** Update Stackable plattform
+** Update Stackable platform
 ** Change custom images in cluster specifications
 ** Remove "do not reconcile flag"
 
@@ -157,7 +153,7 @@ spec:
 ----
 
 ### Quick updates of images
-Sometimes it can be useful to decouple operators upgrades from the image versions to allow using updated images as soons as Stackable releases them.
+Sometimes it can be useful to decouple operators upgrades from the image versions to allow using updated images as soon as Stackable releases them.
 This can significantly shorten turnaround times when reacting to security vulnerabilities for example.
 
 For this scenario the Stackable version can be set to the release line, without including the patch level indicator.
@@ -180,10 +176,8 @@ spec:
     stackableVersion: 23.4
 ----
 
-
-
 #### Custom images / pinned images
-When a setup requires the utmost stability and it is preferrable for things to break, rather than run with a different image version that for example has not been certified.
+When a setup requires the utmost stability, and it is preferable for things to break, rather than run with a different image version that for example has not been certified.
 Or when a user requires custom libraries / code in the images they run and build their own images derived from official Stackable images, this is the only possible way to do this.
 
 Please see the warnings in <<customimages, custom images section>> above for how to upgrade in this scenario.