Few comments on doc patches v36-008 and 009 combined: 1) + An array of JSON objects representing the local state for each conflict attempt.
'each conflict attempt' looks misleading. We do not attempt to cause conflicts; we attempt to apply, but it may result in conflicts. Shall we rephrase to: 'An array of JSON objects representing the state of existing local row(s) that caused the conflict.' There could be multiple rows as well for multiple_unique_conflicts, thus the 'row(s)' 2) + The <link linkend="sql-createsubscription-params-with-conflict-log-destination"><literal>conflict_log_destination</literal></link> + parameter automatically creates a dedicated conflict log table. 'conflict_log_destination' parameter does not create the table automatically unless it is set to table. We shall clarify it. The conflict_log_destination when set to table or all automatically creates a dedicated conflict log table. 3) + Conflicts that occur during replication are, by default, logged as plain text When we say 'Conflicts' here, we shall make it a link to '29.8. Conflicts' chapter. That way it will be more clear. thanks Shveta
