[fix] reword setConfig() vs parse() tip

- replace incorrect "chaining" wording in parse() docs
- describe the alternative as a single setConfig() call covering all props

Author: serhiipylypchuk1991

docs/api/methods/js_kanban_parse_method.md

@@ -13,7 +13,7 @@ description: You can learn about the parse method in the documentation of the DH
 The `parse()` method is an alias for [`setConfig()`](/api/methods/js_kanban_setconfig_method) restricted to data-related properties (`cards`, `columns`, `rows`, `links`). Both methods perform the same operation under the hood for these properties.
 
 :::tip Prefer setConfig()
-Use [`setConfig()`](/api/methods/js_kanban_setconfig_method) that accepts the same data properties **plus** every other Kanban configuration option. The method allows you to apply data together with related settings (such as [`columnKey`](api/config/js_kanban_columnkey_config.md), [`rowKey`](api/config/js_kanban_rowkey_config.md), [`cardShape`](api/config/js_kanban_cardshape_config.md)) in a single call, instead of chaining `setConfig()` and `parse()`:
+Use the [`setConfig()`](/api/methods/js_kanban_setconfig_method) method that accepts the same data properties **plus** other Kanban configuration option. Call `setConfig()` once for all props instead of calling `parse()` for data and `setConfig()` for the other props (such as [`columnKey`](api/config/js_kanban_columnkey_config.md), [`rowKey`](api/config/js_kanban_rowkey_config.md), [`cardShape`](api/config/js_kanban_cardshape_config.md)):
 
 ~~~js
 // instead of two calls