Apply suggestions from code review

Co-authored-by: Malte Sander <malte.sander.it@gmail.com>

Author: sbernauer

docs/modules/nifi/pages/usage_guide/updating.adoc

@@ -2,7 +2,7 @@
 :description: Easily update or downgrade Apache NiFi on Kubernetes by changing the CRD version.
 
 Updating (or downgrading for that matter) the deployed version of NiFi is as simple as changing the version stated in the CRD.
-Continuing the example above, to change the deployed version from `2.6.0` to `2.7.2` you'd simply deploy the following CRD.
+Continuing the example above, the deployed version will be updated by deploying the following custom resource.
 
 [source,yaml]
 ----
@@ -24,7 +24,7 @@ NiFi clusters cannot be upgraded or downgraded in a rolling fashion due to a lim
 When upgrading between NiFi 1 versions or from NiFi 1 to NiFi 2, any change to the NiFi version in the CRD triggers a full cluster restart with brief downtime.
 However, the Stackable image version can be updated in a rolling manner, provided the NiFi version remains unchanged.
 
-For upgrades between NiFi 2 versions, e.g. from `2.6.0` to `2.7.2`, rolling upgrades are supported.
+Since NiFi version 2, rolling upgrades are supported.
 ====
 
 == NiFi 2.0.0

docs/modules/nifi/pages/usage_guide/writing-to-iceberg-tables.adoc

@@ -10,15 +10,15 @@ As of NiFi version `2.7.2` only `PutIceberg` is supported, you need to create an
 
 == NiFi 2.7 and above
 
-In NiFi `2.7.0` Iceberg support was https://issues.apache.org/jira/browse/NIFI-15062[re-added] after the removal in 2.0.0.
+In NiFi `2.7.0` Iceberg support was https://issues.apache.org/jira/browse/NIFI-15062[re-added] after the removal in `2.0.0`.
 
-The 2.7 version has the following changes over the 2.0/2.6 version, you need to adopt your setup accordingly:
+The `2.7.x` version has the following changes over the `2.0.x` and `2.6.x` version, you need to adopt your setup accordingly:
 
 * HDFS and Kerberos support was dropped
 * Hive metastore support was dropped
 * Iceberg REST catalog support was added
 * It now uses the Iceberg S3 IO instead of the Hadoop S3 client libraries
-* It uses much less dependencies and therefore CVEs
+* It uses much less dependencies and therefore reduces the amount of CVEs
 
 There have been efforts from Stackable to re-add at least Hive metastore support, but that turned out to be complicated.