DBZ-7218 Suggested edits

documentation/modules/ROOT/pages/connectors/oracle.adoc

@@ -2242,17 +2242,22 @@ If the redo log lacks sufficient capacity, both the database and the {prodname}
 
 Consult with your database administrator to evaluate whether the database might require increased log capacity.
 
+// Type: procedure
+// ModuleID: oracle-connector-specifying-the-archive-log-destination
+// Title: Specifying the archive log destination that the {prodname} Oracle connector uses
 === Archive log destinations
 
 Oracle database administrators can configure up to 31 different destinations for archive logs.
-Each destination can be set with various parameters for different activities, including log shipping for physical standbys or external storage allowing for longer retention of the logs.
+Administrators can set parameters for each destination to designate it for a specific use, for example, log shipping for physical standbys, or external storage to allow for extended log retention.
-All log destination details are found in the `V$ARCHIVED_DEST_STATUS` table in the Oracle database.
+Oracle reports details about archive log destinations in the `V$ARCHIVE_DEST_STATUS` view.
 
 The {prodname} Oracle connector only uses destinations that have a status of `VALID` and a type of `LOCAL`.
-If multiple destinations are configured in your Oracle environment that satisfy that criteria, then please consult your Oracle administrator to determine which archive log destination should be used.
+If your Oracle environment includes multiple destinations that satisfy that criteria, consult with your Oracle administrator to determine which archive log destination {prodname} should use.
-You will need to provide the `log.mining.archive.destination.name` configuration property to control which path {prodname} uses.
 
-As an example, if both the `LOG_ARCHIVE_DEST_2` and `LOG_ARCHIVE_DEST_3` destinations satisfy the criteria and the administrator has confirmed that destination three should be used, you would provide this configuration using the `log.mining.archive.destination.name` property as follows:
+.Procedure
+* To specify the archive log destination that you want {prodname} to use, set the xref:oracle-property-log-mining-archive-destination-name[`log.mining.archive.destination.name`] property in the connector configuration. +
+ +
+For example, in an organization with archive destinations `LOG_ARCHIVE_DEST_2` and `LOG_ARCHIVE_DEST_3`, if both destinations satisfy the criteria for use with {prodname} (that is, `status` is `VALID` and `type` is `LOCAL`),  to configure the connector to use `LOG_ARCHIVE_DEST_3`, set the value of the `log.mining.archive.destination.name` property as follows:
 
 [source,json]
 ----
@@ -2263,8 +2268,8 @@ As an example, if both the `LOG_ARCHIVE_DEST_2` and `LOG_ARCHIVE_DEST_3` destina
 
 [WARNING]
 ====
-If multiple valid paths are configured as `LOCAL` and the destination name is not provided in the connector configuration, the {prodname} Oracle connector will use a random path.
+If your Oracle environment includes multiple destinations that satisfy that criteria, and you fail to specify the preferred destination, the {prodname} Oracle connector selects the destination path at random.
-This can lead to missing logfile problems sporadically, especially if the retention policy for one path that is picked is less than the others.
+Because the retention policy that is configured for each destination might differ, this can lead to errors if the connector selects a path from which the requested log data was deleted.
 ====
 
 // Type: procedure