Apply suggestions from code review

Co-authored-by: Angela Simms <102690377+asimms41@users.noreply.github.com>

Author: kbatuigas

modules/manage/pages/topic-iceberg-integration.adoc

@@ -55,7 +55,7 @@ In the Redpanda Iceberg integration, the manifest files are in JSON format.
 
 image::shared:iceberg-integration.png[]
 
-When you enable the Iceberg integration for a Redpanda topic, Redpanda brokers store streaming data in the Iceberg-compatible format in Parquet files in object storage, in addition to the log segments uploaded via Tiered Storage. Storing the streaming data in Iceberg tables in the cloud allows you to derive real-time insights through many compatible data lakehouse, data engineering, and business intelligence https://iceberg.apache.org/vendors/[tools^]. 
+When you enable the Iceberg integration for a Redpanda topic, Redpanda brokers store streaming data in the Iceberg-compatible format in Parquet files in object storage, in addition to the log segments uploaded using Tiered Storage. Storing the streaming data in Iceberg tables in the cloud allows you to derive real-time insights through many compatible data lakehouse, data engineering, and business intelligence https://iceberg.apache.org/vendors/[tools^]. 
 
 == Enable Iceberg integration
 
@@ -89,7 +89,7 @@ new-topic-name   OK
 . Enable the integration for the topic by configuring `redpanda.iceberg.mode`. You can choose one of the following modes:
 +
 --
-* `key_value`: Creates an Iceberg table using a simple schema, consisting two columns, one for the record metadata including the key, and another binary column for the record's value.
+* `key_value`: Creates an Iceberg table using a simple schema, consisting of two columns, one for the record metadata including the key, and another binary column for the record's value.
 * `value_schema_id_prefix`: Creates an Iceberg table whose structure matches the Redpanda schema for this topic, with columns corresponding to each field. You must register a schema in the Schema Registry (see next step), and producers must write to the topic using the Schema Registry wire format. Redpanda parses the schema used by the record based on the schema ID encoded in the payload header, and stores the topic values in the corresponding table columns. 
 * `disabled` (default): Disables writing to an Iceberg table for this topic.
 --
@@ -222,7 +222,7 @@ Avro::
 | timestamp | timestamp
 |===
 
-* Different flavors of time (such as time-millis) and timestamp (such as timestamp-millis) types are translated to the same Iceberg `time` and `timestamp` types respectively.
+* Different flavors of time (such as `time-millis`) and timestamp (such as `timestamp-millis`) types are translated to the same Iceberg `time` and `timestamp` types respectively.
 * Avro unions are flattened to Iceberg structs with optional fields:
 ** For example, the union `["int", "long", "float"]` is represented as an Iceberg struct `struct<0 INT NULLABLE, 1 LONG  NULLABLE, 2 FLOAT NULLABLE>`.
 ** The union `["int", null, "float"]` is represented as an Iceberg struct `struct<0 INT NULLABLE, 1 FLOAT NULLABLE>`.
@@ -322,9 +322,9 @@ SELECT * FROM streaming.redpanda.ClickEvent;
 
 Spark can use the REST catalog to automatically discover the topic's Iceberg table. 
 
-==== Filesystem-based catalog (`object_storage`)
+==== File system-based catalog (`object_storage`)
 
-If using the `object_storage` catalog type, you must set up the catalog integration in your processing engine accordingly. For example, you can configure Spark to use a filesystem-based catalog with at least the following properties:
+If you are using the `object_storage` catalog type, you must set up the catalog integration in your processing engine accordingly. For example, you can configure Spark to use a file system-based catalog with at least the following properties:
 
 ```
 spark.sql.catalog.streaming.type = hadoop
@@ -374,7 +374,7 @@ You can register the schema under the `ClickEvent-value` subject:
 rpk registry schema create ClickEvent-value --schema path/to/schema.avsc --type avro
 ----
 
-If you produce to the `ClickEvent` topic in the following format:
+You can then produce to the `ClickEvent` topic using the following format:
 
 [,bash]
 ----
@@ -404,7 +404,7 @@ FROM <catalog-name>.ClickEvent;
 
 You can also forgo using a schema, which means using semi-structured data in Iceberg. 
 
-If you produce to the `ClickEvent_key_value` topic in the following format:
+You can produce to the `ClickEvent_key_value` topic using the following format:
 
 [,bash]
 ----