Docs: further clarify warning about snapshot_ids argument for `expi…

…re_snapshots`

docs/docs/spark-procedures.md

@@ -270,7 +270,7 @@ the `expire_snapshots` procedure will never remove files which are still require
 | `retain_last` |    | int       | Number of ancestor snapshots to preserve regardless of `older_than` (defaults to 1) |
 | `max_concurrent_deletes` |    | int       | Size of the thread pool used for delete file actions (by default, no thread pool is used) |
 | `stream_results` |    | boolean       | When true, deletion files will be sent to Spark driver by RDD partition (by default, all the files will be sent to Spark driver). This option is recommended to set to `true` to prevent Spark driver OOM from large file size |
-| `snapshot_ids` |   | array of long       | Array of snapshot IDs to expire (note that the table's expiration properties will still be applied to remove all expired snapshots, unless `older_than` or `retain_last` arguments are also given). |
+| `snapshot_ids` |   | array of long       | Array of additional snapshot IDs to remove, along with those expired by `older_than` and `retain_last` arguments, and the table's [expiration properties](configuration.md#table-behavior-properties)). |
 ) |
 
 If `older_than` and `retain_last` are omitted, the table's [expiration properties](configuration.md#table-behavior-properties) will be used.