PR feedback

Author: nielsbauman

docs/reference/elasticsearch/index-lifecycle-actions/ilm-searchable-snapshot.md

@@ -46,7 +46,7 @@ By default, this snapshot is deleted by the [delete action](/reference/elasticse
 
     This force merging occurs in the phase that the index is in **prior** to the `searchable_snapshot` action. For example, if using a `searchable_snapshot` action in the `hot` phase, the force merge will be performed on the hot nodes. If using a `searchable_snapshot` action in the `cold` phase, the force merge will be performed on whatever tier the index is **prior** to the `cold` phase (either `hot` or `warm`).
 
-`force_merge_on_clone` {applies_to}`stack: ga 9.3`
+`force_merge_on_clone` {applies_to}`stack: ga 9.2.1`
 :   (Optional, Boolean) By default, if `force_merge_index` is `true`, the index will first be cloned with 0 replicas and the force-merge will be performed on the clone before the searchable snapshot is created. This avoids performing the force-merge redundantly on replica shards, as the snapshot operation only uses primary shards. Setting this option to `false` will skip the clone step and perform the force-merge directly on the managed index. Defaults to `true`.
 
 `total_shards_per_node`

x-pack/plugin/ilm/qa/rest/src/yamlRestTest/resources/rest-api-spec/test/ilm/90_searchable_snapshot.yml

@@ -15,7 +15,7 @@ teardown:
         repository: foo
 
 ---
-"Test downsample in hot phase without rollover":
+"Test put lifecycle with searchable snapshot action including force_merge_on_clone":
   - requires:
       test_runner_features: [ warnings, capabilities ]
       capabilities: