Apply suggestions from SME review

Author: kbatuigas

modules/manage/partials/iceberg/use-iceberg-catalogs.adoc

@@ -33,19 +33,25 @@ Redpanda uses the bearer token unconditionally and does not attempt to refresh t
 
 For REST catalogs that use self-signed certificates, also configure these properties:
 
-* config_ref:iceberg_rest_catalog_trust_file,true,properties/cluster-properties[`iceberg_rest_catalog_trust_file`]: The path to a file containing a certificate chain to trust for the REST catalog.
-* config_ref:iceberg_rest_catalog_crl_file,true,properties/cluster-properties[`iceberg_rest_catalog_crl_file`]: The path to the certificate revocation list for the specified trust file.
+* config_ref:iceberg_rest_catalog_trust,true,properties/cluster-properties[`iceberg_rest_catalog_trust`]: The contents of a certificate chain to trust for the REST catalog. 
+ifndef::env-cloud[]
+** Or, use config_ref:iceberg_rest_catalog_trust_file,true,properties/cluster-properties[`iceberg_rest_catalog_trust_file`] to specify the path to the certificate chain file.
+endif::[]
+* config_ref:iceberg_rest_catalog_crl,true,properties/cluster-properties[`iceberg_rest_catalog_crl`]: The contents of a certificate revocation list for `iceberg_rest_catalog_trust`.
+ifndef::env-cloud[]
+** Or, use config_ref:iceberg_rest_catalog_crl_file,true,properties/cluster-properties[`iceberg_rest_catalog_crl_file`] to specify the path to the certificate revocation list file.
+endif::[]
 
 See xref:reference:properties/cluster-properties.adoc[Cluster Configuration Properties] for the full list of cluster properties to configure for a catalog integration.
 
 ifdef::env-cloud[]
 === Store a secret for REST catalog authentication
 
-To store a secret that you can reference in your catalog authentication cluster properties, you must create the secret using `rpk` or the Cloud API. Secrets are stored in the secret management solution of your cloud provider. Redpanda retrieves the secrets at runtime. 
+To store a secret that you can reference in your catalog authentication cluster properties, you must create the secret using `rpk` or the Data Plane API. Secrets are stored in the secret management solution of your cloud provider. Redpanda retrieves the secrets at runtime. 
 
 To learn more about `rpk` and the Cloud API, see xref:manage:rpk/intro-to-rpk.adoc[] and xref:manage:api/cloud-api-overview.adoc[].
 
-Store secrets for the following properties:
+If you need to configure any of the following properties, you must set their values using secrets:
 
 * `iceberg_rest_catalog_client_secret`
 * `iceberg_rest_catalog_crl`
@@ -91,7 +97,7 @@ You must include the following values:
 - This scope: `"SCOPE_REDPANDA_CLUSTER"`.
 
 +
-The response returns the name of the secret and the scope `"SCOPE_REDPANDA_CLUSTER"`.
+The response returns the name and scope of the secret.
 
 You can now <<use-a-secret-in-cluster-configuration,reference the secret in your cluster configuration>>.
 
@@ -100,7 +106,7 @@ You can now <<use-a-secret-in-cluster-configuration,reference the secret in your
 
 === Use a secret in cluster configuration
 
-To set the cluster property to use the value of the secret, use `rpk` or the Cloud API.
+To set the cluster property to use the value of the secret, use `rpk` or the Control Plane API.
 
 For example, to use a secret for the `iceberg_rest_catalog_client_secret` property, run the following:
 
@@ -111,7 +117,7 @@ rpk::
 --
 [,bash]
 ----
-rpk cluster config set iceberg_rest_catalog_client_secret <secret-name>
+rpk cluster config set iceberg_rest_catalog_client_secret ${secrets.<secret-name>}
 ----
 --