Tweak wording for master merge template
This commit is contained in:
parent
1685d37c01
commit
5bff7d16b9
|
@ -101,10 +101,10 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
The ${h.link_to("{} on the right".format(model_title), view_url(object_to_keep), target='_blank', class_='merge-object')}
|
||||
will be <strong>kept</strong>
|
||||
and the ${h.link_to("{} on the left".format(model_title), view_url(object_to_remove), target='_blank', class_='merge-object')}
|
||||
will be <strong>deleted</strong>. The one which is to be kept may also
|
||||
The ${h.link_to("{} on the left".format(model_title), view_url(object_to_remove), target='_blank', class_='merge-object')}
|
||||
will be <strong>deleted</strong>
|
||||
and the ${h.link_to("{} on the right".format(model_title), view_url(object_to_keep), target='_blank', class_='merge-object')}
|
||||
will be <strong>kept</strong>. The one which is to be kept may also
|
||||
be updated to reflect certain aspects of the one being deleted; however again
|
||||
the details are up to the app logic for this type of merge and aren't fully
|
||||
known to the generic tool which you're using now.
|
||||
|
|
Loading…
Reference in a new issue