[bisq-network/bisq] Clarify DAO status shown when in sync & peers have conflicts. (PR #6130)

[jmacxx]

This is a minor wording change to a status message.  The PRE wording was confusing both for new users and experienced alike, this is cleaned up to let the user know that their DAO state is ok even if peers may not be.

The main effect of the clarification is to show the primary information first (you are in consensus with seed nodes), and the secondary information after (some of your peers are not in consensus).

**PRE:**

![Screenshot from 2022-04-04 09-29-21](https://user-images.githubusercontent.com/47253594/161567368-5d157aa9-b057-4893-8212-4922c61b15a9.png)

**POST:**

![Screenshot from 2022-04-04 08-51-29](https://user-images.githubusercontent.com/47253594/161567377-f92ac551-1dda-44b1-8f5c-c77bb9c4aee9.png)


You can view, comment on, or merge this pull request online at:

  https://github.com/bisq-network/bisq/pull/6130

-- Commit Summary --

  * Clarify DAO status shown when in sync but peers have conflicts.

-- File Changes --

    M core/src/main/resources/i18n/displayStrings.properties (4)

-- Patch Links --

https://github.com/bisq-network/bisq/pull/6130.patch
https://github.com/bisq-network/bisq/pull/6130.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/6130
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/pull/6130 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220404/18a7c42d/attachment.htm>